Link to home
Start Free TrialLog in
Avatar of saintjoes
saintjoes

asked on

Major Solaris NIS Problems

We have a bunch of Solaris 2.5.1 servers that
are experiencing major NIS problems.  We have installed
NSKIT 1.2 (with appropriate patches).  We have all OS patches installed.  We are having problems in these areas:
- Autmount is not working properly (same subnet, fast machines) - it timesout mounting a share
- Logging in takes a long time to authenticate (Pc and UNIX side) and sometime authenticates correct passwords incorrectly.
- PC users cannot use NIS to do hostname resolution using a winsock application.
- Ypbind loses its binding to the domain often.
Any ideas?
Avatar of pxh
pxh

I have a very similar config as you (a NIS master, running 2.5.1 and having the NISKIT installed). I do not have your problems. Let me know more details about your config, the above is too common.

Only answer now: for hostname resolution you usually use a DNS service. You can do it within your NIS domain also, but I have not herad that there is NIS for PC's...

Peter (pxh@mpe-garching.mpg.de)

Avatar of saintjoes

ASKER

We have NIS setup to DNS forwarding.  The client PC's are
using NIS as thier host name resolution.  The only odd thing in our setup is a SunOS master (these 2.5.1 machines are actually slaves, but are being used as NIS servers).
We have duplicated this on *3* Solaris 2.5.1 machines!



ASKER CERTIFIED SOLUTION
Avatar of pxh
pxh

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
I am confused...
you wrote in the comment to my answer:

"Another note: Clients wore fine if they use the SunOS machine as their nis master." and "But all clients are using the solaris machine as their master."

I conclude that you switched between master and slave server and found out that only the slave server give problems.

Question: does NIS work properly on the slave(s) itselve? Is there a difference between those slave(s)?

Again: I am not nervous about your master being a SunOS system. I had this situation here too for several years (also with previous Solaris versions).

What did you precisly do to "We have duplicated this on *3* Solaris 2.5.1 machines!"? "this" meaning the slave service.

How does your /etc/auto_master look like?


Peter (pxh@mpe-garching.mpg.de)