Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!uwm.edu!bionet!agate!usenet.ins.cwru.edu!slc6!lim From: lim@slc6.INS.CWRU.Edu (Hock Koon Lim) Newsgroups: comp.dcom.sys.cisco Subject: Re: unusual terminal server need Message-ID: <1991Mar19.151329.14327@usenet.ins.cwru.edu> Date: 19 Mar 91 15:13:29 GMT References: <33075@boulder.Colorado.EDU> Sender: news@usenet.ins.cwru.edu Reply-To: lim@po.CWRU.Edu Organization: Case Western Reserve Univ. Cleveland, Ohio, (USA) Lines: 35 Nntp-Posting-Host: slc6.ins.cwru.edu In article <33075@boulder.Colorado.EDU> BILLW@mathom.cisco.com (WilliamChops Westfield) writes: > >I don't know that I'd say that "most terminal servers dont support >incoming telnet" - I know of few that don't. I like to think that we >do it better than many - for example, you can limit which systems can >connect to a port, and require them to provide a username/password >before they actually get to send data to the port (handy both for >security, AND for figuring out who is using that port when someone >else needs it!) Check in your terminal server manual under 'configuring >non-terminal devices". I know cisco terminal server can configured with username/password for "incomming connection" to a port. I am unable to configure it to ask for username/password in the "out going" connection like reverse tcp service. Am I doing something wrong? Another point of interest on SLIP implementation on cisco terminal server. On current configuration for SLIP line, each port is associated with an IP address. If you set it these ports on the modem pool for imcomming connection, users will pick up an IP address which associated with that particular port. I would like to be able to do username/password and then assign an IP number that this associated with the username. Will cisco plan to support this kind of configuration in the future? >Bill Westfield >cisco Systems. >------- Thanks, -- Hock-Koon Lim, Information Network services Case Western Reserve University; Cleveland, Ohio, USA 44106 (216) 368-2982 lim@ins.cwru.edu