Support

General Questions and Comments

For non-technical questions and comments please send email to info@franz.com.

Purchase Assistance

For questions related to license purchases via the Franz Store please send email to sales@franz.com.

Technical Assistance

For installation and technical questions please send email to support@franz.com. Please first check that your question isn’t already covered in the FAQ or Documentation.  If you require technical assistance, please collect and send us the following information:

• 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 c:\AllegroNFS\nfsdebug-0.txt. You can see the name of the current log file in the configuration utility on the “Logging” tab.

Release History

• Version 7.1.0
  • Fix: premature expiration issues with the Evaluation version and recent updates to Windows have been resolved.
  • Fix: the Debug tab “Log time stamps” feature now works.
• Version 7.0.0
  • New: 64-bit version. Using the 64-bit version effectively resolves any potential memory conflicts (i.e. heap placement in Windows 10.
  • New: Allow the open-file cache to be disabled. This is described in the documentation.
  • Fix: improve the readability of log files by during off circularity detection.
  • Fix: uid and gid values above (2^25 – 1) in User Lists were ignored.
  • Fix: better handle errors when sending responses to UDP clients.
• Version 6.3.3
  • Fix: The nfsd thread could crash if a persistent file handle with a no-longer-existent volume GUID was seen.
• Version 6.3.2
  • Fix: It was possible for NFS clients to issue a readdir call with a requested max response size which is too large to fit into a UDP datagram. Such requests are now handled without creating a too-large response.
  • Compatibility enhancement: Some NFS clients (for example, the Windows 7 NFS client) can return a byte-swapped cookie verifier in readdir requests. Allegro NFS now detects and handles clients that behave in this way.
• Version 6.3.1
  • Fix: correct a regression introduced in 6.3, which resulted in empty directory listings for directories containing special files (such as pagefile.sys).
• Version 6.3
  • Add configuration option for badly behaved clients that cannot handle 64-bit file-ids; when turned on, file-ids will be truncated to 32-bits.
  • Fix: if the “nsm-state” file becomes corrupted, then handle this more gracefully by reseting its contents.
  • Fix: readdir* calls no longer takes a really long time on large directories.
  • Fix: no longer show negative fractional seconds in debug output.
  • Fix: install: detect when a reboot is pending and abort.
  • Fix: uninstall: detect when a reboot is needed and offer to reboot.
• Version 6.2
  • Fix: use an Allegro CL build that fixes a GC leak, which could result in the server process growing until it runs out of space. This bug was only present in version 6.1.
  • Fix: handle “tcp connection reset” errors, which previously made the server die and require manual restart. They are now ignored.
  • For silent installs (/S given to installer) do not start the configuration program at the end.
  • Directory entries are now returned in the order in which Windows returns them. Previously, directory listing were reversed.
  • The server can now detect when files or directories are renamed externally (i.e., not by an NFS client) and update its cache accordingly. Previously it could get into a confused state if files or directories were renamed externally.
• Version 6.1
  • Log possible conflicting NFS server running if an existing (aka system) portmapper is detected.
  • Fix: adjust the nfsd error handling so that certain errors do not cause the service to exit, and return reasonable errors to the client.
  • Fix: adjustments in heap placement for Windows 10. There should be fewer problems with service startup due to ASLR.
  • Fix: increased general client compatibility.
  • Fix: improved compatibility with the Windows Services For Unix (SFU) NFS client.
  • Fix: don’t display configuration window until config has been loaded. This will help avoid confusion in cases where the NFS server is busy and it takes a while to get a response from it.
  • Fix: handle full filesystem errors, returning the proper ENOSPC error code to the client.
  • Fix: allow statfs and fsstat procedures on filenames (as opposed to a directories).

Previous Versions