gerhow.blogg.se

Using wireshark to troubleshoot slow network
Using wireshark to troubleshoot slow network




using wireshark to troubleshoot slow network

the delay would appear something like the first web page takes "forever" to come up. Something like the primary DNS is down/offline/unavailable (or duplex-mismatched) so each request is timing out on the primary and failing over to the secondary. Many times a "slow network" is really an internal resource that is slow to respond (maybe overloaded, maybe poorly written, old drivers, a user-class machine being used as a server)ĭNS issues can make a network appear slow. If the affected segment feeds a server, or an Internet gateway, everyone will see it. This will usually cause extreme slowness. One or more connections are having duplex-mismatch problems. Some common "slow network" causes (depending on who is complaining): Is the network slow for users just going to the Internet, or just slow for users of the internal resources? First, try to localize the "slowness" if possible.Īre all of the complainers on the same segment? or the whole LAN, or just users that cross the WAN?






Using wireshark to troubleshoot slow network