Frequently Asked Questions
Q1: What versions of Windows are supported?
Server 2003, Server 2008, Server 2012,
Windows 7 (32 and 64-bit),
Windows 8 (32 and 64-bit),
and Windows 10 (32 and 64-bit).
NOTE: XP is no longer supported; as of version 6.3 it no longer runs on
Windows XP, due to runtime libraries on which we depend not being
compatible with XP.
Q2: How do I go from the evaluation to the paid version, or upgrade from one version to another?
We recommend these steps to go from the evaluation to paid version,
or to upgrade from one version to the next:
- Copy the nfs.cfg file from the existing installation directory, which defaults to c:\AllegroNFS, to somewhere safe.
- Uninstall the current version, saying "yes" to the question about
preserving the nfs.cfg file. Answering "yes" will cause all files
in the installation directory to be removed, except nfs.cfg.
- Install the new version. This might require you to reboot.
Q3: Why do I get no response from the NFS server?
If you are using firewalls on Windows or any of the clients, their
configuration must be adjusted to allow various ports through to the
server and clients.
NFS works by using several subprocesses to handle various aspects of
NFS operation. These subprocesses are called portmapper
, and lockd
Each of these subprocesses uses one TCP port and one UDP port
to listen for requests.
have standard port numbers
that they use.
uses port 111 and nfsd
uses port 2049.
, and lockd
arbitrary port numbers that the portmapper
This number will likely be different every time Allegro NFS
initializes and can be a problem if you want to do a
one-time configuration of your firewall to allow NFS to work.
To help with this problem,
Allegro NFS allows you to assign these services a consistent
port number. You can specify the port number
by starting the Allegro NFS configuration program, clicking on the
"Global" tab, and supplying the port number of your choice in the
"Subprogram port assignments" area..
Keep in mind that if you use a port number that is being used by some other
Allegro NFS will fail to initialize correctly and NFS
operations will not work.
If this happens, try a different port
number and restart Allegro NFS.
Here are the ports which must have access through your firewall:
UDP and TCP port 111 (for portmapper protocol)
UDP and TCP port 2049 (for NFS protocol)
Your chosen UDP and TCP port for mountd, statd, and lockd
Specification of these ports requires Allegro NFS Server
version 4.3 or later.
Q4: Are symbolic links supported?
A4: Yes, but it requires Allegro NFS Server version 5.0 or later.
Q5: Is chmod supported?
A5: chmod is not supported. chmod requests are simply ignored by
Allegro NFS. This was a specific design decision to avoid confusing
problems that can be caused when the chmod'd files are subsequently
accessed on the Windows side.
The execute bit is simulated based on filename extension. Files with
filename extension exe, bat, and com automatically have the 'x' bit
If you need the execute bit set, you can make Allegro NFS enable the
execute bit on every file, which may suit your needs. You can do this
by editing the "set mode bits" setting for the export using the
configuration utility. If you use a value of '111', that will set the
execute bit for all files.
Q6: When starting Allegro NFS I get 'Error: portmap_set failed'. What's wrong?
A6: This error indicates that you likely have another vendor's
NFS product installed and it is causing a conflict when Allegro NFS
attempts to set up a portmapper at the same port.
The solution is verify that other NFS server products are completely
uninstalled, reboot, and attempt to start Allegro NFS again.
In particular, customers have noted that Microsoft Services for UNIX includes
a portmapper daemon. Uninstalling or disabling this process has been known to
resolve this issue.
Q7: I exported a mapped network drive or a UNC path, but when I access the export from an NFS client, the files are inaccessible. Why doesn't this work?
The Allegro NFS service normally runs under the window SYSTEM (aka
LocalSystem) account. This account is very powerful and has access to
all files on the local computer (although Allegro NFS will restrict
access according to the configuration you supplied). However, the
SYSTEM account does not have access to network drives.
To remedy this problem, you can reconfigure the Allegro NFS service so
that it runs under a normal user account. To do this, right-click on
My Computer and select 'Manage'. Go into "Services and Applications",
then "Services". Locate the "NFS Server" entry, right-click on it and
select "Properties". Select the "Log On" tab. You'll find that it is
currently set to "Local System account". Select the "This account"
radio button and fill in the account name (and associated password)
for the account that you want Allegro NFS to run under. Then go back
to the "General" tab and stop and restart the service.
Note that the user account that you choose will only be able to
succesfully export files/directories that it normally has access to.
Q8: Why don't the clients see the exports I created?
Make sure your exports start with a slash (/). The usual
way NFS clients reference mounts is from the root directory.
Q9: The NFS service will not start and I see "wait-for-service-to-start: Unexpected service state: 3" in the NFS console. How to fix?
Likely you have another NFS server installed which is holding onto ports
Allegro NFS needs to start. Uninstall or stop the other service, and
Allegro NFS should start properly.
Q10: I played around with other nfs products, but now I'm trying yours, so why are my nfs requests hanging?
It is likely you have another NFS product installed. If you tried the
NFS client in Windows 7, here's how you can turn it off:
Uninstall or change a program =>
Turn Windows features on or off: uncheck "Services for NFS"
Q11: Why can't I mount my export on linux clients with nfs-utils version 1.2.2 or greater?
A11: Newer versions of mount use mount.nfs4 by default. You'll need to specify version 2 or 3 in your mount command. Usually this is done by specifing -o vers=3 on the command line, but please see man mount or man mount.nfs on your system for more information on how to specify the version.
Q12: Why do I get the following error message in Windows: Error 1061:The service cannot accept control messages at this time. when I try to restart the Allegro NFS service?
A12: You'll need to restart the service as the Administrator user.
Q13: How do I present the same share with different permissions?
The internal model of Allegro NFS does not allow this, but there is
a workaround: use the Windows SUBST
command to make additional
drive letters that refer to the same real drive where the
and then have Allegro NFS use different drive
letters for the same shared
directory. Say you want to share
to several different hosts
with different permissions (e.g., different UIDs). You could
subst d: c:\
subst e: c:\
then make shares for
that offer these different qualities.
Q14: Why do I get the error Can't reserve the rest of the C space
ASLR is responsible
. Your options are to
- upgrade to version 6.1 or later, or
- turn off ASLR.
Note that upgrading to version 6.1 is not guaranteed to fix the problem.
We recommend that you try the
Q15: What information should I provide to get support?
Please provide the following information if you require
- Error messages, from the client and/or server.
- The AllegroNFS version number.
- The version on Windows on which you are using AllegroNFS.
- The operating system and version number of any problem clients.
The relevant logs for the problem you are having.
It is best to turn on all debugging options in the configuration app
(see the "Debug" tab), then reproduce the problem, and send us the
relevant portion of the logs as a text attachments (please no pictures
of text, it makes helping you much harder). If the log file is
large, please send us just the relevant portion.
If you took the defaults for installation, the log file is likely