Several people emailed with various suggestions:
Run this nissetup script, (did that)
Hard code the server name by entering it into rc.config. (Didn't try that)
An AIX box started having the same problem, after I configured it.
(It was the old master server). I wound up talking to one of the
University's main Unix support people and we figuered it out.
The University has a class B address (128.83.x.y). However when they
assign IP's they assign them to departments as if they where class C
addresses (my dept is 128.83.62.x). When I initially setup sherman I
left the default netmask of 255.255.0.0. So sherman was thinking the
broadcast address was 128.83.255.255. The clients were thinking the
broadcast address was 128.83.62.255. After editing rc.config to
change the netmask to 255.255.255.0 and rebooting the machines
started seeing the NIS server without any problems.
later,
James
----------------------------------------------------------------------------
James Hammett
ACITS (Academic Computing) CPE 4.468
Chemical Engineering Unix Support 471-9701
----------------------------------------------------------------------------
An injustice anywhere is a threat to justice everywhere - MLK jr.
----------------------------------------------------------------------------
Received on Fri Aug 11 2000 - 13:43:28 NZST