From:	CRDGW2::CRDGW2::MRGATE::"SMTP::CRVAX.SRI.COM::RELAY-INFO-VAX" 29-JUN-1989 16:22
To:	MRGATE::"ARISIA::EVERHART"
Subj:	Re: Telnet restrictions

Message-Id:  <8906292009.AA24720@crdgw1.ge.com>
Received: From KL.SRI.COM by CRVAX.SRI.COM with TCP; Thu, 29 JUN 89 11:04:54 PDT
Received: from twg.com by KL.SRI.COM with TCP; Thu, 29 Jun 89 10:59:37 PDT
Received: from ecovax.twg.com by twg.com with SMTP ; 
          Thu, 29 Jun 89 04:48:54 PDT
Date: 29 Jun 89 07:48:00 EDT
From: "RANDY CATOE" <randy@TWG.COM>
Subject: Re: Telnet restrictions
To: "info-vax" <info-vax@kl.sri.com>

>From: ijah400@indyvax.ics.indiana.edu
>Subject: RE: TCP/IP and restricting access to Telnet and FTP servers
>To: info-vax <info-vax@kl.sri.com>
>Message-ID:  <8906281620.ac24537@Obelix.TWG.COM>
>
>Finally, thanks to David Jones of Ohio State University for giving me the
>workaround for my problem.  The Wollongong software stuffs the IP address of
>the client end of the connection into the UCB of the NTY terminal device,
>with the octets in "network order" in a longword starting at offset (hex)
>13C under VMS V4.x, or offset (hex) 16C under VMS V5.x.  This offset is
>not defined or documented in Wollongong's header files for UCB definitions.
>So, programs using it could probably break with any new release WIN/TCP.
>
>     - Jim
---
Jim,

 This offset will be named and documented in the next release of WIN/TCP and 
will remain so in future releases.
 
Thank you and David Jones for pointing it out. 

J.R. Catoe
The Wollongong Group, Inc.


