The NFS server supports up to version 4 at V6R1 of i/OS and up to version 3 at V5R4 of i/OS.
In v5r4 NFS uses the UDP protocal - that is probably your problem.
Michael Crump
Manager, Computing Services
SGCI
1509 S. Macedonia Ave.
Muncie, IN 47302
765.741.7696
765.741.7012 f
Leave the gun, take the cannoli
Clemenza in The Godfather
This email and its attachments may be confidential and are intended solely for the use of the individual to whom it is addressed. Any view or opinions expressed are solely those of the author and do not necessarily represent those of Saint-Gobain. If you are not the intended recipient of this email and its attachments, you must take no action based upon them, nor must you copy or show them to anyone. Please contact the sender if you believe you have received this email in error.
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Ingvaldson, Scott
Sent: Thursday, April 15, 2010 12:27 PM
To: Midrange Systems Technical Discussion
Subject: RE: NFS over TCP on v5r4?
The *UDP connection on port 2049 should be your NFS daemon. Do an 8 to display the job and you should see QNFSNFSD.
IIRC the System i NFS implementation is version 2. I could be wrong, it's been awhile and I haven't verified this lately.
Can you force the client to use V2 for the mount?
Regards,
Scott Ingvaldson
Senior IBM Support Specialist
Midwest Region Data Center
Fiserv.
-----Original Message-----
From: dino [mailto:dino@xxxxxxxxxxxxx]
Sent: Thursday, April 15, 2010 3:24 AM
To: midrange-l@xxxxxxxxxxxx
Subject: NFS over TCP on v5r4?
hi,
I activated nfs service via STRNFSSVR *ALL on v5r4 in order to present a share of some IFS directories to remote linux machine.
Linux machine(ubuntu client) was not able to mount it. I also tried the same operation from vmware ESXi client which returns the following: "NFS
Error: Unable to Mount filesystem: The NFS server does not support MOUNT version 3 over TCP."
doing rpcinfo -p as400.local.com gives:
program vers proto port
100000 3 udp 111 portmapper
100000 2 udp 111 portmapper
100000 3 tcp 111 portmapper
100000 2 tcp 111 portmapper
100003 2 udp 2049 nfs
100003 3 udp 2049 nfs
100005 1 udp 57063 mountd
100005 3 udp 60135 mountd
100024 1 udp 60101 status
100024 1 tcp 13221 status
100021 1 udp 27447 nlockmgr
100021 1 tcp 34928 nlockmgr
100021 3 udp 13310 nlockmgr
100021 3 tcp 40688 nlockmgr
100021 4 udp 18111 nlockmgr
100021 4 tcp 50195 nlockmgr
100021 2 udp 13214 nlockmgr
100021 2 tcp 52844 nlockmgr
100020 3 tcp 13347 llockmgr
100020 3 udp 50079 llockmgr
back to v5r4 machine, netstat *cnn gives no tcp port 2049!
* * 21 000:00:00 In ascolto
* * telnet 000:00:01 In ascolto
* * 25 000:00:00 In ascolto
* * www 000:00:38 In ascolto
* * 89 017:57:12 In ascolto
* * pop3 000:00:01 In ascolto
* * 111 010:22:52 In ascolto
* * 111 010:22:33 *UDP
* * 123 +++++++++ *UDP
* * 2034 +++++++++ In ascolto
* * 2049 010:22:20 *UDP
* * 2301 +++++++++ In ascolto
..There is no nfs over tcp!
Is nfs over tcp supported in v5r4 ?
thanks
dino muzic
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit:
http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at
http://archive.midrange.com/midrange-l.
midrange.com
