DOC HOME SITE MAP MAN PAGES GNU INFO SEARCH PRINT BOOK
 
Configuring the Network Information Service (NIS)

NIS server problems

When utilities using the network hang, this may mean that NIS is unable to contact the server. The following message on the system console means that the ypbind process is no longer able to contact the NIS server:

   yp: server not responding for name "domainname"; still trying.
To check whether the server is up and running, enter from the client:

rpcinfo -p server_name

It should display a list of programs, versions, protocols, and port numbers similar to:

   program vers proto   port
   100000    2   tcp    111  portmapper
   100000    2   udp    111  portmapper
   100002    1   udp   1027  rusersd
   100002    2   udp   1027  rusersd
   100008    1   udp   1028  walld
   100007    2   tcp   1025  ypbind
   100007    2   udp   1031  ypbind
   100007    1   tcp   1025  ypbind
   100007    1   udp   1031  ypbind
   100005    1   udp   1127  mountd
   100005    1   tcp   1049  mountd
   100003    2   udp   2049  nfs
   100024    1   udp   1128  status
   100024    1   tcp   1050  status
   100021    2   tcp   1051  nlockmgr
   100021    1   udp    621  nlockmgr
   100021    3   udp    621  nlockmgr
   100021    1   tcp    621  nlockmgr
   100021    3   tcp    621  nlockmgr
   100004    2   udp    778  ypserv
   100004    2   tcp    779  ypserv
   100004    1   udp    778  ypserv
   100004    1   tcp    779  ypserv
The portmapper, ypbind, and ypserv programs must be running on the server, or NIS cannot work correctly.

You can also use rpcinfo to check whether a specific server program such as ypserv is running:

rpcinfo -u server_name ypserv

This should return something similar to:

   program 100004 version 1 ready and waiting
   program 100004 version 2 ready and waiting

If these steps fail, run rpcinfo -p on the server's console to verify that the required programs are registered. If they are not running, restart NIS on the server. Check /etc/yp/nislog and /usr/adm/syslog for error messages.

When the required programs are up and running, check whether a network connection can be made between the client and server. See ``Network problems'' for this procedure.

If the NIS server is responding, but the problem is not solved, check to make sure the local domain is set properly. See ``Domain name problems''.


Next topic: Domain name problems
Previous topic: NIS logging

© 2005 The SCO Group, Inc. All rights reserved.
SCO OpenServer Release 6.0.0 -- 02 June 2005