Now I am confused!
The list came from rpcinfo -p 192.168.1.1 run on the bust machine and that is
the ip address of the server. There is only one ypserv running on the network
and it is the same machine as the nfs server. So rpcinfo does seem to be
seeing the right machine.
I get the same result running the command on a client where I can see the
mounted nfs directory.
I also get the same result when I run the command on the server. I checked the
server ip with ifconfig and it is 192.168.1.1.
I am sure its a client issue....the other clients work fine.
The list below was cut and pasted from the server screen
rpcinfo -p 192.168.1.1
program vers proto port
100000 2 tcp 111 portmapper
100000 2 udp 111 portmapper
100009 1 udp 1022 yppasswdd
600100069 1 udp 636 fypxfrd
600100069 1 tcp 638 fypxfrd
100004 2 udp 661 ypserv
100004 1 udp 661 ypserv
100004 2 tcp 664 ypserv
100004 1 tcp 664 ypserv
rpcinfo -p localhost
program vers proto port
100000 2 tcp 111 portmapper
100000 2 udp 111 portmapper
100009 1 udp 1022 yppasswdd
600100069 1 udp 636 fypxfrd
600100069 1 tcp 638 fypxfrd
100004 2 udp 661 ypserv
100004 1 udp 661 ypserv
100004 2 tcp 664 ypserv
100004 1 tcp 664 ypserv
Maintained by the ILUG website team. The aim of Linux.ie is to
support and help commercial and private users of Linux in Ireland. You can
display ILUG news in your own webpages, read backend
information to find out how. Networking services kindly provided by HEAnet, server kindly donated by
Dell. Linux is a trademark of Linus Torvalds,
used with permission. No penguins were harmed in the production or maintenance
of this highly praised website. Looking for the
Indian Linux Users' Group? Try here. If you've read all this and aren't a lawyer: you should be!
