Mac OS X Installation Procedure: Difference between revisions

From CLONWiki
Jump to navigation Jump to search
Boiarino (talk | contribs)
No edit summary
Boiarino (talk | contribs)
No edit summary
Line 33: Line 33:
   sudo domainname CCCHP
   sudo domainname CCCHP
   sudo ypbind
   sudo ypbind
If last command does not return after 10 seconds, Ctrl-C and run it in debug mode:
  sudo ypbind -d
It should return error message, one of following:
    *  unknown domain mydomain.nis: a NIS server was found but it doesn't know the NIS domain name you have specified. Check the name and reenter the domainname command.
    * dead domain mydomain.nis: a NIS server was found and it knows the domain name you've specified. However, this domain is currently marked inactive and cannot be used. Check if you should specify another domain and repeat the domainname command with its name.
    * Domainname not set. Aborting: You forgot or mistyped the domainname command. Enter it correctly and repeat the test.
    * /var/yp/binding/mydomain.nis.ypservers does not exist, defaulting to broadcast: The system has sent out a broadcast message to search for a NIS server, but no server has responded. This can have different reasons:
          o The NIS server is not running: Make sure that the NIS server really is there. If you know its name, you can use the ping command to see if it's alive.
          o The NIS server and your machine are in two different IP subnets: In this case it's impossible that your machine can find the NIS server automatically. Create a file /var/yp/binding/mydomain.nis.ypservers that contains the IP address(es) of your NIS server(s). You have to replace "mydomain.nis" with the correct name of your NIS domain
          o The administrator of the NIS server disabled server recovery through broadcasts for security reasons: In this case, do the same as in the "different IP subnet" situation.
          o There is an error in the IP netmask of your ethernet interface: Enter ifconfig -a to get a list of all your network interfaces and check whether the netmasks are set correctly. Perhaps there was a simple typo during system installation. Many network features will work correctly even with this error, but services that rely on broadcasts certainly will not.
   ypwhich
   ypwhich

Revision as of 14:18, 10 May 2007

Configuring Domain Name System (DNS) server:

 1. Open the System Preferences application.     
 2. From the View menu, select Network.
 3. Select desired network connection and select Configure button.
 4. Select the TCP/IP button.
 5. After DNS Servers: enter the address of your DNS server(s) (clon00 etc).
 6. Click on the Apply Now button.



To setup NIS service type following as root:

 rpcinfo -p

If the portmapper is not running, you'll get the message

 rpcinfo: can't contact portmapper: RPC: remote system error - Connection refused

To fix that type:

 sudo launchctl start com.apple.portmap

Repeat check, you should see something like:

 program vers proto   port
   100000    2   tcp    111  portmapper
   100000    2   udp    111  portmapper

Type following:

 sudo domainname CCCHP
 sudo ypbind

If last command does not return after 10 seconds, Ctrl-C and run it in debug mode:

 sudo ypbind -d

It should return error message, one of following:

   *  unknown domain mydomain.nis: a NIS server was found but it doesn't know the NIS domain name you have specified. Check the name and reenter the domainname command.
   * dead domain mydomain.nis: a NIS server was found and it knows the domain name you've specified. However, this domain is currently marked inactive and cannot be used. Check if you should specify another domain and repeat the domainname command with its name.
   * Domainname not set. Aborting: You forgot or mistyped the domainname command. Enter it correctly and repeat the test.
   * /var/yp/binding/mydomain.nis.ypservers does not exist, defaulting to broadcast: The system has sent out a broadcast message to search for a NIS server, but no server has responded. This can have different reasons:
         o The NIS server is not running: Make sure that the NIS server really is there. If you know its name, you can use the ping command to see if it's alive.
         o The NIS server and your machine are in two different IP subnets: In this case it's impossible that your machine can find the NIS server automatically. Create a file /var/yp/binding/mydomain.nis.ypservers that contains the IP address(es) of your NIS server(s). You have to replace "mydomain.nis" with the correct name of your NIS domain
         o The administrator of the NIS server disabled server recovery through broadcasts for security reasons: In this case, do the same as in the "different IP subnet" situation.
         o There is an error in the IP netmask of your ethernet interface: Enter ifconfig -a to get a list of all your network interfaces and check whether the netmasks are set correctly. Perhaps there was a simple typo during system installation. Many network features will work correctly even with this error, but services that rely on broadcasts certainly will not.



 ypwhich