netstat on local systems shows high number of ipv4/6 Received Packets Discarded, Redirects, Failed Connection Attempts, Reset Connections and Segments Retransmitted
-
@dafyre said in netstat on local systems shows high number of ipv4/6 Received Packets Discarded, Redirects, Failed Connection Attempts, Reset Connections and Segments Retransmitted:
Pick one of the problem Workstations and reset the network counters on the switch and port that it's connected to. If the counters start climbing here's some things you could try:
-
Replace the network cables between PC and wall, and the Patch Panel and Network switch port the work station is connectingto.
And then reset the counters and watch them. -
In the NIC Adapter properties on the workstation:
Disable anything that says offload. (Arp Offload, TCP Checksum Offload, Large Send Offload, TCP/UDP Checksum Offload).
And then reset the counters and watch them again.
- If that doesn't work, check the Speed & Duplex settings and set it to 100 Mbit, Half Duplex (Yes, I know this seems counter intuitive). A lot of times doing this can seem to grant a speed increase despite lowering the speeds. If this fixes the problem, it could be some interference on the line that's preventing the systems from working well at max speeds (I'm assuming 1 gigabit).
I'll give those a try. I did reset the first computer several times that I was looking at which resets the Received Packets Discarded and they quickly start climbing back up, maybe 50 per minute or something. I was just thinking, all these computers also connect directly to a Cisco phone set which then connects to the network. The Cisco phones are on their own VLAN separate from the PC LAN. I wonder if that has anything to do with it...
-
-
@dave247 said in netstat on local systems shows high number of ipv4/6 Received Packets Discarded, Redirects, Failed Connection Attempts, Reset Connections and Segments Retransmitted:
netstat -sp on about 6 other workstations and I am seeing pretty much similar results where systems show a varying degree of seemingly high ipv4/6 Received Packets Discarded, Redirects, Fa
wont iperf3 be more effiecent and faster, just run it on suspected nodes and test the throughput and test on a good node and compare
-
@Emad-R said in netstat on local systems shows high number of ipv4/6 Received Packets Discarded, Redirects, Failed Connection Attempts, Reset Connections and Segments Retransmitted:
@dave247 said in netstat on local systems shows high number of ipv4/6 Received Packets Discarded, Redirects, Failed Connection Attempts, Reset Connections and Segments Retransmitted:
netstat -sp on about 6 other workstations and I am seeing pretty much similar results where systems show a varying degree of seemingly high ipv4/6 Received Packets Discarded, Redirects, Fa
wont iperf3 be more effiecent and faster, just run it on suspected nodes and test the throughput and test on a good node and compare
I've literally never heard of iperf3 before.
-
@dave247 said in netstat on local systems shows high number of ipv4/6 Received Packets Discarded, Redirects, Failed Connection Attempts, Reset Connections and Segments Retransmitted:
@Emad-R said in netstat on local systems shows high number of ipv4/6 Received Packets Discarded, Redirects, Failed Connection Attempts, Reset Connections and Segments Retransmitted:
@dave247 said in netstat on local systems shows high number of ipv4/6 Received Packets Discarded, Redirects, Failed Connection Attempts, Reset Connections and Segments Retransmitted:
netstat -sp on about 6 other workstations and I am seeing pretty much similar results where systems show a varying degree of seemingly high ipv4/6 Received Packets Discarded, Redirects, Fa
wont iperf3 be more effiecent and faster, just run it on suspected nodes and test the throughput and test on a good node and compare
I've literally never heard of iperf3 before.
https://chocolatey.org/packages/iperf3
choco install iperf3 -y -
@scottalanmiller said in netstat on local systems shows high number of ipv4/6 Received Packets Discarded, Redirects, Failed Connection Attempts, Reset Connections and Segments Retransmitted:
@dave247 said in netstat on local systems shows high number of ipv4/6 Received Packets Discarded, Redirects, Failed Connection Attempts, Reset Connections and Segments Retransmitted:
@Emad-R said in netstat on local systems shows high number of ipv4/6 Received Packets Discarded, Redirects, Failed Connection Attempts, Reset Connections and Segments Retransmitted:
@dave247 said in netstat on local systems shows high number of ipv4/6 Received Packets Discarded, Redirects, Failed Connection Attempts, Reset Connections and Segments Retransmitted:
netstat -sp on about 6 other workstations and I am seeing pretty much similar results where systems show a varying degree of seemingly high ipv4/6 Received Packets Discarded, Redirects, Fa
wont iperf3 be more effiecent and faster, just run it on suspected nodes and test the throughput and test on a good node and compare
I've literally never heard of iperf3 before.
https://chocolatey.org/packages/iperf3
choco install iperf3 -yNever heard of choco either!
-
@dave247 said in netstat on local systems shows high number of ipv4/6 Received Packets Discarded, Redirects, Failed Connection Attempts, Reset Connections and Segments Retransmitted:
Never heard of choco either!
That's weird, I had someone else say that like five days ago. Chocolatey is "the" package management system for Windows, even Microsoft uses it for official stuff (sometimes.) It's like the super awesome secret tool of Windows admins. It's crazy popular around here, I swear all of us use it. Makes Windows administration so much better.
-
@scottalanmiller said in netstat on local systems shows high number of ipv4/6 Received Packets Discarded, Redirects, Failed Connection Attempts, Reset Connections and Segments Retransmitted:
@dave247 said in netstat on local systems shows high number of ipv4/6 Received Packets Discarded, Redirects, Failed Connection Attempts, Reset Connections and Segments Retransmitted:
Never heard of choco either!
That's weird, I had someone else say that like five days ago. Chocolatey is "the" package management system for Windows, even Microsoft uses it for official stuff (sometimes.) It's like the super awesome secret tool of Windows admins. It's crazy popular around here, I swear all of us use it. Makes Windows administration so much better.
wtf... seriously. WTF?? It's like you guys are in a different world over here. I'm looking at the website now...
-
Most Tx and Rx errors on switch ports were usually related to poorly terminated cabling in my experience, very rarely to misconfigured or faulty interfaces. Reset counters as already suggested by @dafyre at both ends and see if the numbers grow up quickly again.
-
Normally, you don't want any IP phones with 100 Mbit/s PC ports to avoid network bottlenecks. I've seen issues with duplex mismatches with them too.
-
@taurex said in netstat on local systems shows high number of ipv4/6 Received Packets Discarded, Redirects, Failed Connection Attempts, Reset Connections and Segments Retransmitted:
Normally, you don't want any IP phones with 100 Mbit/s PC ports to avoid network bottlenecks. I've seen issues with duplex mismatches with them too.
Phones only use about 100Kb/s max. So if you are using them for passthrough, you want to avoid that. But if you aren't, no big deal at all to have "slow" phones.
-
@dave247 said in netstat on local systems shows high number of ipv4/6 Received Packets Discarded, Redirects, Failed Connection Attempts, Reset Connections and Segments Retransmitted:
The Cisco phones are on their own VLAN separate from the PC LAN. I wonder if that has anything to do with it...
IIRC, the last place I worked, we had to do this on just about every PC that was connected to a Phone (Mitel phones, not Cisco).
-
@taurex said in netstat on local systems shows high number of ipv4/6 Received Packets Discarded, Redirects, Failed Connection Attempts, Reset Connections and Segments Retransmitted:
Most Tx and Rx errors on switch ports were usually related to poorly terminated cabling in my experience, very rarely to misconfigured or faulty interfaces. Reset counters as already suggested by @dafyre at both ends and see if the numbers grow up quickly again.
Yeah that wouldn't surprise me since many of these cable runs are old and the maintenance guy (non-IT) did a lot of the cable work. I've seen some bad cables and had problems with some terminations and tried to fix them only to have the problem persist. I'm thinking we have a lot of stuff not run properly or draped over electrical things in our ceiling. And we have a lot of stuff up there as its a really old building. Point is, I'm very inclined to think that the runs between switches should be replaced.
-
@dave247 said in netstat on local systems shows high number of ipv4/6 Received Packets Discarded, Redirects, Failed Connection Attempts, Reset Connections and Segments Retransmitted:
@taurex said in netstat on local systems shows high number of ipv4/6 Received Packets Discarded, Redirects, Failed Connection Attempts, Reset Connections and Segments Retransmitted:
Most Tx and Rx errors on switch ports were usually related to poorly terminated cabling in my experience, very rarely to misconfigured or faulty interfaces. Reset counters as already suggested by @dafyre at both ends and see if the numbers grow up quickly again.
Yeah that wouldn't surprise me since many of these cable runs are old and the maintenance guy (non-IT) did a lot of the cable work. I've seen some bad cables and had problems with some terminations and tried to fix them only to have the problem persist. I'm thinking we have a lot of stuff not run properly or draped over electrical things in our ceiling. And we have a lot of stuff up there as its a really old building. Point is, I'm very inclined to think that the runs between switches should be replaced.
Could be the case. A cable tester (good one) should be able to tell you the quality of the runs. Might save time and money.
-
Just move it to a different switch port in the network closet. If that switch port shows the same things and the other one stops then you know what the problem is somewhere in the line or the computer or the phone. At that point you can then patch the phone to a different network jack with a long cable temporarily and eliminates the run as the problem. Finally you can change the cable between the phone in the computer. That eliminates all of the wiring. That leaves you with the devices. Swap the phone and see if it still happens. This is just a basic process of elimination.
-
@JaredBusch said in netstat on local systems shows high number of ipv4/6 Received Packets Discarded, Redirects, Failed Connection Attempts, Reset Connections and Segments Retransmitted:
Just move it to a different switch port in the network closet. If that switch port shows the same things and the other one stops then you know what the problem is somewhere in the line or the computer or the phone. At that point you can then patch the phone to a different network jack with a long cable temporarily and eliminates the run as the problem. Finally you can change the cable between the phone in the computer. That eliminates all of the wiring. That leaves you with the devices. Swap the phone and see if it still happens. This is just a basic process of elimination.
Yes, I already switched ethernet ports on the wall and I'm still seeing the issue. I haven't changed the phone yet though. Waiting for the user to go on lunch.
-
@scottalanmiller said in netstat on local systems shows high number of ipv4/6 Received Packets Discarded, Redirects, Failed Connection Attempts, Reset Connections and Segments Retransmitted:
@dave247 said in netstat on local systems shows high number of ipv4/6 Received Packets Discarded, Redirects, Failed Connection Attempts, Reset Connections and Segments Retransmitted:
@taurex said in netstat on local systems shows high number of ipv4/6 Received Packets Discarded, Redirects, Failed Connection Attempts, Reset Connections and Segments Retransmitted:
Most Tx and Rx errors on switch ports were usually related to poorly terminated cabling in my experience, very rarely to misconfigured or faulty interfaces. Reset counters as already suggested by @dafyre at both ends and see if the numbers grow up quickly again.
Yeah that wouldn't surprise me since many of these cable runs are old and the maintenance guy (non-IT) did a lot of the cable work. I've seen some bad cables and had problems with some terminations and tried to fix them only to have the problem persist. I'm thinking we have a lot of stuff not run properly or draped over electrical things in our ceiling. And we have a lot of stuff up there as its a really old building. Point is, I'm very inclined to think that the runs between switches should be replaced.
Could be the case. A cable tester (good one) should be able to tell you the quality of the runs. Might save time and money.
I have a Fluke Networks MT-8200-49A Cable Tester and in the past when I have checked the connections, I don't get any errors. This might be a crappy cable tester though.
-
@dave247 said in netstat on local systems shows high number of ipv4/6 Received Packets Discarded, Redirects, Failed Connection Attempts, Reset Connections and Segments Retransmitted:
@scottalanmiller said in netstat on local systems shows high number of ipv4/6 Received Packets Discarded, Redirects, Failed Connection Attempts, Reset Connections and Segments Retransmitted:
@dave247 said in netstat on local systems shows high number of ipv4/6 Received Packets Discarded, Redirects, Failed Connection Attempts, Reset Connections and Segments Retransmitted:
@taurex said in netstat on local systems shows high number of ipv4/6 Received Packets Discarded, Redirects, Failed Connection Attempts, Reset Connections and Segments Retransmitted:
Most Tx and Rx errors on switch ports were usually related to poorly terminated cabling in my experience, very rarely to misconfigured or faulty interfaces. Reset counters as already suggested by @dafyre at both ends and see if the numbers grow up quickly again.
Yeah that wouldn't surprise me since many of these cable runs are old and the maintenance guy (non-IT) did a lot of the cable work. I've seen some bad cables and had problems with some terminations and tried to fix them only to have the problem persist. I'm thinking we have a lot of stuff not run properly or draped over electrical things in our ceiling. And we have a lot of stuff up there as its a really old building. Point is, I'm very inclined to think that the runs between switches should be replaced.
Could be the case. A cable tester (good one) should be able to tell you the quality of the runs. Might save time and money.
I have a Fluke Networks MT-8200-49A Cable Tester and in the past when I have checked the connections, I don't get any errors. This might be a crappy cable tester though.
Fluke is quality stuff. If it says that the line is clear, I'd believe it. Do you get packed loss across the line?
-
@dave247 said in netstat on local systems shows high number of ipv4/6 Received Packets Discarded, Redirects, Failed Connection Attempts, Reset Connections and Segments Retransmitted:
@Emad-R said in netstat on local systems shows high number of ipv4/6 Received Packets Discarded, Redirects, Failed Connection Attempts, Reset Connections and Segments Retransmitted:
@dave247 said in netstat on local systems shows high number of ipv4/6 Received Packets Discarded, Redirects, Failed Connection Attempts, Reset Connections and Segments Retransmitted:
netstat -sp on about 6 other workstations and I am seeing pretty much similar results where systems show a varying degree of seemingly high ipv4/6 Received Packets Discarded, Redirects, Fa
wont iperf3 be more effiecent and faster, just run it on suspected nodes and test the throughput and test on a good node and compare
I've literally never heard of iperf3 before.
-
@dave247 : Have you performed a netstat -ps on another device in another network?
I'm here with a computer hardwired directly to a router in a new installation I'm working on today and am getting similar results to yours (except 0 redirects).I'm guessing this is completely normal...
-
@scottalanmiller said in netstat on local systems shows high number of ipv4/6 Received Packets Discarded, Redirects, Failed Connection Attempts, Reset Connections and Segments Retransmitted:
@dave247 said in netstat on local systems shows high number of ipv4/6 Received Packets Discarded, Redirects, Failed Connection Attempts, Reset Connections and Segments Retransmitted:
Never heard of choco either!
That's weird, I had someone else say that like five days ago. Chocolatey is "the" package management system for Windows, even Microsoft uses it for official stuff (sometimes.) It's like the super awesome secret tool of Windows admins. It's crazy popular around here, I swear all of us use it. Makes Windows administration so much better.
yeah - but it's still basically a completely unknown entity.
