Xref: utzoo comp.protocols.tcp-ip:5045 comp.os.vms:9714
Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!mailrus!ames!elroy!suned1!efb
From: efb@suned1.UUCP (Everett F. Batey II)
Newsgroups: comp.protocols.tcp-ip,comp.os.vms
Subject: CMU and WIN not talking, ideas?
Summary: Installing new standalones, cant talk
Message-ID: <848@suned1.UUCP>
Date: 31 Oct 88 06:06:26 GMT
Reply-To: suned1!efb@elroy.JPL.Nasa.Gov (Everett F. Batey II)
Distribution: na
Organization: NSWSES 4V43 Port Hueneme, CA 93043 - Opinions: Mine Alone
Lines: 17
Phones: 805/982-5881 (A/v: 360) Res: 983-1220 (Ans)
Groups: SOCAL SUN Local User Group / DECUS Santa Barbara / Ventura / SLO

Just incorporated TCP/IP packages on two VMS 4.6 MicroVAX IIs.  They are now
DEQNA to DEQNA (FCO looks current).  DECNET (FULL to END) works.  We are try-
ing to get them running but don't yet have external Internet or other hosts to
talk to.  Each currently can do loopbacks ( me, myhostname, myhostnumber ) but
both CMU 6.3 and WIN_TCP 3.2 complain of timeout.  Yes DECNET was started FIRST.

Both products were installed by the book.  They only fail when attempting to
talk OFF-HOST.

Would anyone care to suggest some tips to troubleshoot this problem .. no 
third ethernet device .. no network analyzer.  Ideas greatly appreciated

/Ev/
-- 
           The_Main_User (So Calif SunLUG | Vta-SB-SLO-DECUS)
    efb@elroy.JPL.Nasa.Gov sun!tsunami!suned1!efb efbatey@nswses.arpa
      Statements, Opinions ... MINE ... NOT those of my US Employer