NFS in unstable not working, a bug?
Hello,
I upgraded my home server machine and at the same time moved from debian testing
to unstable. Now, I've basicly got everything else working except for nfs. With
the old machine and testing distribution everything was working fine. So, I'm
wondering if there are broken packages in unstable or is it my setup that's broken.
my setup is following: client connecting to the debian/unstable server is ubuntu
hoary machine. ip-number of the client is 192.168.0.10 and that of the server is
192.168.0.1.
In the server:
/etc/hosts.deny is empty
/etc/hosts.allow has a line:
ALL: 192.168.0.10
server:# showmount -e
/home/shared 192.168.0.10
server:# rpcinfo -p localhost
program vers proto port
100000 2 tcp 111 portmapper
100000 2 udp 111 portmapper
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 32772 nlockmgr
100021 3 udp 32772 nlockmgr
100021 4 udp 32772 nlockmgr
100021 1 tcp 32768 nlockmgr
100021 3 tcp 32768 nlockmgr
100021 4 tcp 32768 nlockmgr
100005 1 udp 993 mountd
100005 1 tcp 996 mountd
100005 2 udp 993 mountd
100005 2 tcp 996 mountd
100005 3 udp 993 mountd
100005 3 tcp 996 mountd
391002 2 tcp 792 sgi_fam
100024 1 udp 799 status
100024 1 tcp 802 status
server:# iptables -L
Chain INPUT (policy ACCEPT)
target prot opt source destination
Chain FORWARD (policy ACCEPT)
target prot opt source destination
Chain OUTPUT (policy ACCEPT)
target prot opt source destination
But my client can't make a rpc connection to the server:
client:# rpcinfo -p 192.168.0.1
rpcinfo: can't contact portmapper: RPC: Remote system error - Connection refused
Does anybody have any idea what's going on here? Thanks in advance for any help!
juhis
Reply to: