On Mon, Sep 06, steve-ss wrote:
On Monday 06 September 2004 10:28, Thorsten Kukuk wrote:
On Sun, Sep 05, steve-ss wrote:
On Sunday 05 September 2004 07:14, Thorsten Kukuk wrote:
The question is, why is the SuSE box not allowed to contact the rpc.yppasswdd daemon on the NIS master server? Are you really sure it is running? Are there any firewalls, /etc/hosts.{allow,deny} rules or similar? What can you find in the log files on the master server?
Not to say: it works fine for me.
Yes. I have a firewall. What port needs to be open?
The RPC one and the ones used by rpc.yppasswdd and ypserv.
Thorsten
Hi Thorsten. Hi Everyone.
here is a snip from rpcinfo -p program vers proto port 100000 2 tcp 111 portmapper 100000 2 udp 111 portmapper 100004 2 udp 829 ypserv 100004 1 udp 829 ypserv 100004 2 tcp 832 ypserv 100004 1 tcp 832 ypserv 100009 1 udp 849 yppasswdd
So from this I can guess that these ports need to be open. Is this correct?
Yes. But be aware: If you restart the services, this ports will change.
What confuses me is this: 100003 2 udp 2049 nfs 100003 3 udp 2049 nfs 100227 3 udp 2049 nfs_acl 100003 2 tcp 2049 nfs 100003 3 tcp 2049 nfs 100227 3 tcp 2049 nfs_acl
nfs works fine without any mention of 2049 on our firewall (SuSEfirewall2)
Could be that there is a special rule for NFS in the code or this is because nfs uses ports above 1024. Thorsten -- Thorsten Kukuk http://www.suse.de/~kukuk/ kukuk@suse.de SuSE Linux AG Maxfeldstr. 5 D-90409 Nuernberg -------------------------------------------------------------------- Key fingerprint = A368 676B 5E1B 3E46 CFCE 2D97 F8FD 4E23 56C6 FB4B