I think that you get that behaviour if /etc/inetd.conf specifies
/usr/sbin/tcpd as the server path, and it is missing.

Regards,
/Karl

-----------------------------------------------------------------------
Karl Hammar                    Aspö Data           [EMAIL PROTECTED]
Lilla Aspö 2340             +46  173 140 57                    Networks
S-742 94 Östhammar         +46  10 270 26 67                  Computers
Sweden                                                       Consulting
-----------------------------------------------------------------------

From: Jon Stanley <[EMAIL PROTECTED]>
Subject: Telnet problems after massive update
Date: Mon, 27 Aug 2001 00:01:55 -0500

> I was on the testing branch for awhile, then my bro took over the machine and 
> I lost the root password.  At any rate, I now have the root passwd again and 
> went to do an update.  Finding that there were massive things to be upgraded, 
> I went ahead and did them.  After this, I lost telnet access into the box.  
> Not that big of a deal for me, I use SSH.  But my bro insists on being able 
> to use telnet for some odd and strange reason.  At any rate, the brokeness of 
> telnet is somewhat of a big deal.  Anyhow, here is what happens:
> 
> [EMAIL PROTECTED] /home]$ telnet <hostname>
> Trying xxx.xxx.xxx.xxx ...
> Connected to xxx.xxx.xxx.xxx.
> Escape character is '^]'.
> Debian GNU/Linux testing/unstable xxx.xxx.xxx
> Connection closed by foreign host.
> [EMAIL PROTECTED] /home]$
> 
> There are no access controls that I know of - looking at the logs just shows 
> successful telnet connections.  A glance at hosts.allow and hosts.deny are 
> unrevealing (Wouldn't get that far into it anyway, with the banner).  
> Manually executing /bin/login at the command line gives the expected results 
> and I am able to successfully authenticate.  I'm not quite sure how to debug 
> whether login is getting called or not, or where in the process this is 
> dying.  Any help would be appreciated.  Thanks
> 
> 
> -- 
> To UNSUBSCRIBE, email to [EMAIL PROTECTED]
> with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to