1855408 Members
2292 Online
104110 Solutions
New Discussion

NIS on HP-UX and SCO

 
Nicky Davey_1
Occasional Contributor

NIS on HP-UX and SCO

Hi,

Hope someone can help here. I am new to configuring NIS. I configured the
master on a HP-UX 11 machine and a client on a SCO Openserver 5.0.5 machine (on
a different subnet so have selected the ypset option). I can sync passwords
from master to client, but not the other way. The console on the SCO machine
continually flashes up the message "NIS server not responding for domain
"domainname" still trying". I checked out SCO's tech. articles with no luck so
i thought i would try here. ypserv etc. on the master is running, ypbind is
running on the client, ypwhich reports as expected on both machines, i don't
know where the YP_ADDR option in SCO is so i have been using ypset at the
command line. yppoll works fine on both machines also. Also i noticed in Sam
A/cs for users and groups i have groups, NIS users, shouldn't i also have local
users?

Any help would be much appreciated,

Rgds,

Nicky D.
1 REPLY 1
Jason Luginbuhl_1
Frequent Advisor

Re: NIS on HP-UX and SCO

I'm not really experience with SCO's version of Unix or NIS, but I'm assuming
that the commands are similar to HP. If ypserv is running on the master and
ypbind on the client that is a good start. You might want to check to see if
the client is bound. The command is ypwhich on hp but I'm not sure for SCO.
Also you may want to make sure that the SCO client can communicate with the
ypserv daemon on the HP. If the client were HP, the command for that would be:
# rpcinfo -u hostname_of_NIS_Master ypserv

Make sure to use the fully qualified name. If that doesn't work then you may
want to use the IP of the NIS master instead of the hostname to take name
resolution out of the loop. You should expect to see something like the
following output from a sucessful rpc communication with ypserv on the Master:
program 100004 version 1 ready and waiting
program 100004 version 2 ready and waiting

Again, I'm not sure how these commands translate to SCO, but it may be worth a
try.