This may be a really dumb suggestion -- but have you considered using the Win2K telnet server, and running bash once you're logged in?
Andrew. On Sat, 14 Jun 2003 Brian dot Kelly at Empireblue dot com wrote: > Date: Sat, 14 Jun 2003 06:26:42 -0400 > From: [EMAIL PROTECTED] > To: [EMAIL PROTECTED] > Subject: Native Microsoft Telnet Client Blows Past the Password Prompt > > 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. > > 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! > > Are these known problems, or am I missing something "REALLY" simple here? > Is there something I can change to fix this? For AIX or MS 2000? > > Brian Kelly > > > > > "WellChoice, Inc." made the following > annotations on 06/14/2003 06:28:23 AM > ------------------------------------------------------------------------------ > Attention! This electronic message contains information that may be legally > confidential and/or privileged. The information is intended solely for the > individual or entity named above and access by anyone else is unauthorized. > If you are not the intended recipient, any disclosure, copying, distribution, > or use of the contents of this information is prohibited and may be unlawful. > If you have received this electronic transmission in error, please reply > immediately to the sender that you have received the message in error, and > delete it. Release/Disclosure Statement > > -- 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/
