nfsAxe software is a NFS client and NFS server for Windows. The only NFS software that gives you the high performance file sharing connectivity capabilities. nfsAxe enhances your networking performance and access.

nfsAxe NFS Server: nfsAxe Server can be installed on any Windows 9x/ME/NT4/2K/2K3/XP workstation 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.

nfsAxe NFS Client: nfsAxe NFS Client for Windows can be installed on any Windows 9x/ME/NT4/2K/2K3/XP workstation to enable your workstation to benefit from networks NFS Server services.

With the help of nfsAxe 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.

nfsAxe is a complicated product for integrating the Microsoft Windows and TCP/IP network environments. nfsAxe is an effective way to transform a standard PC running under MS Windows (9x/ME/NT4/2000/XP) into a multi-function terminal.

Being based on the TCP/IP open standards, the package integrates a PC into an interoperable computer network. The network of dissimilar computers and operating systems becomes perfectly transparent to you.

nfsAxe enables you to work on your PC's screen with several applications executed simultaneously on various network nodes. As a result, a heterogeneous network appears to you as a unified large computer system arranged directly on your desktop.

The nfsAxe package includes:
￭ NFS client
￭ NFS Server
￭ FTP client
￭ Telnet
￭ LPD & LPR
￭ TFTP

Requirements:

PC Hardware & Software Requirements:
￭ A standard 32-bit IBM PC (e.g., i486, or Pentium) or 100% compatible
￭ 8 Mbytes RAM (MS Windows 9x/ME/NT4/2000/XP)
￭ Color graphics controller supporting SVGA video modes
￭ Mouse Unit compatible with Microsoft Windows
￭ Optional math coprocessor
￭ 8 Mbytes free hard disk space.
￭ Note that this disk requirement does not account for the disk cluster size. The larger the cluster size the greater the disk requirement.
￭ TCP/IP facility with Windows Sockets Interface.

Host Requirements:
￭ TCP/IP protocols over Ethernet or Serial port connection
￭ Optional server implementations of FTP and TFTP
￭ Virtual terminal protocol Telnet
￭ Optional server implementation of Berkeley Line Printer protocol
￭ Login account on the host machine.

Limitations:

· Operational 30 minutes per run. After 30 minutes session you need to restart nfsAxe.

What's New in This Release: [ read full changelog ]

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.
NFS-Server:
· 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=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.
NFS-Client for MS Windows NT4/2K/2K3/XP/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
· Processed the "sophisticated rename/delete MS Windows file operation" when long- and short- filenames are used very specifically during the first 15 seconds.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-3write mode. This has critical influence on the writing performance.
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
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").
Telnet:
· the "Log All session output" provides now the same with the "Log Prontable output only" Logging mode (wrongly did nothing, what is unexpected).
NFS-Server and NFS-Server as NT Service:
· 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 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.
NFS-Client for MS Windows NT4/2K/2K3/XP/Vista:
· 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.
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.