Path: utzoo!attcan!uunet!mcvax!enea!maxim!prc From: prc@maxim.ERBE.SE (Robert Claeson) Newsgroups: comp.dcom.lans Subject: Re: Ethernet terminal servers Message-ID: <459@maxim.ERBE.SE> Date: 17 Jan 89 21:25:45 GMT References: <6556@fluke.COM> <405@ccd700.UUCP> Organization: ERBE DATA AB Lines: 36 In article <405@ccd700.UUCP>, reh@ccd700.UUCP (reh) writes: > We have a VAX 8700 with a couple terminal servers, and users logged > into the VAX thru the terminal server are assigned virtual terminal > names. This is because the server is capable of allowing the user > to have multiple sessions from the same server port. The problem > is that the host has no way of finding the physical port that the > user is connected to. This makes it frustrating to debug bad ports > or locate users. Is there any way to find out the physical port > that a user is on? It depends on what terminal servers you're using. If you have Encore's Annex terminal servers, you can create pty's (assuming you run UNIX) on the host that are tied to ports on the servers and let the host put a getty on that port. But then you cannot open multiple sessions. Or, you can have the Annex log all connections. It can use either the syslog facility on your host or its own log, or both. I do hope someone can get their act together and standardize on a consistent remote terminal or pty numbering scheme. Encore has done this with Annex'es connected to their own computers, the Multimax'es (provided you use their own distributed tty interface), and I guess that DEC has done something similar with their own LAT remote tty protocol. Disclaimer: Any opinions expressed in this article is solely those of my own. My employer might share them, but don't bet it. If you want to quote this article, please include this disclaimer. -- Robert Claeson, ERBE DATA AB, P.O. Box 77, S-175 22 Jarfalla, Sweden "No problems." -- Alf Tel: +46 758-202 50 EUnet: rclaeson@ERBE.SE uucp: uunet!erbe.se!rclaeson Fax: +46 758-197 20 Internet: rclaeson@ERBE.SE BITNET: rclaeson@ERBE.SE