How to Run NIS from a Remote Subnet?
By default, you can not run a NIS client if your NIS server is on a different subnet. This is because NIS usually runs in broadcast mode, which means that it only queries local servers when starting. In Solaris, if you want to bind to a remote server, simply initialize the client with the -c flag: # ypinit -c (/usr/sbin/ypinit on Solaris 2.x) In SunOS, instead of running ypbind normally you must run it with the -ypsetme option, and then run ypset, using the NIS server’s ip address as an argument: # ypbind -ypsetme # ypset nis-server-ip (/usr/lib/netsvc/yp/ypbind on Solaris 2.x) (/usr/sbin/ypset on Solaris 2.x) In this case, be sure to also modify the rc.local file appropriately. It is recommended that you have at least one NIS slave on each subnet. If you do this, only your NIS slave server will need to follow the above procedures all other machines on the subnet will be able to run normally, and they will bind to the local NIS slave.
Related Questions
- I have a remote location in addition to my office. Can I run LimoNexus at the remote location and connect with the office?
- I have setup my SQL Remote to send every 10 minutes. What happens when it takes more than 10 minutes for DBRemote to run?
- What are the maximum number of console redirection sessions that I can run on a remote system?
