Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!umich!samsung!zaphod.mps.ohio-state.edu!usc!ucsd!ucsdhub!hp-sdd!hp-pcd!hplsla!hpubvwa!pnl-geo!gary
From: gary@pnl-geo.UUCP ( Gary Black )
Newsgroups: comp.sys.next
Subject: Re: Loss of non-NetInfo Network Configuration
Message-ID: <23460003@pnl-geo.UUCP>
Date: 8 Mar 90 19:18:59 GMT
References: <23460002@pnl-geo.UUCP>
Organization: Battelle Northwest
Lines: 18


I have found the solution to mye problem through NeXT technical support.
Mail to ask_next@next.com is an effective way to get answers where as calling
the NeXT support number is not.  They only talk with liscensed NeXT developers.

The problem was that we (read I) pulled the /etc/hosts file from the system
that is serving as the name server for the NeXT but named it something other
than hosts.  I did an niload hosts . <yourhostsfile as per instructions in
the network and system administration manual.  This properly fired up the
netinfo network daemon and connected to the network until the machine was
rebooted.  At this time it looked for /etc/hosts but couldn't find it.
All that was necessary to remedy the problem was to rename the fi transferredd
over to hosts.  Since I lost the user accounts without the network, this
had to be done by rebooting in single user mode from the monitor.  
Everything came back properly configured after renaming the fe and rebooting
conventionally.  I hope this saves someone else this pain because the network
and system administration manual does not explicitly tell you what to name
the file.