This page is a part of XSecurePro online Help Manual.
X-SecurePro is X-Server for windows by Labtam bringing your PC to Unix and X-Windows. Seamless Secure integration from PC to Unix and X-Window System. Bringing Maximum Security while still finding all of the standard access of X11, TCP/IP, FTP, TFTP, LPR, TELNET, NFS and SSH. Visit Home of X Server for windows for more information.



NFS-Server


It seemed like my FTP server conflicted with your NFS-Server. I am using WarFTP server. Is there a known conflict between these two products?

As we know, WarFTP usually runs the 'portmapper' service daemon. You may check this by using the 'netstat a' command.

If you see the TCP and/or UDP 'LISTEN' socket with '111' port number, then portmapper is active.

If you see also the 'LISTEN' socket(s) with '2049' port number, then you have NFS-Server active (already!).

The third important thing is the presence of the mountd 'LISTEN' socket(s). This service does not have a constant port number (it may be 1058, but not always).

Please also run the 'rpcinfo -p YourPC' command (where YourPC is the hostname or IP address of your PC with WarFTP) on any machine with UNIX-like system (Solaris, LINUX, AIX, OS/2). This command will show you all services that are registered in your WarFTP's portmapper.

If you see the 'mountd' and do not see 'nfs' registered in the portmapper, then you can simultaneously use our NFS-Server with WarFTP. Simply run it as 'nfs_serv.exe -ExternalPortmapper'.

Before disabling WarFTP, please try to run our NFS-Server with the 'nfs_serv.exe -ExternalPortmapper' command. If you obtain problems, then you need to disable somehow the WarFTP's portmapper to use our NFS-Server.

In any case, you should worry if you see the TCP and/or UDP 'LISTEN' socket with '111' port number before you run our NFS-Server.


I installed NFS-Server and set "NFS User Access" to 'any-host, any-user, any-group can read/write'. After mounting the PC-local-disk (C:\temp) on the Linux-file-system (/usr1/temp), I (not root-user) can read the PC-files. But I cannot write (and create) any file on the NFS-mounted disk. Only the root-user can write files. We use "RedHat 6.0" Linux.

There are two ways to specify "User ID" and "Group ID":

1) One recommended for "RedHat 6.0" Linux:

  • Mount a PC-local-disk (as root-user)
  • Change directory to the mount point
  • Run command 'chown -R <User ID>:<Group ID> <mount point>' (for example, 'chown -R root:wheel /usr1/temp')

2) One recommended for Solaris.

To set up the UID and GID that the (Solaris) nfs-client will see, you can edit the export.us file (in the XSecurePro home directory). For example, the following lines:

d:\mnt\ 2603 1003 W 0
=>192.168.136.* 65535 65535 0

indicate that any host from the sub-network 192.168.136.* will be able to mount to 'd:\mnt', and UID and GID will be 2603 and 1003 after mounting (only digits are allowed here, not names. You can determine this by using the command 'id' on the UNIX box). By default, UID=0 and GID=0 (i.e. root).

You should use UID and GID only known to a UNIX host.


How can I control the file mode? Can I set or reset the 'system', 'archive', or 'hidden' attribute of MS Windows file (and directory) by using UNIX commands?

Unfortunately, the FAT file system does not support permissions similar to UNIX permissions (i.e. 'Read/Write/Execute' for 'user/group/world'). While writing files from UNIX to MS Windows, NFS-Server applies the following rules:

UNIX attributes DOS attributes

-r--r--r-- FILE_ATTRIBUTE_NORMAL
-rw-rw-rw- FILE_ATTRIBUTE_SYSTEM
at least one execution allowed FILE_ATTRIBUTE_HIDDEN
at least one write not allowed FILE_ATTRIBUTE_READONLY
for all files FILE_ATTRIBUTE_ARCHIVE

You can set/reset attributes by using UNIX commands. And so you can set up attributes of MS Windows file (for example, the command 'chmod +x <file name>' will produce the 'hidden' <file> on the MS Windows box).


How to run your NFS Server as a MS Windows XP service?

You can find full description of how to install, uninstall, make settings, specify properties, run and control NFS-Server as a MS Windows XP service in subsection The NFS-Server service Tab of section The Run Box in chapter Configuring XSecurePro.

Also, there is information on how to resolve access to NFS-Server for MS Windows Firewall.


I copy a file (1 GB) from NFS server (read operation) to the client PC by 2 ways:
1) from the mapped disk 'M'
2) from My Network Places/Entire Network/XwpNTrdr/Remote NFS Servers/xxx.xxx.xxx.xxx./Directory without disk mapping.
I could not find out why there is so big difference in performance (more than 30%).
I tried also copy operation from the client to the server (write operation) and the difference is smaller but still important.
Thank you very much for your reply if there is any information that explains the problem.

The difference in performance between mapped disk and XwpNTrdr network place is in that MS Windows uses different components for mapped drive requests (MPR) and for UNC requests (MUP). The NFS-Client driver processes both of the request types equally.

Note that trace flags (enabled with the NFStrace utility and used by the NFS-Client driver) have an influence on performance of read/write operations. So you should switch off all trace flags to eliminate the trace influence. (See section The NFStrace Utility in Appendix E.)

Also, you can choose Async for Asynchronous Write mode or Sync for Synchronous Write mode that NFS-Client will use (for NFS-3 protocol version). This choice has critical influence on performance of write operations. (You can choose the mode on the The Advanced Tab described in section NFS-Client Settings under MS Windows NT4/2000/XP in chapter Network File System Client (NFS-Client).)






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


Labtam Copyright 1999 - 2009 LabtamTM Inc.