On 20/07/11 12:04, Laurie Brown wrote:
Good luck - I hope you find the problem.
The above is a good idea to check; I've seen that happen as well. Also, check if DNS is an issue; there may be a problem with look-ups.
Cheers, Laurie.
DNS wouldn't particularly explain all the mid session freezes.
Are your switches managed switches....maybe have a poke around the management interface see if there is anything strange going on.
ping's delayed ? dropped packets ?...maybe mtr would help here and you can leave it running for some time pinging a local address and then just check back on the stats later
Can you replicate the problem between any two hosts on the network ? Or does it only happen from Client to Server and if so are all your Server's on one switch ?
Did you notice any heavy broadcast traffic when you were using wireshark...I've had silly things in the past like ethernet enabled printers with every network type known to man enabled in the control panel shout all over the broadcast address trying to announce themselves to clients.
Or two UPnP enabled routers on the same subnet both of which think they are a default gateway...that drives the zeroconf service in Windows a bit mad..but you would have seen that going on in wireshark as it runs on broadcast traffic. Last time I saw that it was when someone had re-purposed an old router as a Wifi AP..turned off DHCP but left it still thinking it was a router.
I've also had the runaround with a confused stack of switches (particularly if they are cheap or a mixture or makes) if you can afford the downtime then reboot them. Or seen a rogue network card on a single host play havoc although again usually you would see broadcast traffic or something going on in wireshark.