Netserver LH4 Dropping network packets...

[Debbie Farris]

Greetings,
We have an LH4 that suddenly started dropping the odd network packet. We've tried swapping network card/slot and still the same result. You can ping the server and it will respond 7 times time out twice respond again. Exert:
Reply from 10.168.1.66: bytes=32 time<10ms TTL=128
Request timed out.
Request timed out.
Reply from 10.168.1.66: bytes=32 time<10ms TTL=128
Request timed out.
Reply from 10.168.1.66: bytes=32 time<10ms TTL=128
Reply from 10.168.1.66: bytes=32 time<10ms TTL=128
Reply from 10.168.1.66: bytes=32 time<10ms TTL=128
Reply from 10.168.1.66: bytes=32 time<10ms TTL=128
Reply from 10.168.1.66: bytes=32 time<10ms TTL=128
Reply from 10.168.1.66: bytes=32 time<10ms TTL=128
Reply from 10.168.1.66: bytes=32 time<10ms TTL=128
Request timed out.
Request timed out.
Request timed out.
Reply from 10.168.1.66: bytes=32 time<10ms TTL=128
Reply from 10.168.1.66: bytes=32 time<10ms TTL=128
Reply from 10.168.1.66: bytes=32 time<10ms TTL=128
Request timed out.
Request timed out.
Reply from 10.168.1.66: bytes=32 time<10ms TTL=128
Reply from 10.168.1.66: bytes=32 time<10ms TTL=128
Reply from 10.168.1.66: bytes=32 time<10ms TTL=128
Request timed out.
Request timed out.
Reply from 10.168.1.66: bytes=32 time<10ms TTL=128
Reply from 10.168.1.66: bytes=32 time<10ms TTL=128
Reply from 10.168.1.66: bytes=32 time<10ms TTL=128
Request timed out.
Request timed out.
Reply from 10.168.1.66: bytes=32 time<10ms TTL=128
Reply from 10.168.1.66: bytes=32 time<10ms TTL=128
Reply from 10.168.1.66: bytes=32 time<10ms TTL=128
Request timed out.
Request timed out.
Reply from 10.168.1.66: bytes=32 time<10ms TTL=128
Request timed out.
Reply from 10.168.1.66: bytes=32 time<10ms TTL=128
Request timed out.
Request timed out.
Reply from 10.168.1.66: bytes=32 time<10ms TTL=128
Request timed out.
Reply from 10.168.1.66: bytes=32 time<10ms TTL=128
Request timed out.
Reply from 10.168.1.66: bytes=32 time<10ms TTL=128
Reply from 10.168.1.66: bytes=32 time<10ms TTL=128
Reply from 10.168.1.66: bytes=32 time<10ms TTL=128
Request timed out.
Reply from 10.168.1.66: bytes=32 time<10ms TTL=128
Reply from 10.168.1.66: bytes=32 time<10ms TTL=128
Request timed out.
Reply from 10.168.1.66: bytes=32 time<10ms TTL=128
Request timed out.
Reply from 10.168.1.66: bytes=32 time<10ms TTL=128
Reply from 10.168.1.66: bytes=32 time<10ms TTL=128
Reply from 10.168.1.66: bytes=32 time<10ms TTL=128
Request timed out.
Reply from 10.168.1.66: bytes=32 time<10ms TTL=128
Reply from 10.168.1.66: bytes=32 time<10ms TTL=128
Request timed out.
Reply from 10.168.1.66: bytes=32 time<10ms TTL=128
Reply from 10.168.1.66: bytes=32 time<10ms TTL=128
Reply from 10.168.1.66: bytes=32 time<10ms TTL=128
Request timed out.
Request timed out.
Reply from 10.168.1.66: bytes=32 time<10ms TTL=128
Reply from 10.168.1.66: bytes=32 time<10ms TTL=128
Reply from 10.168.1.66: bytes=32 time<10ms TTL=128
Request timed out.
Reply from 10.168.1.66: bytes=32 time<10ms TTL=128
Reply from 10.168.1.66: bytes=32 time<10ms TTL=128
Reply from 10.168.1.66: bytes=32 time<10ms TTL=128
Reply from 10.168.1.66: bytes=32 time<10ms TTL=128
Reply from 10.168.1.66: bytes=32 time<10ms TTL=128
Request timed out.
Request timed out.
Reply from 10.168.1.66: bytes=32 time<10ms TTL=128
Reply from 10.168.1.66: bytes=32 time<10ms TTL=128
Reply from 10.168.1.66: bytes=32 time<10ms TTL=128
Reply from 10.168.1.66: bytes=32 time<10ms TTL=128
Reply from 10.168.1.66: bytes=32 time<10ms TTL=128
Reply from 10.168.1.66: bytes=32 time<10ms TTL=128
There is no reason for this, that I can think of execpt the mother board is going. Does anyone else have any ideas.
Thank you in advance.

[Chris Blumenshine]

You've tried other cards and other slots... How about other cables, other ports, other switches? I'm not clear if this IP is on the LH 4 or not...if not, could it be a problem with the other machine? If so, what happens if you do ping another machine? What about when another machine pings the server? What happens when you ping 127.0.0.1? Although not totally out of the question, to me, a system board causing this is unlikely if you have the same issue in other slots.

[Theo Hill_1]

Also, verify you are using the HP driver for the NIC, and not the one that came with the OS. You should also be able to install the set utility and run diagnostics on the NIC.

[Debbie Farris]

The server is now on our private network hence the non routable ip. The original post is me pinging the server. When I ping the server there is a 5% packet loss, when I ping out from the server there is a 10% or more packet loss. If I ping 127.0.0.1 there is no packet loss. I have changed to different types of network cards, used different slots on the motherboard, used manufactures drives and windows drivers. Same thing.
For a while is wasn't communicating on the network at all, I would ping and see no traffic going out or coming in. I applied the work around for IRQ9 and that seemed to help. But it is still dropping packets.

[gruson]

Hi,

Have you tried to desactivate your antivirus ?
I have had a customer which has had the same
type of pb than yours.
Finally, it was this.

Bye.

Fab.

[Debbie Farris]

Greetings All,
It seems that a system bus on the IO card is gone. I put the network card in the last possible pci slot and it works. So we have found a replacement IO board and it is on it's way to us. Thank you for all your suggestions.