Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Slow telnet and ftp login response

Status
Not open for further replies.

mrberry

MIS
Jun 15, 2004
80
US
I have 3 AIX servers, 2 of which exhibit this problem and 1 does not.

On the 2 problem hosts when I telnet or ftp from a PC running XP it just sits there for about 60 seconds. On a telnet I eventually get a prompt and can login. With ftp I get the connected to host message, but never get a login prompt - just a "connection closed by remote host" message after about 60 seconds.

This problem does not occur when I telnet or ftp between the AIX hosts.

I seem to remeber that you have to set the duplex setting in the network interface to resolve such a problem, but could be wrong. I can't find where to set this anyway.

Does anyone know a solution to this problem?

Thanks

Mark
 
I forgot to mention on the 2 problem servers we are using a virtual network interface to load balance 2 physical interface cards.

The working host only uses a single network card.

Thanks

Mark
 
smitty dev->communication->Ethernet Adapter->Adapter->
Change / Show Characteristics of an Ethernet Adapter

then pick the correct interface you want to modify, the 'Media Speed' attirbute is the one to look at, but i have no idea if that's your real problem. you'll have to apply change to database only, then boot, or down the interface and bring it back up.

you can skip smit and use chdev from the CLI if so inclined.
 
We have issues like this a lot. Usually ends up that the port on the switch is mis-matched from the machine (either Unix server or PC). Our machines are 100M Full, but the network is usually set to auto-negotiate. Transfers are always slow and we get a bunch of errors. Once our network guys change the switch port to 100M Full, it works well again. I guess I would expect the auto-negotiate to work, but it never does in our case.

Tim
 
OK, after some investigation this problem has been found to be related to name resolution and the fact that the PC's on our network (like most corporate networks today) uses DCHP.

In the /etc/inetd.conf if you add a -c option (which by the way appears to be undocumented) to telnetd and do an inetd refresh it resolves my telnet issue. There is also a -c option for ftpd, but this only half solves my problem: there is a delay but I so now eventually get a login prompt.

If I remove my resolv.conf file this solves the problem for both telnet and ftp. (incidently the reason why inter-unix ftp and telnet worked was becasue they had definitions in the /etc/hosts file).

So now I need to talk to my Windows admin to find out why DHCP assigned addresses are not being resolved.

Thanks to all those that replied.

Mark

 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top