Having a weird problem that is puzzling me... been researching all day to no avail.

We have recently moved to multiple VLANS on our VM network and when we did this VFS started acting flakey on the Linux machines. They are all various incarnations of RedHat, the oldest being ES 2.1 which is the current focus of this message.

We were able to fix the NFS issue by moving the Linux machines back to their old VLAN config and not VM support is telling us that the issue is because NFS is configured to use UPD rather than TCP. So in an effort to test this theory, I was remounting from the DEV machine (Red Hat Enterprise Linux ES release 4 (Nahant Update 6)) to the PROD machine (Red Hat Enterprise Linux ES release 2.1 (Panama)). Please hold the "upgrade to newer" responses at this point .

Anyhow, on both machines port 2049 exists in the /etc/services file for UDP and TCP. On the DEV machine we have the following rpcinfo output

program vers proto port
100000 2 tcp 111 portmapper
100000 2 udp 111 portmapper
100024 1 udp 969 status
100024 1 tcp 972 status
100011 1 udp 813 rquotad
100011 2 udp 813 rquotad
100011 1 tcp 816 rquotad
100011 2 tcp 816 rquotad
100003 2 udp 2049 nfs
100003 3 udp 2049 nfs
100003 4 udp 2049 nfs
100003 2 tcp 2049 nfs
100003 3 tcp 2049 nfs
100003 4 tcp 2049 nfs
100021 1 udp 32768 nlockmgr
100021 3 udp 32768 nlockmgr
100021 4 udp 32768 nlockmgr
100021 1 tcp 32786 nlockmgr
100021 3 tcp 32786 nlockmgr
100021 4 tcp 32786 nlockmgr
100005 1 udp 829 mountd
100005 1 tcp 832 mountd
100005 2 udp 829 mountd
100005 2 tcp 832 mountd
100005 3 udp 829 mountd
100005 3 tcp 832 mountd

and on the PROD machine we have

program vers proto port
100000 2 tcp 111 portmapper
100000 2 udp 111 portmapper
100024 1 udp 32768 status
100024 1 tcp 32768 status
391002 2 tcp 32769 sgi_fam
100021 1 udp 32770 nlockmgr
100021 3 udp 32770 nlockmgr
100021 4 udp 32770 nlockmgr
100011 1 udp 620 rquotad
100011 2 udp 620 rquotad
100011 1 tcp 623 rquotad
100011 2 tcp 623 rquotad
100005 1 udp 32908 mountd
100005 1 tcp 34655 mountd
100005 2 udp 32908 mountd
100005 2 tcp 34655 mountd
100005 3 udp 32908 mountd
100005 3 tcp 34655 mountd
100003 2 udp 2049 nfs
100003 3 udp 2049 nfs

So the question is, why isn't TCP showing up on the PROD machine even though its listed in the services file?

Thanks!

Report the errors that you get when you issue the mount command for your NFS volume, both at the command line and in messages.

One problem I've run into is that NFS is picky about DNS. For security purposes, the client needs to have correct forward and reverse mappings.

Thanks for the info and sorry for the late response to it... got slammed with other higher priority stuff shortly after posting. Gotta solve this by the end of month though now...

From the machine tying to mount:

mount syrwms:/home/scratch /home/prod_scratch -o rsize=8192,wsize=8192,timeo=14,intr,soft,tcp
mount: mount to NFS server 'syrwms' failed: RPC Error: Program not registered.

There are no messages in the "messages" file that are related to this command.