Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!zaphod.mps.ohio-state.edu!rpi!uupsi!grebyn!walters
From: walters@grebyn.com (Chris Walters)
Newsgroups: comp.sys.next
Subject: Re: Problems with 2.0
Summary: Netinfo Woes
Keywords: problems 2.0
Message-ID: <24147@grebyn.com>
Date: 20 Dec 90 04:32:20 GMT
References: <2923@ux.acs.umn.edu>
Reply-To: walters@grebyn.com (Chris Walters)
Organization: Grebyn Timesharing, Vienna, VA, USA
Lines: 35

Ok,

Here is my first set of problems with 2.0.

We upgraded our NetInfo server to 2.0 and the '040; fine, no
problem.

We then proceeded to upgrade another machine.  We forgot to 
correct the Ethernet address in the NetManager application
before rebooting the "new" cube, but it found the NetInfo server
somehow and booted up.

The problem came when I went to NetManager and opened up the
'/' domain to correct the entry.  There were now duplicate entries
(the hosts were listed twice, both the server and client) in the
list.  I then blithely deleted one of the duplicates; that's when
it all fell apart.  The server hung, and still is.

I guess I got the "wrong" entry, but I am not so sure it was all
my fault!  It seems pretty poor that the duplicates were there
to begin with and I think NetInfo/NetManager is to blame.
If anyone has any ideas about how to fix this without
reinstalling I'd like to hear about them!

Can anyone point to any general guidelines on rebuilding corrupted
NetInfo .nidb files?  Have I missed this in the FM?

Another problem:  printing to a DEC Printserver 20 via a VAX.
It didn't work in 1.0a and it doesn't work in 2.0, and the recently
announced patch doesn't help.  Which printer type should be 
selected for the 'ty' printers entry?  All print jobs make it
to the printer, which terminates the print job with the message
"deleting current job".  Any pointers on this one would also
be appreciated.
  -- Chris