Connection dropping on device

[j-lucero]

I am having problems with a network connection being dropped on a device connected to a Catalyst 3524.

The system is a harden CPU running Windows 98. The network adapter is a Realtek RTL8139(A/B/C/8130) PCI Fast Ethernet NIC.

After a period of inactivity the system will quit responding on the network. The Device can not be pinged from a remote subnet. It can be pinged from the local subnet, but the first packet always drops.

There is no wake on LAN option. There is a configuration option for Early Tx Threshold (set to 10). I do not know what that is.

Any Ideas would be appreciated.

[lgijssel]

Please try the following:

As the device cannot be pinged from a remote subnet please first check the default-gw setting on the device.

To know if this is an ARP-related issue do a ping from a device (preferrably a cisco-switch) and check that it has no existing arp-entry for the device before you do this. Then repeat the test after this step has been successfull.

Subsequently check arp table on both sides. Windows has a short arp-timeout (about 3 min) Repeat the test after the arp entry on the target device has aged out and compare the results.

Regards,

Leo

[scottmac]

1). Check to see that "Allow Windows to power down this device to conserve power" is not checked in the advanced NIC properties and / or the power management section.

2.) For most, if not all switches, the first packet must be processed and evaluated (then all of the paramaters are hashed in/to the CAM for fast sitching). It's possible, depending on the load of the switch, that the ARP and forwarding table is expiring ... causing the next "first frame" to have to undergo(the slow) process switching.

You may be able to mitigate this by extending the ageing time in the CAM and / or ARP table (possible static entry??).

3). (The usual stuff) Check that your NIC drivers re up-to-date, try another NIC (RealTech is OK, but doesn't enjoy a steller reputation for reliability and performance).

4.) Are you sure that the ping from the remote LAN is getting to the box? How are you verifying it?

If you haven't already, load up Ethereal or similar packet analyzer and capture the session. See if each packet is making it, and that the box is responding. Most firewalls, by default, will filter pings and other ICMP and / or UDP traffic inbound. Check the firewall (or take it out for diagnostic purposes if you can without compromising the network).

Good Luck

Scott

[j-lucero]

Scott

Thank you for the input. While we are seeing some interesting things happening in the router arp table. The problem we are seeing is very much like what has been discussed in the threads I have gone over concerning the RealTeck card.

I think our next step is to replace the card, or atleast update the drivers.