Update: Wierd telnet problems
2007-12-24 19:00:00
to pin it down:
The subnet is wired into a Cisco hub, not switch or router, exclusively.
Nothing else is on the hub whatsoever, and all servers have a direct cable
connection to the hub. The default route that all servers have is also
plugged directly into the hub, there is nothing inbetween. The default
route interface happens to be on a firewall, but I am the administrator of
it, and it is fine.
Effectlively, I think I can rule out the following suggestions:
Firewall Rules (30 second connection theory)
Router on the network giving out duff RIP
Duplicate IP addresses
Both the default route interface and servers on the subnet come up with
100Mb half duplex, and this is the only slight irregularity I can find
anywhere. I will try to force the servers to use 100 FD, if it can be done
on the fly with NDD.
Thanks
Dan
-----Original Message-----
From: Wilkinson, Daniel
Sent: 18 December 2000 11:19
To: sun-managers at codeprof.ececs.uc.edu
Subject: Wierd telnet problems
Admins,
I have a problem on with a subnet on my network that I can't understand.
Servers on the subnet 10.0.19.0 (Subnet 255.255.255.0) have the following
routing table:
10.0.19.0 10.0.19.90 U 3 2 hme0
224.0.0.0 10.0.19.90 U 3 0 hme0
default 10.0.19.1 UG 0 18
127.0.0.1 127.0.0.1 UH 0 204 lo0
When I telnet to any server on this network, I can connect OK, and log in.
The default route back is sufficient to allow me to telnet in normally etc.
I can play around on for generally about 30 seconds, before my session
freezes, and all I can do it a CTRL=] to quit from telnet. If I snoop on
the default route interface I often still see the traffic that I was doing
carry on (eg a vmstat) happily scrolling away like it was still runing.
So, what is going on and how do I stop it?
Thanks
Dan
Comments
Got something to say?
You must be logged in to post a comment.
