[Search for users]
[Overall Top Noters]
[List of all Conferences]
[Download this site]
Title: | DEChub/HUBwatch/PROBEwatch CONFERENCE |
Notice: | Firmware -2, Doc -3, Power -4, HW kits -5, firm load -6&7 |
Moderator: | NETCAD::COLELLA DT |
|
Created: | Wed Nov 13 1991 |
Last Modified: | Fri Jun 06 1997 |
Last Successful Update: | Fri Jun 06 1997 |
Number of topics: | 4455 |
Total number of notes: | 16761 |
1710.0. "Need a serial line security device" by CENPCS::BIRMINGHAM (Transporter Room - 1 to beam up...) Sun Nov 20 1994 16:34
I have a customer who is using the DS90M and a MUXserver 380 acting as a
TELNET/LAT Gayeway to provide connectivity from remote locations to a
OpenVMS CLuster over both a Token-Ring and Frame Relay backbone. The
Cluster and the MUX380's are on the Ethernet backbone, the routers are
Cisco. A remote DS90M user TELNETs to the Muxserver 380 at the Port
number assigned for the Cluster alias, and get a load-balanced LAT
connection into the cluster. The connections work just fine.
The customer has certain locations that are secured in a locked room,
and the application is set up to grant certain privileges based on the
terminal's location. The problem we have is that when we come to the
Cluster using TELNET ( the Cluster also runs TCP/IP Services for VMS ),
the result of a SHOW TERM ( or F$GETDVI("tt:","TT_ACCPORNAM') ) shows
the IP address of the DS90M but does not indicate the port name. We
understand that the TELNET protocol is not capable of providing this
the way a LAT connection does. When the same user TELNETs to the
MUXserver at the Cluster Alias port number and gets the LAT connection,
the SHOW TERMINAL and the Lexical function show 'MUXSERVER/TELNET_x' as
the port name. TENLET_x doesn't indicate either the server port name or
the IP address of the original user.
The customer will not accept setting the VT420's Answerback to the
location code and locking out setup, or using a ROM answerback device
on the printer port. What we need is a way to determine the terminal's
location, either by query from the Cluster in a programmatic fashion,
or by using am answerback device physically connected into the wiring
at the terminal that cannot be removed.
Can ayone suggest a way that we can create a secure identity mechanism
for terminals connected in the fashion I have described ? Any
suggestions, pointers, or names of companies producing a serial
answerback device will be greatly appreciated.
Regards,
George Birmingham
Cross posted in the Terminal_servers Notes Conference (#2056)
T.R | Title | User | Personal Name | Date | Lines |
---|
1710.2 | How does this apply to my original question ? | CENPCS::BIRMINGHAM | Transporter Room - 1 to beam up... | Mon Nov 21 1994 10:44 | 3 |
| Huh ?
|
1710.3 | oups error | SZAJBA::PEYRACHE | Jean-Yves Peyrache Country Support Group France | Mon Nov 21 1994 11:33 | 5 |
| re-1
sorry bad select under notes
jean-yves
|
1710.4 | Try the terminal servers notes conference | SLINK::HOOD | I'd rather be at the Penobscot | Mon Nov 21 1994 11:50 | 3 |
| Try the TOOK::TERMINAL_SERVERS conference.
Tom
|
1710.5 | Been there, done it... | CENPCS::BIRMINGHAM | Transporter Room - 1 to beam up... | Mon Nov 21 1994 16:15 | 3 |
| Already did. See note #2056.
GB :-)
|