ITEM: AF0130L

Binding to a NIS server across a router

Question:  I can not bind to my master NIS server across a route
           I get the following error when I do a ypset to the NIS
           master server.
       
           Sorry, I couldn't send my rpc message to ypbind on host \.
                   
Act:    Some machines have the current (as of 1/25/95) ypbind daemon
        that will not allow them to bind to the NIS server
        across a router by doing a simple 'ypset \'.
        Where \ is the IP address of the master NIS 
        server that you want to bind to.  The following error will
        be produced:

        Sorry, I couldn't send my rpc message to ypbind on host \.

        Where \ is the name your NIS client that
        displays this message on the console.

        If this is the case, do not try to configure your machine
        as a NIS client through smit.  Make sure that the 
        ypbind daemon is not running then type the following on the
        command line:

        domainname \
        startsrc -s ypbind -a "-ypset"
        ypset \

        If the domainname already exists skip the first line.



Support Line: Binding to a NIS server across a router ITEM: AF0130L

Dated: February 1995 Category: N/A

This HTML file was generated 99/06/24~13:30:28

Comments or suggestions?
Contact us