Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com X-Info: This message was accepted for relay by smtp03.mrf.mail.rcn.net as the sender used SMTP authentication X-Trace: UmFuZG9tSVaha3RmiFdt8VA9zGPGAwlAoalIkX0sQcFJR9bUKYU8TOcy+Wyi054K Message-ID: <3EEB44FA.1080005@cygwin.com> Date: Sat, 14 Jun 2003 11:53:30 -0400 From: Larry Hall Reply-To: cygwin AT cygwin DOT com User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030529 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Brian DOT Kelly AT Empireblue DOT com CC: cygwin AT cygwin DOT com Subject: Re: Native Microsoft Telnet Client Blows Past the Password Prompt References: In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Brian DOT Kelly AT Empireblue DOT com wrote: > I've looked through the archives and have not seen a write-up on this. I > have the very latest cygwin everything installed on an MS 2000 Server. > TERM=cygwin is set in the profile. Running the telnetd daemon with > inetutils. I have absolutely no problems connecting to this service with > any client program except the native one that comes with every copy of MS > 2000. The native one that comes with every earlier copy of MS Windows - 95, > 98, NT4 works just fine. When I use the Native MS 2000 telnet I get the > following output: > > > CYGWIN_NT-5.0 1.3.22(0.78/3/2) (*******************) (tty2) > > login: mylogin > > Password: > Login incorrect > login: > > > Essentially, it just blows right past the password prompt without pausing - > apparently taking null as the password. This renders the MS 2000 Telnet > client completely useless for direct telneting. For most I imagine this not > a problem or even annoyance because probably just about every other client > in existance works just fine. The problem for me, is that I work for a > large organization, and I like the flexibility of being able to plop down > at desktop anywhere - more than 5000 desktops - and telnet to any of the > servers I manage and run scripts, do diagnosis, etc. On 98% of these > machines, MS 2000 telnet client is the ONLY client available, and I do not > have the right to install a different one whenever I want one (not to > mention the inconvenience even if I could). Currently, I work around this > by logging into an AIX box (which has it's own set of telnet-to-cygwin > woes) and then from there to my cygwin/MS 2000 boxes. This is a known issue. Thus far, no one has been interested enough in the problem to find workarounds or solutions. Like you said, it's only a problem with MS's telnet client so it's quite possibly a bug there. You might want to bug MS about it. > And since I did mention AIX, if one telnets to a cygwin box from the NATIVE > AIX telnet client, AIX does NOT display anything typed at the command line. > It receives it, and you can get output (after you press enter) and run > commands, etc. But not seeing what you're typing while you're typing it is > QUITE a headache. Now I know AIX is the one of the most reviled and avoided > OS's amongst the open source community. More than once I've encountered not > only disinterest - but almost what could be called PRIDE that this, that or > the other does not run on AIX. Nevertheless, one of the conundrums of my > existance is that AIX is what I am saddled with - not just with my current > employer, but 3 out of the last 5! Sounds to me like AIX doesn't understand the cygwin terminal type. Have you tried moving your cygwin terminal definition over to AIX or switching your terminal type once you log into the AIX machine? -- Larry Hall http://www.rfk.com RFK Partners, Inc. (508) 893-9779 - RFK Office 838 Washington Street (508) 893-9889 - FAX Holliston, MA 01746 -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/