[lug] telnetd problem

[D. Stimits]

Chris Wade wrote:
> 
> > It might not be an error, but since the identd daemon should
> > be sending:
> > Escape character is '^]'.
> >
> > A proper termination to a session would be something similar to:
> > 0 , 0 : ERROR : UNKNOWN-ERROR
> 
> Sorry, forgot to mention that I do receive these messages when I go in
> through a shell from work, followed by 'Connection closed by foreign host.'
> >From SecureCRT on the laptop, I don't get 'Connected to...', 'Escape
> character is...' or 'Connection closed by...' but I think that's normal.  I
> do get the error message though, right before I'm disconnected.  On dos I
> just get nothing but a cursor, then when I type (no echo) and hit return I
> get disconnected: 'Connection to host lost.'

Nope, the connection portion is tcp/ip, not identd. auth may not matter,
but if it does, these are failure cases for auth.

> 
> > daemon. Assuming
> > you are using RH, run as root first a status check:
> > /etc/rc.d/init.d/identd status
> >
> > Assuming it is running, then stop it temporarily:
> > /etc/rc.d/init.d/identd stop
> >
> > Try your successful version again. If it fails to allow you in, you
> 
> Using SuSE.  Found identd, did this, I was still let in from work.  In fact,
> same results all around.
> (I'm actually telnetting using securecrt, no SSH.  Should have clarified.)

Next wold be to see if you can shut off identd from work. I have no idea
how to do this on the windows side...it is a mystery how to turn auth on
or off. It may be more trouble than it is worth to figure out how to
toggle windows' versio of auth, although you could simulate it by
blocking port 113.

> 
> > that the client end responds to identd requests. So also try the
> > reverse, though I'm not certain it will be any more than a subjective
> > clue: from the linux box, telnet to port 113 of the
> > connecting sources,
> > see if things work or fail as before.
> 
> Since the machine at work is behind a firewall, I can't telnet into it from
> outside.  No telnet daemon on the Windows box, either... any good ones out
> there? :)
> 
> I suspect that if I took this laptop to work and tried to connect to home
> from there, it would work fine.  Maybe I'll take it to work tomorrow and
> test this.

It seems that the firewalled end works, but local doesn't, so I doubt
even more that it is an auth problem...unless the firewall allows 113
but your local net doesn't. Wish I had more to suggest. You can turn up
debugging levels on most ssh clients though.

D. Stimits, stimits at idcomm.com

> 
> Thanks,
> 
> Chris
> 
> >
> > Before I confuse you with "maybe" suggestions, go ahead and give it a
> > try. I've wanted to turn on auth port in my Win 2k machine, but I've
> > never been able to figure out how to enable it. And the MS
> > site doesn't
> > give the information. I suppose auth port requires one to pay for a
> > third party package on win.
> >
> > D. Stimits, stimits at idcomm.com
> >
> > >
> > > Chris
> > >
> > > > -----Original Message-----
> > > > From: D. Stimits [mailto:stimits at idcomm.com]
> > > > Sent: Sunday, October 14, 2001 8:39 PM
> > > > To: lug at lug.boulder.co.us
> > > > Subject: Re: [lug] telnetd problem
> > > >
> > > >
> > > > Chris Wade wrote:
> > > > >
> > > > > I use SecureCRT at work to telnet from Win2000 to my Linux
> > > > machine at home.
> > > > > I've got a cable modem at home with a hub going off to the
> > > > linux machine and
> > > > > two windows laptops, all with separate IP addresses.  So
> > > > picture Cable
> > > > > Modem, Hub, then the three branching off from there... I
> > > > would like to have
> > > > > the laptops plus one macintosh going through the hub to the
> > > > linux box to the
> > > > > cable modem, but that's another issue.
> > > > >
> > > > > When I try to telnet now from my laptop to the linux box,
> > > > using its IP, I
> > > > > get 'telnetd: getnameinfo' and connection aborted, while at
> > > > work it works
> > > > > fine.  Any obvious reasons why this would be so?
> > > > >
> > > > > Thanks,
> > > > >
> > > > > Chris
> > > > > _______________________________________________
> > > > > Web Page:  http://lug.boulder.co.us
> > > > > Mailing List:
> > http://lists.lug.boulder.co.us/mailman/listinfo/lug
> > > >
> > > > Minor possibility, I'm not familiar with what the errors
> > would show up
> > > > as, but maybe it is an auth issue? From the location that
> > works, is it
> > > > possible to telnet to port 113 of the target machine for
> > cases that
> > > > work, but not able to do so from the location that fails? E.G.,
> > > > telnet 1.2.3.4 113
> > > > (if it allows connect, just type garbage and hit enter,
> > > > you've verified
> > > > auth is open)
> > > >
> > > > There's a good chance it has nothing to do with auth, but
> > sometimes
> > > > things are set to require it.
> > > >
> > > > D. Stimits, stimits at idcomm.com
> > > > _______________________________________________
> > > > Web Page:  http://lug.boulder.co.us
> > > > Mailing List: http://lists.lug.boulder.co.us/mailman/listinfo/lug
> > > >
> > > _______________________________________________
> > > Web Page:  http://lug.boulder.co.us
> > > Mailing List: http://lists.lug.boulder.co.us/mailman/listinfo/lug
> > _______________________________________________
> > Web Page:  http://lug.boulder.co.us
> > Mailing List: http://lists.lug.boulder.co.us/mailman/listinfo/lug
> >
> _______________________________________________
> Web Page:  http://lug.boulder.co.us
> Mailing List: http://lists.lug.boulder.co.us/mailman/listinfo/lug