There is a linux server supporting NFS v3 and 4, and a virtual machine with WinXP running a client service for NFS. XP can ping the server, but cannot mount NFS shares.
From /etc/exports:
/home/files
192.168.0.0/24(ro,all_squash,anonuid=1003,anongid=1003,insecure,no_subtree_check)
--debug
option is passed to nfsd
, but no corresponding output in /var/log/messages was seen. Looks like requests didn’t come to the server at all.
On windows when I run
mount 192.168.0.1:\home\files Z:
I got
ERROR — Invalid command line argument
mount 192.168.0.1:\home\files Z:
^^^^^^^^^^^^^^^^^^^^^^^
If I go with
net use Z: 192.168.0.1:\home\files
It throws
System error 67 has occurred.
The network name cannot be found.
After small change in address
net use Z: \\192.168.0.1\home\files
It skips for a second then gives another error:
System error 1231 has occurred.
The network location cannot be reached. For information about network troubleshooting, see Windows Help.
According to the digital signature and the last mod time of the ‘UNIX services’ downloaded, they’re presumably of 2003–2004 year. The Linux kernel running the server is new—3.10, so there might be a some kind of incompatibility. However, NFS v4 was released yet in the December 2000, so I’m not sure. I’ve tried to disable windows’s firewall, but with no luck. The server shouldn’t be blocking any ports for the NAT.
\\192.168.0.1
?Z:
letter I enter\\192.168.0.1\home\files
; two windows appear next: one indicating search process nad the other with error ‘Couldn’t find remote folder.’\home\files
? If it's accessible at all, windows should present you with a folder (\home
, ideally) that you could then click on and see if there's an error or prompt or what...