Native Microsoft Telnet Client Blows Past the Password Prompt

Native Microsoft Telnet Client Blows Past the Password Prompt

[Brian.Kelly]

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/

Re: Native Microsoft Telnet Client Blows Past the Password Prompt

[Larry Hall]

Brian.Kelly@Empireblue.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/

Re: Native Microsoft Telnet Client Blows Past the Password Prompt

[Thorsten Kampe]

* Brian.Kelly@Empireblue.com (2003-06-14 12:26 +0200)
> 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:
> [...]
> 
> 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.

Jesus, it's 2003 and you're telnetting into your servers...

> Are these known problems, or am I missing something "REALLY" simple here?
> Is there something I can change to fix this?

unset ntlm

Thorsten
-- 
 Content-Type: text/explicit; charset=ISO-8859-666 (Parental Advisory)
 Content-Transfer-Warning: message contains innuendos not suited for
 children under the age of 18


--
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/

RE: Native Microsoft Telnet Client Blows Past the Password Prompt

[Brian Kelly]

uhhh - that's "MR CHRIST" to you sir. Yes OF COURSE I telnet to my
servers. I do so inside a secure network from desktops that are locked
down tighter than gold in Swiss Banks. Since I don't have every little
thing browser enabled on my servers, and IT has not seen fit to
distribute Putty to every desktop, just how pray tell do you suggest I
get to them from the CEO's secretary's desktop????????? Heck I can't
even use "run" at the start menu to start telnet - they have that
disabled as well. I have to start a cmd window and do it from there. Not
of all us work for Red Hat or live off of university grants or own our
own software firm. Some of us have to take orders from folks who know a
heck of a lot less technically than we do, and who are five times more
paranoid about letting employees even use the calculator bundled with
Windows. My use of "Cygwin" itself on corporate servers is "unofficial"
and "unsupported" and exists only with wink and nod approval by managers
who will disavow all knowledge if ever asked by the wrong people. But in
this "brave new economy" new software budgets are becoming smaller than
the price of a Happy Meal at McDonald's. So the managers in the know are
secretly VERY thankful for software like cygwin that with a little
ingenuity and resourcefulness can do the job that otherwise would
require ten's or even hundred's of thousands of dollars spent on third
party software - with all the attendant license's, maintenance, etc etc
etc. In fact some sanctioned software is being discreetly discarded for
open source because no can find $10,000 for a maintenance renewal.

Yes - it's 2003 my friend - but try explaining that to a "technical
lead" who interrupts you mid-sentence and asks you with child-like
naivety:

	What's ping??

Anyway - thank's for the advice, I'll play with it and see if I get the
desired result.

BK

-----Original Message-----
From: cygwin-owner@cygwin.com [mailto:cygwin-owner@cygwin.com] On Behalf
Of Thorsten Kampe
Sent: Saturday, June 14, 2003 6:49 PM
To: cygwin@cygwin.com
Subject: Re: Native Microsoft Telnet Client Blows Past the Password
Prompt

* Brian.Kelly@Empireblue.com (2003-06-14 12:26 +0200)
> 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:
> [...]
> 
> 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.

Jesus, it's 2003 and you're telnetting into your servers...

> Are these known problems, or am I missing something "REALLY" simple
here?
> Is there something I can change to fix this?

unset ntlm

Thorsten
-- 
 Content-Type: text/explicit; charset=ISO-8859-666 (Parental Advisory)
 Content-Transfer-Warning: message contains innuendos not suited for
 children under the age of 18


--
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/


--
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/

Partial Solution! - Native Microsoft Telnet Client Blows Past the Password Prompt

[Brian Kelly]

Sooo, competing for a "FREE" copy of CYGWIN!, whose advice was the REAL
solution???

Was it KIA #1   -    Richard Campbell	unset crlf

or     KIA #2   -    Thorsten Kampe		unset ntlm


And the Winner is ..............  RICHARD CAMPBELL!!!  Ding Ding DING!!

KIA???	Richard Campbell  - "Know it All"
		Thorsten Kampe	- "Killed in Action"  ( a WAGer?? )

Nevertheless the efforts of both were much appreciated!

COMPLETE INSTRUCTIONS FOR FUTURE ARCHIVE SURFERS LIKE ME WKN
(Who Know Nothing)

At Start Menu Run, or in a CMD window, type "telnet" and hit enter.
One should see this:

	Microsoft (R) Windows 2000 (TM) Version 5.00 (Build 2195)
	Welcome to Microsoft Telnet Client
	Telnet Client Build 5.00.99206.1

	Escape Character is 'CTRL+]'

	Microsoft Telnet>

At the prompt ( Microsoft Telnet> ) type:

	unset crlf<ENTER>

Then type   quit   to exit.

Again - Thanks to Richard Campbell.

Now for my UAU (unsolicited and unwanted) RANT. It is only a "partial"
solution because the default setting for millions of 2000 telnet clients
around the globe is incompatible with Cygwin. And of course, unless
someone "knows" the "simple" solution above - they are outta luck. Of
course brain surgery is "simple" if you know how to do it. So why isn't
it fixed yet??

BWAM

I understand, really I do ;-)

BK



  
-----Original Message-----
From: cygwin-owner@cygwin.com [mailto:cygwin-owner@cygwin.com] On Behalf
Of Brian Kelly
Sent: Saturday, June 14, 2003 11:13 PM
To: cygwin@cygwin.com
Subject: RE: Native Microsoft Telnet Client Blows Past the Password
Prompt

uhhh - that's "MR CHRIST" to you sir. Yes OF COURSE I telnet to my
servers. I do so inside a secure network from desktops that are locked
down tighter than gold in Swiss Banks. Since I don't have every little
thing browser enabled on my servers, and IT has not seen fit to
distribute Putty to every desktop, just how pray tell do you suggest I
get to them from the CEO's secretary's desktop????????? Heck I can't
even use "run" at the start menu to start telnet - they have that
disabled as well. I have to start a cmd window and do it from there. Not
of all us work for Red Hat or live off of university grants or own our
own software firm. Some of us have to take orders from folks who know a
heck of a lot less technically than we do, and who are five times more
paranoid about letting employees even use the calculator bundled with
Windows. My use of "Cygwin" itself on corporate servers is "unofficial"
and "unsupported" and exists only with wink and nod approval by managers
who will disavow all knowledge if ever asked by the wrong people. But in
this "brave new economy" new software budgets are becoming smaller than
the price of a Happy Meal at McDonald's. So the managers in the know are
secretly VERY thankful for software like cygwin that with a little
ingenuity and resourcefulness can do the job that otherwise would
require ten's or even hundred's of thousands of dollars spent on third
party software - with all the attendant license's, maintenance, etc etc
etc. In fact some sanctioned software is being discreetly discarded for
open source because no can find $10,000 for a maintenance renewal.

Yes - it's 2003 my friend - but try explaining that to a "technical
lead" who interrupts you mid-sentence and asks you with child-like
naivety:

	What's ping??

Anyway - thank's for the advice, I'll play with it and see if I get the
desired result.

BK

-----Original Message-----
From: cygwin-owner@cygwin.com [mailto:cygwin-owner@cygwin.com] On Behalf
Of Thorsten Kampe
Sent: Saturday, June 14, 2003 6:49 PM
To: cygwin@cygwin.com
Subject: Re: Native Microsoft Telnet Client Blows Past the Password
Prompt

* Brian.Kelly@Empireblue.com (2003-06-14 12:26 +0200)
> 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:
> [...]
> 
> 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.

Jesus, it's 2003 and you're telnetting into your servers...

> Are these known problems, or am I missing something "REALLY" simple
here?
> Is there something I can change to fix this?

unset ntlm

Thorsten
-- 
 Content-Type: text/explicit; charset=ISO-8859-666 (Parental Advisory)
 Content-Transfer-Warning: message contains innuendos not suited for
 children under the age of 18


--
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/


--
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/


--
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/

Re: Native Microsoft Telnet Client Blows Past the Password Prompt

[andrew brian clegg]

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: Brian.Kelly@Empireblue.com
> To: cygwin@cygwin.com
> 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/

RE: Native Microsoft Telnet Client Blows Past the Password Prompt

[Richard Campbell]

> 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. 

I have had this problem.  IIRC, the "unset crlf" option was what
I needed to do, to change the return key from sending "crlf" to 
"cr".

I only have 2000 at work, though, so I can't test it now.

-Richard Campbell.

--
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/