Solaris 2.6 NIS master problems
The problem is that the SunOS boxes were running at a broadcast address of
137.71.0.0 instead of 137.71.255.255. It seems the default is 0s when it
should really be 1s - a little reading told me that when SunOS came out there
was no finalized standard.
Anyhow, changing /etc/netmasks from
137.71.0.0 255.255.0.0
to
137.71.255.255 255.255.0.0
did the trick
Thanks for the quick response Casper
- J
Original Post:
On Sep 14, 1998, Jay Donoghue said:
>
>Hi Managers,
>
>We are trying to move from a SunOS 4.1.4 NIS master to a Solaris 2.6 5/98
>NIS master (and slave servers). Note that we are not using shadow password
>at this time, the password file looks like a standared SunOS passwd file.
>
>NIS starts fine on the master and slaves (mixed Solaris and SunOS). Solaris
>clients bind to the NIS domain, but SunOS clients hang after starting ypbind
>saying that the server for domain "blah" is not responding.
>
>I snooped these failing SunOS machines, and they kept outputting "NONACK NIS"
>errors.
>
>We found a web page that discussing the use of the "-B" variable in
>the Makefile and 'ypxfr -b' that may be related to this problem, but
>we can't seem to understand the chart. The URL is:
>http://docs.sun.com:80/ab2/coll.47.4/NETNAME/@Ab2PageView/36472?DwebQuery=NIS+
>so
>laris+sunos
>
>In the meantime, we have reverted back to the SunOS master.
>
>Thanks in advance - I will summarize,
>
> - Jay Donoghue
--
Jay Donoghue ##|`#####
Analog Devices, Inc. ##| `###
(781) 937-2295 ##| >#
##| ,### PGP Key available:
Jay.Donoghue@analog.com ##|,##### Email with subject "PGP_key"
