eric@eddie.MIT.EDU (Eric Van Tassell) (05/19/89)
Is there anyone on the net I can talk to about getting a single NeXT
to play nice on a YP network . I am now getting zillions of netinfo timeouts.
Yes, I did read the manual. TIA. --
Eric Van Tassell(dlcdev!eric@eddie.mit.edu)
Progress Software Corp.
22B Cotton Rd.
Nashua, NH 03063 {603-882-2488}gerrit@nova.cc.purdue.edu (Gerrit) (05/19/89)
In article <11776@eddie.MIT.EDU> eric@eddie.MIT.EDU (Eric Van Tassell) writes: > >Is there anyone on the net I can talk to about getting a single NeXT >to play nice on a YP network . I am now getting zillions of netinfo timeouts. >Yes, I did read the manual. TIA. -- [ I sent this to eric already, but I figured this problem could be fairly common given the documentation that discusses setting up NetInfo. If you get in the same bind, you can try the following "bugfix".] It sounds like your problem isn't really YP, but rather that NetInfo is misconfigured. After many headaches which yielded the same sort of netinfo timeouts, I'd suggest doing the following: Boot the machine in single user bsd -s Once the machine is up, fire up portmap and nibindd: # /usr/etc/portmap # /usr/etc/nibindd Now try the following, looking for "broadcasthost" in the output of: # niutil -list . /machines If one of the machines listed is "broadcasthost" NetInfo will be using the broadcast address to locate its parent NetInfo server, which probably doesn't exist. To fix this, run: # niutil -destroy . /machines/broadcasthost which deletes this default bogus entry. It would have been left behind if you didn't select a "Non-NeXT network" from the NetManager when you configured the machine. After this, halt the machine: # halt And boot again (don't use "# reboot" because it will reboot in single-user). bsd Hope this helps. Gerrit Huizenga NeXT Workstation Support Purdue University Computing Center gerrit@mentor.cc.purdue.edu