[Techtalk] [OT] NIS problems on legacy Solaris 1.1.2 systems

distantnorth at netscape.net distantnorth at netscape.net
Tue Oct 7 09:50:58 EST 2003

Hi, everyone,

I'm hoping that someone has been doing UNIX long enough and has a good enough memory to help me with some legacy Solaris 1.1.2/SunOS 4.1.4 systems which are absolutely driving me nuts.  (Oh, and no, I can't upgrade them because of a legacy app.  Believe me, if I could I would.)

Anyway, these boxes arrived from a now closed office and I thought this was simply a matter of giving them new IP addresses.  Silly me.  I did run /usr/etc/install/sys-unconfig and then go through a manual configuration.  At first they wouldn't communicate at all.  I took some hard coding of netmask and broadcast address a previous admin had done in /etc/rc.local, added an appropriate line to let this ancient pre-CIDR version know that our address really was class C in /etc/netmasks, did put the NIS master and slave in /etc/hosts.equiv, did put appropriate entries in /etc/hosts, /etc/resolv.conf, /etc/defaultdomain, and /etc/defaultrouter.  The net result is that the box is now up on the network and resolving fine through DNS.  The minute I try to put it back into the NIS domain is when I run into trouble.  It won't see the NIS master and won't see the domain.  This despite the fact that I can communicate with the NIS master and slave just fine via telnet, ftp, ping, etc...

(Yes, I know what I just described is a security nightmare.  I'll address that soon enough.)

What am I missing?  What stupid little Solaris 1.1.x trick do I not know?  This is my first exposure to the ancient BSD-based Solaris and it hasn't been a happy experience so far.

Any ideas are muchly appreciated.

All the best,
(who is just fine with Solaris 2.x, 7, 8, and 9)

McAfee VirusScan Online from the Netscape Network.
Comprehensive protection for your entire computer. Get your free trial today!

Get AOL Instant Messenger 5.1 free of charge.  Download Now!

More information about the Techtalk mailing list