Xref: utzoo comp.protocols.tcp-ip:6609 comp.sys.encore:184
Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!uflorida!haven!h.cs.wvu.wvnet.edu!wvucoe!manager
From: manager@a.coe.wvu.wvnet.edu (Cris Fuhrman, Systems Manager)
Newsgroups: comp.protocols.tcp-ip,comp.sys.encore
Subject: An Annex by any other nameserver would smell...
Message-ID: <68@a.coe.wvu.wvnet.edu>
Date: 27 Mar 89 19:12:15 GMT
Lines: 37

Salut,

We have 3 Annex Terminal servers, connected via TCP/IP to our ethernet.  
The problem concerns the handling of host names.  Here's what happens:

After a server boots, one can access nodes outside of our local domain 
(i.e. outside of .wvnet.edu).  However, after a period of time, if one 
tries to access even the same node as before, the address is resolved, and 
the internet number is added to the cache hosts table, but the Annex 
responds with (an immediate response, i.e. no delay)

    Trying...
    CLI: Network is unreachable.

As I said, the nameserver features appear to be working, and in fact our 
ethernet is working, as I can telnet to remote hosts right after a boot.

Anyone have any input on this one?

Also, I have some related questions:

    1)  What's the difference between BIND, IEN_116, and RWOD name servers?
    2)  Are the RWOD machines the ones that show up in the hosts table with
        a system load factor?

I have a couple of other minor questions about Annex configurations in 
general, and I'd like to pick someone's brain about them if they'd be 
willing to exchange some info.

-Cris
-- 
  /''''--''''''''''''''''.  Cris Fuhrman, Systems Manager''''''''''''''/
 /    /  \               .  WVU College of Engineering                /
<    |      __   o       .  Morgantown WV 26506-6101                 <
 \   |     )  |  |  /\   .  internet:  manager@a.coe.wvu.wvnet.edu    \
  \...\___/...|_/|_/__).....bitnet:....manager%wvucoe@wvnvms...........\
              Plus ca change, plus c'est la meme chose.