BTT Software
Home
Applications
Base Converterbullet point
Canonbullet point
Egg Timerbullet point
IP Loadbullet point
IP Spybullet point
NFS Serverbullet point
Send To Printerbullet point
SNMP Managerbullet point
SNMP Trap Watcherbullet point
Stop Watchbullet point
Time Serverbullet point
Window Listbullet point

NFS Server & Port Mapper

This software package includes an RPC port mapper, and NFS server, which covers NFSv2 and NFSv3. Both can either be run as standard Windows applications, or as services - running as a service is the preferred method for execution. The installer can install either way, and requires Administrative rights.

RPC Port Mapper

The RPC Port Mapper supports RFC 1833, which covers version 2 of the binding protocol. There are no configuration options to this application, other than those related to installing it as a service. The port mapper can be used with other applications that require the use of a port mapper. It supports both TCP and UDP, on port 111.

Supported RFCs:

  • RFC 1014: External Data Representation Standard
  • RFC 1831: Remote Procedure Call Protocol Specification v2
  • RFC 1833: Binding Protocols for ONC RPC v2
The Port Mapper can be run as either a standalone windows application, or can be run as a service. When run as a service, events or messages are logged into the Windows Event Log.

It has been successfully tested with a variety of NFS clients.

NFS Server

The NFS Server supports versions 2 and 3 or the NFS protocol and versions 1, 2 and 3 of the Mount protocol. Both TCP and UDP are supported.

Supported RFCs:

  • RFC 1014: External Data Representation Standard
  • RFC 1831: Remote Procedure Call Protocol Specification v2
  • RFC 1094: NFS Version 2 Protocol Specification
  • RFC 1813: NFS Version 3 Protocol Specification
The exports are specified in the "nfsserver.ini", which must be in the same directory as the NFSServer.exe file. The ports used by the mount and nfs protocols can be changed, if they are specified in the [general] section. A Server restart is needed for these options to take effect.

[general]
mountport=3555
nfsport=2049

Each export should be specified as below. The section heading is name of the export, and the "exportpath" should point to the directory to be exported. The example below would export the "c:\progam files" directory. There are no limits on the number of exported directories, and export changes are applied straight away. Overlapping exports are currently allowed.

[/export]
exportpath=c:\program files

As this is the first release, the following is a list of restrictions or limitations:

  • The exports need to be manually configured in the nfsserver.ini file
  • Only works on NTFS filesystems and Windows XP or newer
  • Can't export the root of a filesystem, only sub-directories
  • No security, other than the security of the process that runs the application/service - newly created files will be owned by the owner of the NFS Server process
  • No export restrictions can be applied
  • Requires a port mapper to register the listening ports
  • Does not support symlinks or device files
  • Filename case is preserved, but case insensitive filename are not supported
  • Read and write sizes are currently limited to 8K
The NFS Server has been successfully tested with a variety of NFS clients. Please remember that any directory exported will be accessible to any NFS client, and files can be easily deleted, and may be permanently lost - Please bare this in mind when configuring exports.

Download NFS Server v1.0.0.0 (200K installer file) - last updated 28/05/2013

This software is provided as FREEWARE, and will run on Windows XP or newer. It requires an NTFS formatted file system, otherwise it cannot be used.

If this application simply does what you want, with no problems, why not consider funding BTT Softwares future development, by donating a small amount via PayPal?