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 102 tcp111 portmapper 102 udp111 portmapper 132 udp 2049 nfs 133 udp 2049 nfs 134 udp 2049 nfs 132 tcp 2049 nfs 133 tcp 2049 nfs 134 tcp 2049 nfs 1000211 udp 32772 nlockmgr 1000213 udp 32772 nlockmgr 1000214 udp 32772 nlockmgr 1000211 tcp 32768 nlockmgr 1000213 tcp 32768 nlockmgr 1000214 tcp 32768 nlockmgr 151 udp993 mountd 151 tcp996 mountd 152 udp993 mountd 152 tcp996 mountd 153 udp993 mountd 153 tcp996 mountd 3910022 tcp792 sgi_fam 1000241 udp799 status 1000241 tcp802 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 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: NFS in unstable not working, a bug?
> > Please check /etc/default/portmap; I had a nasty surprise there once > when someone dropped OPTIONS="-i localhost" there, which binds it to > lo or to 127.0.0.1 or otherwise makes it refuse connections from > elsewhere, preventing all remote connections. By and large various > defaults that break my setup show up in /etc/default/, which I suppose > saves me the trouble of looking in still odder places, but still, ugh. > > > -- wli > Hi, Firstly, Thanks William for your fast answer. And thanks for solving my problem!!! Actually in my installation there was no portmap file in /etc/default directory, so I thought I'd run dpkg-reconfigure portmap if there's something wrong with my installation of portmap. Well, dpkg-reconfigure asks if the portmapper should be bound to localhost and I had this setting as 'yes' (so the same thing but not in /etc/default). Anyhow, I changed that, and now it's just working! Thanks alot! juhis -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
