[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference netcad::hub_mgnt

Title:	DEChub/HUBwatch/PROBEwatch CONFERENCE
Notice:	Firmware -2, Doc -3, Power -4, HW kits -5, firm load -6&7
Moderator:	NETCAD::COLELLADT

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

598.0. "Telnet on DEChub" by SAHQ::TROTTER () Fri Jan 07 1994 11:15

    Does the new terminal server for the DEChub 900 have the ability to
    address specific ports via Telenet?  Sort of like reverse LAT when you
    want to assign a specific address because the device connected doesn't
    have a keyboard.
    
    A healthcare systems provider is considering using the DEChub if we
    have this sort of functionality.

T.R Title User Personal
Name Date Lines

598.1 In a nutshell... TOOK::D_NELSON Dave Nelson LKG1-3/A11 226-5358 Fri Jan 07 1994 13:20 12

T.R	Title	User	Personal Name	Date	Lines
598.1	In a nutshell...	TOOK::D_NELSON	Dave Nelson LKG1-3/A11 226-5358	`Fri Jan 07 1994 13:20`	12
	RE: .0 There is discussion of this in TOOK::TERMINAL_SERVERS. The short answer is that for non-network-peers (simple Telnet listener) you distinguish physical async ports by TCP port number. They all share the same IP address. For network devices (via SLIP, CSLIP, PPP) each async port must have a distinct IP address. Regards, Dave

    RE: .0
    
    There is discussion of this in TOOK::TERMINAL_SERVERS.  The short
    answer is that for non-network-peers (simple Telnet listener) you
    distinguish physical async ports by TCP port number.  They all share
    the same IP address.  For network devices (via SLIP, CSLIP, PPP) each
    async port must have a distinct IP address.
    
    Regards,
    
    Dave