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

["Brian Kelly" <brian dot m dot kelly at verizon dot net>]

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/