Xref: utzoo comp.sys.dec:5779 comp.os.vms:38848
Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!mips!spool.mu.edu!news.cs.indiana.edu!noose.ecn.purdue.edu!mentor.cc.purdue.edu!WESTERM@aclcb.purdue.edu
From: westerm@aclcb.purdue.edu (Rick Westerman)
Newsgroups: comp.sys.dec,comp.os.vms
Subject: Re: Putting a modem on a LAT server
Message-ID: <00948BEC.8A7456C0@aclcb.purdue.edu>
Date: 17 May 91 20:27:40 GMT
References: <42405@cup.portal.com>
Sender: news@mentor.cc.purdue.edu
Reply-To: westerm@aclcb.purdue.edu (Rick Westerman)
Followup-To: comp.sys.dec
Distribution: na
Organization: Purdue AIDS center
Lines: 33


>Billy D'Augustine (Azog-Thoth@cup.portal.com) writes:
>
>I would like to attach a modem to our DECserver 200/mc, for the 
>purposes of dialing out, and have some questions regarding this...
>

I had constant trouble with this until I upgraded (last week) to
VMS 5.4-2 and LAT 5.4-2.  The new LAT allows you to specify outgoing
(from the VAX) connections to LAT services; e.g., the VAX can act like
a terminal server. Once you setup the VAX via LAT to be a terminal server,
you can then do a "set host/lat service_name" to get to the service. 

Pre-LAT 5.4-2 you could, in theory, have an outgoing connection that
would go to a specified terminal server and a specified port on the 
terminal server. Because I was using non-DEC terminal servers, the server's
name was not being accepted by the VAX (or not being generated properly
by the terminal server, I could never figure out which machine was the 
culprit) and thus I couldn't connect to the outgoing modems from my VAXen. 

Try using LATCP to setup outgoing connections and if that doesn't work,
upgrade to 5.4-2.




-- Rick

Rick Westerman                System Manager of the AIDS Center Laboratory
westerm@aclcb.purdue.edu      for Computational Biochemistry (ACLCB), BCHM
(317) 494-0505                bldg., Purdue University, W. Lafayette, IN 47907

                If you can't fight or flee, then flow.