Hi all,
i am currently setting my windows XP environment to use with Services for Unix (NFS Client) to mount my unix file system as a network drive. However, though i could mount the unix file directory successful, but the folder is empty (which is not). Why is this so? i have imported my unix password and group file but there is no difference. Pls advise urgently. thank you
Permissions are always a thorny issue with Windows-UNIX mounts.
sorry, a fundamental question, do i need to install both the client for nfs and server for nfs to work? i have only install client for nfs at the windows and perform a map to the unix server..
Yes, but SAMBA can use the SMB protocol and the windows mount server. You can SAMBA serve your UNIX files to windows clients and vice versa, and of course you can SAMBA mount UNIX on UNIX.
For NFS, or AFS or whatever, windows and UNIX both need client and or server depending on the roles (mounted server or mounting client). I think there is even a system for mounting zip files as compressed file systems, where the netword xfer is compressed as well as the storage.
thanks for the good idea of samba, but does samba cause additional loading to the host server? sorry, i need to read up more about samba but do i need to install additional packages to do so or it is already in the os existing default packages? thanks for the idea..
---------- Post updated at 10:31 PM ---------- Previous update was at 10:27 PM ----------
for the problem which i had mentioned earlier, it is the permission of the folders that resulted me unable to see the files. had successfully managed to see the folders and the files. now, i have to do the other way round, to let the unix clients see the windows folder..
just curious any reason is samba better than Microsoft S4U?
Install SAMBA
client and server
You only need the NFS client which is part of SUA (SFU). There is nothing wrong with that NFS client. It is working as intended. The reason you are having a problem is that Windows and Unix use different authentication mechanisms.
The correct longterm solution is to use AD/LDAP. A quick "fix" is to add your UID and GID to two new DWORDs (AnonymousUid and AnonymousGid) under the following registry key:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\clientForNFS\CurrentVersion\Default
Do an Internet search and you will find plenty of documentation about this "fix"
Avoid Samba like the plague. It is seriously buggy.