home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.sys.att
- Path: sparky!uunet!zaphod.mps.ohio-state.edu!magnus.acs.ohio-state.edu!usenet.ins.cwru.edu!news.csuohio.edu!vmcms.csuohio.edu!R1004
- From: R1004@vmcms.csuohio.edu
- Subject: Starlan Problem solved (?)
- Message-ID: <16847DB72.R1004@vmcms.csuohio.edu>
- Sender: news@news.csuohio.edu (USENET News System)
- Organization: CSU
- Date: Tue, 18 Aug 1992 20:36:18 GMT
- Lines: 30
-
- Greetings,
-
- I hope this information helps someone else out there - took
- me a long time to get the problem solved. Here goes...
-
-
- This will only help if you are running StarGROUP *and* WIN TCP
- on your machine. The problem was the StarLAN listener croaking
- and refusing to come back to life due to a corrupt address of some
- sort.
-
- It turns out that my machine's IP address in
- /usr/net/nls/tcp/addr was not the same as in /etc/hosts (and
- elsewhere?) The addr file did not get updated when we had
- to change IP addresses some time ago. I never had much of
- a problem with TCP/IP inbound or outbound (except for a few
- machines I just couldn't talk to - I've not tried those since
- the fix went in) Anyways somehow that was botching up starlan.
- The NCR people were at a loss to explain why.
-
- So far I have been unable to mess up the machine, but I'm sure
- that will change! 8-)
-
- Hope this helps someone out there.
- ------------------------------------------------------------------------
- Bob Martel |
- bob2@cua3.csuohio.edu | Lady luck must have been a wonderful girl
- R1004@vmcms.csuohio.edu | -She's never been a friend of mine!
- | Alan Parsons Project
- --------------------------------------------------------------------------
-