Discussion Locked

Very odd telnet problem

0 helpful
7 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
Our critical app runs off an IBM AIX box, accessed through telnet. We're having scattered, intermittent telnet hangs throughout our local network. 6 other locations on our WAN are not experiencing the problem, so it's only within the LAN. After telnet hang, pinging the server results in request timed out, but you can see and use everything else on the network. Problem seems to disappear after a random amount of time no longer than 15 mins. Please note that, while one user is hung, others are working fine - it doesn't hang everybody at once. On our LAN, we have 8 3com 10/100 hubs. 5 are connected by cascade cables in back, and 3 are connected by crossovers in front. Problem seems to affect users on ALL hubs, including the one the server is on. Problem has been occurring for about 2 weeks, and we have NOT had a recent, significant increase in LAN users. Please don't hesitate to ask for more information, and I thank anyone who considers this.

7 replies

by gutridgesj

on the hub side, i would check to see if a hub is messed up and i would not expect the one the server is on since others users are still on when it happens to some.
when things are normal, i would look at the hubs to see what lights are on. when the problem occurs, i would go to the hubs and see if any other lights or any other things that did not look normal on the hubs.

is there anything in common with the users that are having the problem? is it the same users?

try switching the server to another port on another hub. and also for the user that is having the problem when it occurs.

Could it be that there is a dupe IP address somewhere? so when the problem occurs, other pcs can ping the server? can other pcs ping the pc in question?

is it just one pc at a time that is hung or multiple pcs at a time? when the problem happens, can a new user telnet in?

does the server have multiple ip addresses assinged to it?

by kyle.wickliffe

finally tracked down the problem to a pix firewall taking the same IP address - i don't know anything about pix configuration, but i think that falls under dupe ip - thanks for your help and sorry it took so long to rate

by stillatit

I have seen this on AIX 4.1.4 after the server was up for a long time. Rebooting the server made the problem go away.

Good luck.

by shanghai sam

Kyle, it sounds like a session is initiated but not established, and then gets trashed, perhaps due to collisions and other traffic on the hubs. Then you have to wait for the server to timeout the attempted connection. I don't know how many users you've got, but here's a possible "quick fix". See if you can purchase a 12 or 16 port switch for your network. First, move the AIX box to one port on the switch. Then break out each hub and give it a port on the switch. This should drastically reduce the number of collisions on the network and should improve response. If you get a 10/100 switch, be sure to set the AIX box to 100 Mbps full-duplex for best performance (providing the AIX NIC can operate at that speed). Since this suggestion is not really based on hard facts, check out the number of users accessing the AIX box from your WAN sites. I don't know how big your hubs are, so I don't know if you've got 8x12, 8x16 or 8x32 users on this same collision domain. Not knowing how your WAN sites attach to the AIX makes a difference as well. Plus, does this problem happen during "peak" traffic times? Do you have any tools to tell you when your network is the busiest? It just "feels" load related and switches are the fastest way to alleviate hub load problems. If you want to talk more, drop me an e-mail at chris.kilday@ctg.com. Best wishes,
ck

by kyle.wickliffe

we've been considering using a switch, but we didn't really know how it was supposed to help - thanks for shedding some light on that

This discussion is closed to new replies.