Bugzilla – Bug 116028
nis server for domain not found
Last modified: 2006-03-16 21:11:11 UTC
Choose nis authentication during installation. Type in the NIS-domain. Click on search servers. The server is not found. This worked in beta3! If I type in the server everything works without problems.
Created attachment 49297 [details] yast2 logs
Strange, Firewall blocks the broadcast reply but this wasn't that case, firewall had been disabled (see y2log-2).
Was network configured correctly? Did you test the netowork during installation? Could you reproduce this behaviour on installed system?
And one more info - what does 'rpcinfo -p <your-nis-server>' return?
No, it works on the installed system. I just installed another machine and there was the same problem. Nis server isn't found by the search, but is works. Network connection was ok. I pinged the nis-server successfully. Output from rpcinfo: asklein@donald:/tmp> ssh -X root@wpyc022 Password: Last login: Fri Sep 9 03:43:46 2005 from wpyc045.physik.uni-wuerzburg.de Have a lot of fun... wpyc022:~ # rpcinfo -p wpyc049 program vers proto port 100000 2 tcp 111 portmapper 100000 2 udp 111 portmapper 100004 2 udp 895 ypserv 100004 1 udp 895 ypserv 100004 2 tcp 898 ypserv 100004 1 tcp 898 ypserv 100009 1 udp 961 yppasswdd 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 100024 1 udp 32775 status 100021 1 udp 32775 nlockmgr 100021 3 udp 32775 nlockmgr 100021 4 udp 32775 nlockmgr 100024 1 tcp 32772 status 100021 1 tcp 32772 nlockmgr 100021 3 tcp 32772 nlockmgr 100021 4 tcp 32772 nlockmgr 100005 1 udp 897 mountd 100005 1 tcp 900 mountd 100005 2 udp 897 mountd 100005 2 tcp 900 mountd 100005 3 udp 897 mountd 100005 3 tcp 900 mountd 100011 1 udp 918 rquotad 100011 2 udp 918 rquotad 100011 1 tcp 921 rquotad 100011 2 tcp 921 rquotad
What is the output of that rpcinfo command during installation? Esp. when you are at that NIS authentication screen - just switch to console and test it.
Andreas, I've tried it and it works for me with last RC's. Could you test the installation and rpcinfo during installation?
Ok, I installed another machine. Nis server was not found, but works, when typed in manually. I switched to a console and ran the rpcinfo. Here is the output: program vers proto port 100000 2 tcp 111 portmapper 100000 2 udp 111 portmapper 100004 2 udp 898 ypserv 100004 1 udp 898 ypserv 100004 2 tcp 901 ypserv 100004 1 tcp 901 ypserv 100009 1 udp 986 yppasswdd 100011 1 udp 959 rquotad 100011 2 udp 959 rquotad 100011 1 tcp 962 rquotad 100011 2 tcp 962 rquotad 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 100024 1 udp 32775 status 100021 1 udp 32775 nlockmgr 100021 3 udp 32775 nlockmgr 100021 4 udp 32775 nlockmgr 100024 1 tcp 32772 status 100021 1 tcp 32772 nlockmgr 100021 3 tcp 32772 nlockmgr 100021 4 tcp 32772 nlockmgr 100005 1 udp 996 mountd 100005 1 tcp 999 mountd 100005 2 udp 996 mountd 100005 2 tcp 999 mountd 100005 3 udp 996 mountd 100005 3 tcp 999 mountd
Strange - and you say it worked in beta3 while not in 10.0. However it works for me. Nothing was done in YaST setup in that time - Thorsten, do you have an idea? The agent-ypserv doesn't return anything - it is still based on your code provided in the bug #45799
(In reply to comment #9) > Strange - and you say it worked in beta3 while not in 10.0. However it works for me. Yes, it worked the beta, but not in rc1. It I try the module in the installed system, then it works also in the rc1. (The same problem exists also in the ipp-printer search. Was fine in beta, doesn't find the printserver with RC1.)
The last comment sounds like something with the network configuration during installation was changed or firewall is not yet disabled or something similar, but not a poblem with the code itself. But I don't know if something and if yes what was changed.
Yes, I agree it is something network-related - Martin, any idea of what was changed from beta3?
There were no significant changes in this area. Andreas, perhaps you are testing in a different network structure and there is a filter somewhere? You can try tcpdump on the client and server.
Thorsten, how could one do the search for yp servers on console? (I would expect this from '/usr/sbin/rpcinfo -b ypserv 1' which probably isn't right). I really think it is not yast2-nis-client (and even not NIS) related; just want to check the other ways...
rcypbind stop domainname <mydomain> ypbind -broadcast -d rpcinfo cannot do this, since portmap does not allow it.
Andreas, could you test it?
I tested the suggestion from comment 15. ypbind -broadcast -d does not find the nis-server during installation. Even in the installed system the server isn't found.
So the problem is not in nis-client configuration - however I'm not sure where, maybe in your network configuration. Martin, could you investigate a bit?
This works again in 10.1beta5 as it worked in 9.3. SUSE 10.0 is the only broken one.
Seems to work in 10.1 stream.