Home of FTP client

sitemaphomecontact us

ProNFS Version 3.0 - NFS Client and Server by Labtam Inc.

Date: July 4, 2008

Labtam is pleased to present a new major software update for ProNFS now Version 3.0. It is the second major release for the 2008 year.

ProNFS is an NFS Client and Server for Microsoft Windows. It is the only NFS software that gives you the high performance file sharing connectivity capabilities. ProNFS enhances your networking performance and access.

The ProNFS Package can be split into the following:

ProNFS Server

ProNFS Server can be installed on any Windows 95/98/NT/2000 PC to share your local drives and folders with other networked users, no matter which operating system they are running on their workstations. Only a NFS Client is required on that system for users to mount your disks as part of their system.

ProNFS Client

ProNFS Client can be installed on any Windows 95/98/2000/NT/XP PC to enable your workstation to benefit from networks NFS Server services. With the help of ProNFS Client you can mount disks and folders from network, no matter under which operating system they reside, and make them as part of your familiar local desktop environment.

NOTES on this release (PLEASE READ):

1. The Beta3 MS Windows XP/2003/Vista x64 NFS-Client can be installed by running the self-extracting archive file, "nfsclx64.exe". This file and "nfsclx64.txt" can be found in the directory with the uncompressed package distributive.

2. The MS Windows 9x/ME/NT4/2K/2K3/XP/Vista NFS-Client can be installed by using the "Custom" installation mode only.

3. The Windows NT LPR printer driver is manually installed by running the self-extracting archive file, "lprd.exe". This file can be found in the directory with the uncompressed package distributive.

4. Use the "setup -wauto -s" command line (instead of "setup -auto") to start the "Silent Installation".

New Features on this release include:

1. Ftp:
- the "HideDrives" optional setting implemented to provide the disk drives' visibility. This allows you to reflect the Windows User Configuration -> Windows Components -> Windows Explorer Policy Settings. You can also provide your own drives' visibility;
- in the SFTP mode the ASCII/BINARY transfer mode switching was implemented (same as FTP mode). Important note. Since the added feature is non-standard for SFTP,please make sure you are aware that the initial state of transfer mode is "BINARY".
- the "NFS-Browser" mode was implemented to allow access to any remote NFS-Server's export without any NFS-Client installed on a local PC. It is the demo of the "NFS-Client SDK" usage. The "trNFSbr.cpr" file may be pointed in the "CPR file" input field to enable the full tracing.

2. NFS-Server:
- the "-RunOnTaskbar" did not allow the "Settings" item of the Taskbar menu (and the "Exports" button was passivated);
- to avoid the error message at shutdown of the PC with the NFS-Server running, the "GracefulExit=0" manual setting was implemented;
- the Unicode/UTF8 mode was implemented;
- the "Use UTF8 Name Format" setting is available in the "NFS-Server Settings";
- the "umask=&t;code>" optional setting was implemented to provide the understandable control of the files permissions. The default value is the traditional umask=0022. The "FL_MITXELENA=1" setting is obsolete as subset of umask.
- the 8.3 filename is used in non-Unicode mode for files with non-ANSI long filenames.
- the "Exports" tab (the "Settings" item of Taskbar menu) is available now if the NFS-Server is started with "-RunOnTaskbar" option.

3. NFS-Client for MS Windows NT4/2K/2K3/XP/Vista:
- the UNC access has been significantly improved. A user can directly access remote NFS servers without the necessity to navigate via "explorer. This feature is available under WinXP/SP2, Win2003/SP1 and Vista;
- the empty "net use server:export" command line is now allowed to allow UNC access to NFS-Servers;
- the Unicode/UTF8 mode was implemented. The mounting exports must still be in ANSI only;
- the "NFS Settings -> Permissions -> Remember ROFS (Read Only File System)Reply" setting was implemented to block the Write(), MKDIR(), CreateFile(), Rename(), SetFileAttributes() operation on the NFS Server and return the STATUS_ACCESS_DENIED.
- NFS-Client can be installed now under MS Windows Server 2003 R2.
- the "super-silent" installation was implemented to provide the mode of "invisible" installation of the NFS-Client as the part of a foreign package;
- The NFS-Client now supports the "CheckDirList" request of the NFS-Client mini-DDK. It provides "pseudo" re-mapping(re-mount) actions for UNC-way access of "bad" remote NFS-Servers which can unpredictably restart sometimes. The checknfs.exe utility is the sample implementation of this (see the checknfs.txt for details).
- Processed the "sophisticated rename/delete MS Windows file operation" when long- and short- filenames are used very specifically during the first 15 seconds. (see MSDN Library "File Name Aliases" article). This is for the "Aditor" text editor;
- The "NFS Settings -> Name Converting -> Remember Long Name Alias" setting was implemented to provide a "sophisticated rename/delete MS Windows file operation" mode;
- The Authentication(PCNFSd and/or LDAP) usage are much more flexible now.
Four new settings are now implemented :

- "NFS Settings -> Authentication -> Ask Authentication for each connecting attempt"
- "NFS Settings -> Authentication -> Use NFS Authentication during MS Windows Login"
- "NFS Settings -> Authentication -> Use MS Login Name/Password for NFS Authentication"
- In "NFS Client Authentication" Dialogbox has added the "Anonymous" button to set UID=-2 and GID=-2 for Unix Authentication

- The LDAP Authentication was implemented to access the LDAP Active Directory Servers of Windows 2003 R2 Standart Edition and/or Enterprise Edition. The mentioned Standard and Enterprise Editions have different schemes and require the additional tuning of the NFS-Client(see ldaptest.txt for details);
- The "NFS Settings -> Authentication -> Use LDAP v3 Server" setting was implemented to allow LDAP usage for Unix NFS Authentication;
- The "Permissions" tab is divided to "Authentication" and "Permissions";
- The "NFS Settings -> Permissions -> Use NULL Secure DACL" setting was implemented to set NULL DACL as parameter in any file operations.
- The "NFS Settings -> Name Converting -> Use this symbol as prefix for reaserved Windows names" setting is implemented to mark the reserved names as AUX, CON, NUL, and etc. By defauld is "^".
- The "NFS Settings -> Advanced -> NFS3 write synchronization mode" setting was implemented to set Asynchronous or Synchronous NFS-3 write mode. This has critical influence on the writing performance.

4. XStartup:
- the "Disconnect" button was implemented for RLogin/RExec/RSH modes to process the possible infinite (with disabled "Exit after timeout of" setting) timeout carefully;
- the "LogFile" settings is available for RLogin

5. NFS-Client SDK:
- this all-sufficient Software Development Kit (SDK) can be run from your programs to provide access to exported resources of the NFS-Servers. Its application program interface (API) is similar to the standard one of MS I/O "File Management Functions" API. Full NFS-protocol access is provided without the necessity of using any other software (that can be installed on your PC and usually named as "NFS-Client for MS Windows").

6. Telnet:
- some terminals ("vt100","vt52"..) were not colored originally. The deviation from the strong emulation was implemented to allow to use colors for such as terminal types.

The following bugs have been fixed:

1. Telnet:
- the "Colors" attribute of the "VT240" terminal type (in the "terminfo.ini" file) incorrectly has the "3" value. It was changed to the correct "Colors=16";
- the initialization of the terminal window is more correct now;
- some bugs during the loading, viewing and edition of profiles were fixed;
- the "Log All session output" provides now the same with the "Log Prontable output only" Logging mode (wrongly did nothing, what is unexpected).

2. NFS-Server and NFS-Server as NT Service:
- NFS-Server may crash sometimes after "FileWrite" operation if the tracing mode is enabled;
- a little memory leaking was fixed. This problem might be visible after 1..2 weeks of the NFS-Server application running;
- NFS-Server returned sometimes the incorrect EXECUTE attribute in the ACCESS NFS-protocol reply. As result, some NFS-Clients failed to start the executable file on Unix side;
- the "rename" NFS-protocol request was answered with incorrect data. In most NFS-Clients the reply of the "rename" was ignored, but Fedora's one uses it. As result, the rename operation (e.g., "mv testfile1 t1" command) leaded to the "Stale Handler" on "ls" execution;
- the NFS-Server might crash if the "enable logging (to NFSLOG.TXT)" setting enabled;
- the crash took place if NFS-Client sent the wrong/incorrect file handle.

3. NFS-Client for MS Windows NT4/2K/2K3/XP/Vista:
- NFS-Client may fail to connect to servers if several network cards are used;
- the delay of reply on the "FileWrite" operation could lead to a crash of the system - BSOD("Blue Screen" error);
- NFSDRIVE and NFSALIAS crashed if the NFS-Server's export list contained item(s) with non-ASCII symbols;
- the space(blanc) symbols are allowed now in the mounting export path as well as in Windows Alias name;
- incorrect error message took place as result of changing of Unix Attributes via MS Explorer.

4. XStartup:
- In rlogin mode the XStartup sends two end-line symbols (CR and LF) instead of the correct one (CR). This unexpected carriage-return symbol might lead to incorrect action of the "read" operation on the remote side.

Please read more about ProNFS in product home section of Labtam Inc site.

Single User licenses are at $40.00 USD. Please visit the Software Pricing page for pricing on Multiple Licenses.

If at anytime you require any information or assistance please do not hesitate to e-mail us at: sales@Labtam-inc.com.

Download and try ProNFS software for FREE.
Get FREE 30 day trial license to make deep software evaluation.


The programs associated in this package may send and/or receive broadcast IP requests. Since such packets cannot cross the nearest firewall/gateway/router, please be sure that these IP requests are invisible from outside your network. We assume that such behavior cannot be considered as "Hacking" or "Trojan horse's action".

Home | Product | Download | Order Now | Upgrade | Support | Pricing | Company Information | Contact Us

Labtam Copyright 1999 - 2003 LabtamTM Inc.