13.07.2015 Views

Naming and Directory Services (DNS, NIS, and LDAP)

Naming and Directory Services (DNS, NIS, and LDAP)

Naming and Directory Services (DNS, NIS, and LDAP)

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

■■■■Messages saying that <strong>NIS</strong> is unavailableComm<strong>and</strong>s on a client limp along in background mode or function much slowerthan normalComm<strong>and</strong>s on a client hang. Sometimes comm<strong>and</strong>s hang even though the systemas a whole seems fine <strong>and</strong> you can run new comm<strong>and</strong>sComm<strong>and</strong>s on a client crash with obscure messages, or no message at all<strong>NIS</strong> Problems Affecting One ClientIf only one or two clients are experiencing symptoms that indicate <strong>NIS</strong> bindingdifficulty, the problems probably are on those clients. If many <strong>NIS</strong> clients are failing tobind properly, the problem probably exists on one or more of the <strong>NIS</strong> servers. See“<strong>NIS</strong> Problems Affecting Many Clients” on page 117.ypbind Not Running on ClientOne client has problems, but other clients on the same subnet are operating normally.On the problem client, run ls -l on a directory, such as /usr, that contains filesowned by many users, including some not in the client /etc/passwd file. If theresulting display lists file owners who are not in the local /etc/passwd as numbers,rather than names, this indicates that <strong>NIS</strong> service is not working on the client.These symptoms usually mean that the client ypbind process is not running. Verifywhether the <strong>NIS</strong> client service is running.client# svcs network/nis/clientSTATE STIME FMRIdisabled Sep_01 svc:/network/nis/client:defaultIf the client is disabled, log in as superuser, or assume an equivalent role, <strong>and</strong> start the<strong>NIS</strong> client service.client# svcadm enable network/nis/clientMissing or Incorrect Domain NameOne client has problems, the other clients are operating normally, but ypbind isrunning on the problem client. The client might have an incorrectly set domain.On the client, run the domainname comm<strong>and</strong> to see which domain name is set.client7# domainname neverl<strong>and</strong>.comCompare the output with the actual domain name in /var/yp on the <strong>NIS</strong> masterserver. The actual <strong>NIS</strong> domain is shown as a subdirectory in the /var/yp directory.114 System Administration Guide: <strong>Naming</strong> <strong>and</strong> <strong>Directory</strong> <strong>Services</strong> (<strong>DNS</strong>, <strong>NIS</strong>, <strong>and</strong> <strong>LDAP</strong>) • January 2005

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!