telnet

[Ted Potter]

On Tue, 2005-03-29 at 09:23, roland brouwers wrote:
> roland brouwers wrote:
> > I have a server with FD3
> > I want to telnet from the workstations to this server.
> > We have WS with Xppro, Win98 an WinMe
> > Everything goes well with XP and W98
> > With WinMe, the workstation hangs after login and the display of
> > lastlogin
> > If I enter Ctrl+C, I get into the shell and I can continue manually.
> > I don't find any firewall on the pc's. I disabled Norton virus, it has
> > no firewall.
> > What does Me that XP an W98 don't?
> 
> First off, using telnet is a bad idea as it is completely insecure
> (everything including passwords are sent in cleartext).  This isn't an
> issue if your network has no gateway to the internet, but I'd highly
> recommend you stop using telnet and use ssh.  There are a number of free
> ssh clients for Windows, the most popular being "putty".  Do a google
> search for that, install it and use it.  Disable telnet completely.
> 
> Now, as to why ME behaves differently, I suspect it has to do with the
> terminal emulation in its telnet protocol.  One of the last things a
> login does is set the prompt string and many systems will "eat" the
> first prompt, just due to the way they set up the connections.  I'll bet
> that it's not necessary for a "CTRL-C", but a simple "ENTER" would get
> you the prompt.
> 
> Can you fix it?  Probably not.
> --------------------------------------------------->
> As I told you before "ENTER" doesn't work and it is getting worse. It is
> like eating my network. More and more workstations, even XP are waiting
> on telnet. If you wait long enough they continue. Some workstations that
> hat this problem do not anymore. What is this, PACKMAN?
> I replaced WinME with XP, but the same problem stays. 
> I thought it was Norton, so I deinstalled it. But nothing happened.
>  
> I worked for months to convince the client to change from Winserver to
> Linux and now I am stucked.
> 
> Has anyone some brillant idea or something that is near to brillant.
> 
> Thanks for your thoughts.
> roland
> 
It's beginning to sound more like a network issue. Or perhaps the telnet
server has a limit to the number of connections it allows. I note that
first we thought XP and 98 worked but now it seems all clients are
having the issue.

Someone with more experience in networking than I should jump in, but
first things first. Test for dropped packets with a ping test from the
client. Inspect your physical connections. Telnet from a windows machine
to a *nix machine is nothing new so we are not inventing the wheel here.

Oh yes, please do use puty. It is your friend.

I am sure there is a way to log the events on the server side but what
that is I do not know now.


hth

Ted