Xref: utzoo comp.sys.dec.micro:1911 comp.sys.dec:5846
Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!think.com!zaphod.mps.ohio-state.edu!caen!kuhub.cc.ukans.edu!mcginnis
From: mcginnis@kuhub.cc.ukans.edu
Newsgroups: comp.sys.dec.micro,comp.sys.dec
Subject: Solution to PathWorks hanging server's DECnet... Thanks
Message-ID: <1991May28.080504.31094@kuhub.cc.ukans.edu>
Date: 28 May 91 08:05:04 CDT
Organization: University of Kansas Academic Computing Services
Lines: 10

Thank you for your replies to my posting about my PathWorks for DOS
client killing DECnet on our server (VAX).  The NETSETUP utility 
that configures the client PC requests only one DECnet node name
and address; that for the "file server".  I don't know why it didn't
seem strange to me that it never asked for the client or PC node
name and address.  NETSETUP gave the client the DECnet node name 
and address of the server and when the client started up DECnet
the servers DECnet would choke.

Thanks again.