Kitkat362's profile

New Contributor

 • 

75 Messages

Sunday, November 13th, 2016 3:13 AM

Closed

Packet loss again with the Cox Network Please help

So it seems I am again having packet loss in the cox network. 2 Hops seem to be messed up. One at 68.1.11.76 and one at 68.1.2.109

I'm not so much worried about the packetloss after that since its not in your control. Before you guys ask me any questions I want to make sure 100% I answer the basics this way we can try to fix this issue. 

#1. I am directly connected with my computer to the modem. There is no router I'm connected by an either net cable 

#2. these problems are constant throughout the day/evening/late night. 

#3. I ran a virus /spyware removal tool to make sure my computer is not infected. 

#4. I'm only worried about things in the cox network. I seem to have packetloss at many cox hops including 10.18.179.1 and 68.1.11.76 and 68.1.2.109

Something seems very wrong with my connection

I just ran a speed test on the cox speed test logged in 

Sat Nov 12 10:12 PM Yes 97 Mbps 11 Mbps 28 millisec 98.162.169.77

Atlanta

However on testmy.net I'm am getting low upload speeds due to the packet loss.

New Contributor

 • 

75 Messages

9 years ago

https://share.pingplotter.com/hLc9DJ2sNi6

New Contributor

 • 

75 Messages

9 years ago

Double post sorry

Contributor II

 • 

319 Messages

9 years ago

You are getting packet loss on even the first hop, which really isn't good.  You are also getting, on average, a ping delay of 18ms just from your computer to your router.  My computer (wired)-> client bridge (wireless)-> router averages <1ms of delay, so you've definitely got something going on local.  Also, none of the packet loss is consistent - which doesn't really indicate anything at all.

So re-reading your post, this makes your results even stranger.  IF your modem is directly connected to your computer you should have absolutely 0 packet loss, and a delay of <1ms - so either there is something going on in the computer or the modem itself that is causing a significant symptom.

However, your post from pingplotter indicates you are going through a router, that is the 192.168.0.1 hop - so which modem do you have?  Does it have the router integrated?

Moderator

 • 

4.3K Messages

9 years ago

Hi Kitkat362,

Thanks for providing so many details in your initial post. Is there a splitter on the coax cable that connects to your Gateway/modem?

New Contributor

 • 

75 Messages

9 years ago

There is not. Its a line coming from outside into my modem. I have an appointment with a technician tomorrow. I used the online chat feature. I'm going to show them the ping plotter reports and do one while they're here. Still having issues this morning.

New Contributor

 • 

75 Messages

9 years ago

And yes the router is integrated in the modem 

modem NetGear Docsis3.0

DN6300B

All my wifi items are off and regardless I wasn't having this problem until yesterday (even when I was using wifi items and streaming on twitch)

EDIT

I listened to what was said about the local ping being very high and changed out my eithernet cord. It worked better for the first hop but still getting packet loss in the cox network

https://share.pingplotter.com/8qTJ4grgoeM (in coxnetwork)

https://share.pingplotter.com/RNuoqhKmSxR (to google)

Moderator

 • 

4.3K Messages

9 years ago

Hi Kitkat,

I'm glad to hear you have an appointment scheduled. Please let us know the results of the service call so we can provide follow-up if necessary.

Contributor II

 • 

319 Messages

9 years ago

There you go, first hop is <1ms with 0 packet loss, so that is part of the problem solved.  Although it does appear you are getting some packet loss on the next hop (CMTS), and that is usually signal or noise based.  A tech should be able to track that down.

New Contributor

 • 

75 Messages

9 years ago

I may not explain this 100% correctly but let me try to say what the others have said.

I've been bumped up to a tier 2 situation? whatever that means

My IP address is being used in part of a DDoS attack and I've been getting the error of "Ping of Death" "[Illegal Fragments]" coming from 3 different IP addresses. This is why there was latency in the modem itself apparently there isn't much I can do except to wait for the IP address to change which is every month. This is probably why it affected me out of no where, also, you guys apparently can't just change the IP address I'll have to wait until next month?


Here is some information and hopefully one of you guys could help me. This is the LOG from my Modem/router combo 


2016-11-15, 07:23:31.0 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=a4:2b:8c:2f:cd:e0;CMTS-MAC=00:14:f1:e8:69:a0;CM-QOS=1.1;CM-VER=3.0;
2016-11-15, 03:50:22.0 Error (4) DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=a4:2b:8c:2f:cd:e0;CMTS-MAC=00:14:f1:e8:69:a0;CM-QOS=1.1;CM-VER=3.0;
2016-11-15, 02:49:26.0 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=a4:2b:8c:2f:cd:e0;CMTS-MAC=00:14:f1:e8:69:a0;CM-QOS=1.1;CM-VER=3.0;
2016-11-14, 22:03:51.0 Warning (5) Admin login authentication fail
2016-11-14, 21:37:27.0 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=a4:2b:8c:2f:cd:e0;CMTS-MAC=00:14:f1:e8:69:a0;CM-QOS=1.1;CM-VER=3.0;
2016-11-14, 15:50:24.0 Notice (6) TLV-11 - unrecognized OID;CM-MAC=a4:2b:8c:2f:cd:e0;CMTS-MAC=00:14:f1:e8:69:a0;CM-QOS=1.1;CM-VER=3.0;
2016-11-14, 15:50:24.0 Critical (3) TLV-11 - Illegal Set operation failed;CM-MAC=a4:2b:8c:2f:cd:e0;CMTS-MAC=00:14:f1:e8:69:a0;CM-QOS=1.1;CM-VER=3.0;
2016-11-14, 15:49:08.0 Critical (3) Resetting the cable modem due to docsDevResetNow
2016-11-14, 15:41:29.0 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=a4:2b:8c:2f:cd:e0;CMTS-MAC=00:14:f1:e8:69:a0;CM-QOS=1.1;CM-VER=3.0;
2016-11-14, 15:39:46.0 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=a4:2b:8c:2f:cd:e0;CMTS-MAC=00:14:f1:e8:69:a0;CM-QOS=1.1;CM-VER=3.0;
2016-11-14, 15:39:04.0 Critical (3) TLV-11 - Illegal Set operation failed;CM-MAC=a4:2b:8c:2f:cd:e0;CMTS-MAC=00:14:f1:e8:69:a0;CM-QOS=1.1;CM-VER=3.0;
2016-11-14, 15:37:49.0 Critical (3) Resetting the cable modem due to docsDevResetNow
2016-11-14, 15:15:47.0 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=a4:2b:8c:2f:cd:e0;CMTS-MAC=00:14:f1:e8:69:a0;CM-QOS=1.1;CM-VER=3.0;
2016-11-14, 08:24:37.0 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=a4:2b:8c:2f:cd:e0;CMTS-MAC=00:14:f1:e8:69:a0;CM-QOS=1.1;CM-VER=3.0;
2016-11-13, 20:12:03.0 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=a4:2b:8c:2f:cd:e0;CMTS-MAC=00:14:f1:e8:69:a0;CM-QOS=1.1;CM-VER=3.0;
2016-11-13, 08:27:26.0 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=a4:2b:8c:2f:cd:e0;CMTS-MAC=00:14:f1:e8:69:a0;CM-QOS=1.1;CM-VER=3.0;
2016-11-13, 08:26:43.0 Critical (3) TLV-11 - Illegal Set operation failed;CM-MAC=a4:2b:8c:2f:cd:e0;CMTS-MAC=00:14:f1:e8:69:a0;CM-QOS=1.1;CM-VER=3.0;
2016-11-13, 08:18:44.0 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=a4:2b:8c:2f:cd:e0;CMTS-MAC=00:14:f1:e8:69:a0;CM-QOS=1.1;CM-VER=3.0;
2016-11-13, 08:18:01.0 Critical (3) TLV-11 - Illegal Set operation failed;CM-MAC=a4:2b:8c:2f:cd:e0;CMTS-MAC=00:14:f1:e8:69:a0;CM-QOS=1.1;CM-VER=3.0;
2016-11-13, 07:50:37.0 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=a4:2b:8c:2f:cd:e0;CMTS-MAC=00:14:f1:e8:69:a0;CM-QOS=1.1;CM-VER=3.0;
2016-11-13, 01:46:37.0 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=a4:2b:8c:2f:cd:e0;CMTS-MAC=00:14:f1:e8:69:a0;CM-QOS=1.1;CM-VER=3.0;
2016-11-13, 01:45:55.0 Critical (3) TLV-11 - Illegal Set operation failed;CM-MAC=a4:2b:8c:2f:cd:e0;CMTS-MAC=00:14:f1:e8:69:a0;CM-QOS=1.1;CM-VER=3.0;
2016-11-13, 01:44:38.0 Critical (3) Resetting the cable modem due to docsDevResetNow
2016-11-13, 01:04:33.0 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=a4:2b:8c:2f:cd:e0;CMTS-MAC=00:14:f1:e8:69:a0;CM-QOS=1.1;CM-VER=3.0;
2016-11-12, 22:51:31.0 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=a4:2b:8c:2f:cd:e0;CMTS-MAC=00:14:f1:e8:69:a0;CM-QOS=1.1;CM-VER=3.0;
2016-11-12, 22:51:15.0 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=a4:2b:8c:2f:cd:e0;CMTS-MAC=00:14:f1:e8:69:a0;CM-QOS=1.1;CM-VER=3.0;
2016-11-12, 22:50:48.0 Critical (3) TLV-11 - Illegal Set operation failed;CM-MAC=a4:2b:8c:2f:cd:e0;CMTS-MAC=00:14:f1:e8:69:a0;CM-QOS=1.1;CM-VER=3.0;
2016-11-12, 22:00:47.0 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=a4:2b:8c:2f:cd:e0;CMTS-MAC=00:14:f1:e8:69:a0;CM-QOS=1.1;CM-VER=3.0;
Time Not Established Warning (5) DHCP WARNING - Non-critical field invalid in response ;CM-MAC=a4:2b:8c:2f:cd:e0;CMTS-MAC=00:14:f1:e8:69:a0;CM-QOS=1.0;CM-VER=3.0;
Time Not Established Notice (6) Honoring MDD; IP provisioning mode = IPv4
Time Not Established Notice (6) WiFi Interface [wl0] set to Channel 1 (Side-Band Channel:N/A) - Reason:INIT
Time Not Established Notice (6)

WiFi Interface [wl1] set to Channel 36 (Side-Band Channel:N/A) - Reason:INIT



Also 

Description Count Last Occurrence Target Source
[Teardrop or derivative] 2 Tue Nov 15 11:39:52 2016 84.12.76.107:0 130.192.156.0:0
[Illegal Fragments] 1 Tue Nov 15 11:39:52 2016 84.12.76.107:0 130.192.156.0:0
[Teardrop or derivative] 2 Tue Nov 15 11:39:52 2016 84.12.76.107:0 130.192.156.0:0
[Illegal Fragments] 1 Tue Nov 15 11:39:52 2016 84.12.76.107:0 130.192.156.0:0
[Teardrop or derivative] 9 Tue Nov 15 11:39:53 2016 84.12.76.107:0 130.192.156.0:0
[Illegal Fragments] 1 Tue Nov 15 11:39:53 2016 84.12.76.107:0 130.192.156.0:0
[Teardrop or derivative] 1 Tue Nov 15 11:40:23 2016 84.12.76.107:0 130.192.156.0:0
[Illegal Fragments] 1 Tue Nov 15 11:40:24 2016 84.12.76.107:0 130.192.156.0:0
[Ping Of Death] 1 Tue Nov 15 11:40:24 2016 84.12.76.107:0 130.192.156.0:0
[Teardrop or derivative] 10 Tue Nov 15 11:43:34 2016 84.12.76.107:0 130.192.156.0:0
[Ping Of Death] 2 Tue Nov 15 11:43:34 2016 84.12.76.107:0 130.192.156.0:0
[Teardrop or derivative] 4 Tue Nov 15 11:43:34 2016 84.12.76.107:0 130.192.156.0:0
[Ping Of Death] 1 Tue Nov 15 11:43:34 2016 84.12.76.107:0 130.192.156.0:0
[Teardrop or derivative] 12 Tue Nov 15 11:44:36 2016 84.12.76.107:0 130.192.156.0:0
[Ping Of Death] 1 Tue Nov 15 11:44:39 2016 84.12.76.107:0 130.192.156.0:0
[Teardrop or derivative] 9 Tue Nov 15 11:44:41 2016 84.12.76.107:0 130.192.156.0:0
[Ping Of Death] 1 Tue Nov 15 11:44:41 2016 84.12.76.107:0 130.192.156.0:0
[Teardrop or derivative] 18 Tue Nov 15 11:49:22 2016 84.12.76.107:0 130.192.156.0:0
[Illegal Fragments] 1 Tue Nov 15 11:50:53 2016 84.12.76.107:0 130.192.156.0:0
[TCP- or UDP-based Port Scan] 2 Tue Nov 15 14:38:36 2016 98.162.168.135:61830 68.105.29.11:53
[FAILURE: User interface login] 2 Tue Nov 15 14:38:40 2016 192.168.0.1:80 192.168.0.4:54833
[SUCCESS: User interface login] 1 Tue Nov 15 14:38:50 2016 192.168.0.1:80 192.168.0.4:55068
[Public Network Interface up] 1 Tue Nov 15 14:41:40 2016 0.0.0.0:0 0.0.0.0:0
[Firewall Up] 1 Tue Nov 15 14:41:40 2016 0.0.0.0:0 0.0.0.0:0
[TCP- or UDP-based Port Scan] 1 Tue Nov 15 14:41:56 2016 98.162.168.135:52128 68.105.28.12:53
[Public Network Interface up] 1 Tue Nov 15 14:42:43 2016 0.0.0.0:0 0.0.0.0:0
[Firewall Up] 1 Tue Nov 15 14:42:43 2016 0.0.0.0:0 0.0.0.0:0
[Public Network Interface up] 1 Tue Nov 15 14:43:35 2016 0.0.0.0:0 0.0.0.0:0
[Firewall Up] 1 Tue Nov 15 14:43:35 2016 0.0.0.0:0 0.0.0.0:0
[TCP- or UDP-based Port Scan] 1 Tue Nov 15 14:47:38 2016 98.162.168.135:62493

68.105.28.12:53

Anything I can do? This seems very scary.

New Contributor

 • 

75 Messages

9 years ago

We also know that the one of the IP addresses are coming from Monash University in Melbourne Australia in their cyber tech department

Valued Contributor II

 • 

2.8K Messages

9 years ago

It looks like your router is relaying traffic from one location(off Cox) to another location (off Cox). Do you have any VPN server or client running on any of your computers or router? If not, i wonder if this is caused by some kind of malware infection.

Is there any log or table on the router that shows the routing table? Maybe "Static Routes"? Can you post a netstat from the computer? Windows Key + R > CMD > netstat -a > right click > select all > enter then paste.

PS. You wouldn't have any security camera or PVR would you? Not to be a alarmist, but I wonder if Cox may part of Mirai. 

New Contributor

 • 

75 Messages

9 years ago

C:\Users\mike>netstat

Active Connections

Proto Local Address Foreign Address State
TCP 127.0.0.1:49761 mike-PC:49762 ESTABLISHED
TCP 127.0.0.1:49762 mike-PC:49761 ESTABLISHED
TCP 127.0.0.1:49764 mike-PC:49765 ESTABLISHED
TCP 127.0.0.1:49765 mike-PC:49764 ESTABLISHED
TCP 192.168.0.4:49700 msnbot-65-52-108-198:https ESTABLISHED
TCP 192.168.0.4:49775 mia25:http ESTABLISHED
TCP 192.168.0.4:49888 msnbot-65-52-108-232:https ESTABLISHED
TCP 192.168.0.4:50124 r-149-58-45-5:http CLOSE_WAIT
TCP 192.168.0.4:50372 oj-in-f189:https ESTABLISHED
TCP 192.168.0.4:50374 oj-in-f189:https CLOSE_WAIT
TCP 192.168.0.4:50376 oi-in-f125:5222 ESTABLISHED
TCP 192.168.0.4:50380 oi-in-f125:5222 CLOSE_WAIT
TCP 192.168.0.4:50391 oj-in-f188:5228 ESTABLISHED
TCP 192.168.0.4:50392 ya-in-f147:https ESTABLISHED
TCP 192.168.0.4:50393 oj-in-f188:5228 CLOSE_WAIT
TCP 192.168.0.4:50406 192.168.0.12:http TIME_WAIT
TCP 192.168.0.4:50413 134.170.111.154:http TIME_WAIT
TCP 192.168.0.4:50416 dfw25s13-in-f78:https ESTABLISHED
TCP 192.168.0.4:50580 dfw06s46-in-f174:https ESTABLISHED
TCP 192.168.0.4:50581 dfw06s46-in-f174:https CLOSE_WAIT
TCP 192.168.0.4:50653 r-56-41-234-77:http LAST_ACK
TCP [2600:8807:82c0:9c00:280a:7831:800d:32f6]:50047 [2001:428:c06:187::3114]:https ESTABLISHED
TCP [2600:8807:82c0:9c00:280a:7831:800d:32f6]:50048 [2001:428:c08:187::3114]:https ESTABLISHED

C:\Users\mike>

New Contributor

 • 

75 Messages

9 years ago

The router is integrated with the modem I'm not sure where I can look it up  its a c6300bd netgear

New Contributor

 • 

75 Messages

9 years ago

Microsoft Windows [Version 10.0.14393]
(c) 2016 Microsoft Corporation. All rights reserved.

C:\Users\mike>netstat -aon

Active Connections

Proto Local Address Foreign Address State PID
TCP 0.0.0.0:80 0.0.0.0:0 LISTENING 4
TCP 0.0.0.0:135 0.0.0.0:0 LISTENING 976
TCP 0.0.0.0:445 0.0.0.0:0 LISTENING 4
TCP 0.0.0.0:1801 0.0.0.0:0 LISTENING 3524
TCP 0.0.0.0:2103 0.0.0.0:0 LISTENING 3524
TCP 0.0.0.0:2105 0.0.0.0:0 LISTENING 3524
TCP 0.0.0.0:2107 0.0.0.0:0 LISTENING 3524
TCP 0.0.0.0:2869 0.0.0.0:0 LISTENING 4
TCP 0.0.0.0:5357 0.0.0.0:0 LISTENING 4
TCP 0.0.0.0:7680 0.0.0.0:0 LISTENING 812
TCP 0.0.0.0:15600 0.0.0.0:0 LISTENING 4
TCP 0.0.0.0:17729 0.0.0.0:0 LISTENING 3552
TCP 0.0.0.0:27036 0.0.0.0:0 LISTENING 8420
TCP 0.0.0.0:49664 0.0.0.0:0 LISTENING 684
TCP 0.0.0.0:49665 0.0.0.0:0 LISTENING 812
TCP 0.0.0.0:49666 0.0.0.0:0 LISTENING 1108
TCP 0.0.0.0:49667 0.0.0.0:0 LISTENING 2060
TCP 0.0.0.0:49668 0.0.0.0:0 LISTENING 3668
TCP 0.0.0.0:49669 0.0.0.0:0 LISTENING 3524
TCP 0.0.0.0:49688 0.0.0.0:0 LISTENING 744
TCP 0.0.0.0:49758 0.0.0.0:0 LISTENING 756
TCP 127.0.0.1:3212 0.0.0.0:0 LISTENING 3684
TCP 127.0.0.1:3213 0.0.0.0:0 LISTENING 3684
TCP 127.0.0.1:4370 0.0.0.0:0 LISTENING 7600
TCP 127.0.0.1:4380 0.0.0.0:0 LISTENING 7600
TCP 127.0.0.1:5939 0.0.0.0:0 LISTENING 3216
TCP 127.0.0.1:9990 0.0.0.0:0 LISTENING 3444
TCP 127.0.0.1:12025 0.0.0.0:0 LISTENING 1900
TCP 127.0.0.1:12110 0.0.0.0:0 LISTENING 1900
TCP 127.0.0.1:12119 0.0.0.0:0 LISTENING 1900
TCP 127.0.0.1:12143 0.0.0.0:0 LISTENING 1900
TCP 127.0.0.1:12465 0.0.0.0:0 LISTENING 1900
TCP 127.0.0.1:12563 0.0.0.0:0 LISTENING 1900
TCP 127.0.0.1:12993 0.0.0.0:0 LISTENING 1900
TCP 127.0.0.1:12995 0.0.0.0:0 LISTENING 1900
TCP 127.0.0.1:21320 0.0.0.0:0 LISTENING 3284
TCP 127.0.0.1:21321 0.0.0.0:0 LISTENING 3308
TCP 127.0.0.1:21323 0.0.0.0:0 LISTENING 3284
TCP 127.0.0.1:21327 0.0.0.0:0 LISTENING 9324
TCP 127.0.0.1:21332 0.0.0.0:0 LISTENING 3284
TCP 127.0.0.1:27275 0.0.0.0:0 LISTENING 1900
TCP 127.0.0.1:49761 127.0.0.1:49762 ESTABLISHED 1900
TCP 127.0.0.1:49762 127.0.0.1:49761 ESTABLISHED 1900
TCP 127.0.0.1:49763 0.0.0.0:0 LISTENING 1900
TCP 127.0.0.1:49764 127.0.0.1:49765 ESTABLISHED 1900
TCP 127.0.0.1:49765 127.0.0.1:49764 ESTABLISHED 1900
TCP 127.0.0.1:49766 0.0.0.0:0 LISTENING 1900
TCP 127.0.0.1:52061 127.0.0.1:21332 TIME_WAIT 0
TCP 127.0.0.1:65000 0.0.0.0:0 LISTENING 3508
TCP 192.168.0.4:139 0.0.0.0:0 LISTENING 4
TCP 192.168.0.4:49700 65.52.108.198:443 ESTABLISHED 2924
TCP 192.168.0.4:49775 77.234.42.35:80 ESTABLISHED 1900
TCP 192.168.0.4:49888 65.52.108.232:443 ESTABLISHED 812
TCP 192.168.0.4:50124 5.45.58.149:80 CLOSE_WAIT 1900
TCP 192.168.0.4:50376 64.233.160.125:5222 ESTABLISHED 4036
TCP 192.168.0.4:50391 64.233.168.188:5228 ESTABLISHED 6204
TCP 192.168.0.4:50731 216.58.194.78:443 CLOSE_WAIT 6204
TCP 192.168.0.4:50825 216.58.194.78:443 ESTABLISHED 6204
TCP 192.168.0.4:51850 50.57.196.159:80 ESTABLISHED 6204
TCP 192.168.0.4:51851 50.57.196.159:80 ESTABLISHED 6204
TCP 192.168.0.4:51852 50.57.196.159:80 ESTABLISHED 6204
TCP 192.168.0.4:51853 50.57.196.159:80 ESTABLISHED 6204
TCP 192.168.0.4:51854 50.57.196.159:80 ESTABLISHED 6204
TCP 192.168.0.4:51855 50.57.196.159:80 ESTABLISHED 6204
TCP 192.168.0.4:51862 209.18.104.20:443 ESTABLISHED 6204
TCP 192.168.0.4:51906 208.74.205.20:443 TIME_WAIT 0
TCP 192.168.0.4:51907 208.74.205.20:443 TIME_WAIT 0
TCP 192.168.0.4:51910 50.97.40.233:443 ESTABLISHED 6204
TCP 192.168.0.4:51911 104.16.26.235:443 ESTABLISHED 6204
TCP 192.168.0.4:51912 129.152.38.68:443 ESTABLISHED 6204
TCP 192.168.0.4:51913 129.152.38.68:443 TIME_WAIT 0
TCP 192.168.0.4:51914 129.152.38.68:443 TIME_WAIT 0
TCP 192.168.0.4:51915 129.152.38.68:443 TIME_WAIT 0
TCP 192.168.0.4:51918 72.21.91.97:443 ESTABLISHED 6204
TCP 192.168.0.4:51922 104.16.24.35:443 ESTABLISHED 6204
TCP 192.168.0.4:51925 23.219.163.10:80 TIME_WAIT 0
TCP 192.168.0.4:51926 23.219.163.10:80 TIME_WAIT 0
TCP 192.168.0.4:51927 23.219.163.10:80 TIME_WAIT 0
TCP 192.168.0.4:51928 23.219.163.10:80 TIME_WAIT 0
TCP 192.168.0.4:51929 23.219.163.10:80 TIME_WAIT 0
TCP 192.168.0.4:52043 68.99.123.171:80 TIME_WAIT 0
TCP 192.168.0.4:52045 68.99.123.171:80 TIME_WAIT 0
TCP 192.168.0.4:52059 68.99.123.171:80 TIME_WAIT 0
TCP 192.168.0.4:52060 68.99.123.171:80 TIME_WAIT 0
TCP 192.168.0.4:52067 216.58.194.34:80 ESTABLISHED 6204
TCP 192.168.0.4:52068 216.58.194.34:80 ESTABLISHED 6204
TCP 192.168.0.4:52069 216.58.194.34:80 ESTABLISHED 6204
TCP 192.168.0.4:52073 68.67.73.20:80 ESTABLISHED 6204
TCP 192.168.0.4:52074 68.67.73.20:80 ESTABLISHED 6204
TCP 192.168.0.4:52075 68.67.73.20:80 CLOSE_WAIT 6204
TCP 192.168.0.4:52076 68.67.73.20:80 ESTABLISHED 6204
TCP 192.168.0.4:52077 68.67.73.20:80 ESTABLISHED 6204
TCP 192.168.0.4:52078 68.67.73.20:80 ESTABLISHED 6204
TCP 192.168.0.4:52079 54.230.122.41:80 CLOSE_WAIT 6204
TCP 192.168.0.4:52080 54.230.122.41:80 CLOSE_WAIT 6204
TCP 192.168.0.4:52081 54.230.122.41:80 CLOSE_WAIT 6204
TCP 192.168.0.4:52091 104.16.24.35:80 ESTABLISHED 6204
TCP 192.168.0.4:52092 104.16.24.35:80 ESTABLISHED 6204
TCP 192.168.0.4:52093 104.16.27.235:80 ESTABLISHED 6204
TCP 192.168.0.4:52094 104.16.25.235:80 ESTABLISHED 6204
TCP 192.168.0.4:52095 104.16.27.235:80 CLOSE_WAIT 6204
TCP 192.168.0.4:52096 23.218.224.91:80 ESTABLISHED 6204
TCP [::]:80 [::]:0 LISTENING 4
TCP [::]:135 [::]:0 LISTENING 976
TCP [::]:445 [::]:0 LISTENING 4
TCP [::]:1801 [::]:0 LISTENING 3524
TCP [::]:2103 [::]:0 LISTENING 3524
TCP [::]:2105 [::]:0 LISTENING 3524
TCP [::]:2107 [::]:0 LISTENING 3524
TCP [::]:2869 [::]:0 LISTENING 4
TCP [::]:5357 [::]:0 LISTENING 4
TCP [::]:7680 [::]:0 LISTENING 812
TCP [::]:15600 [::]:0 LISTENING 4
TCP [::]:49664 [::]:0 LISTENING 684
TCP [::]:49665 [::]:0 LISTENING 812
TCP [::]:49666 [::]:0 LISTENING 1108
TCP [::]:49667 [::]:0 LISTENING 2060
TCP [::]:49668 [::]:0 LISTENING 3668
TCP [::]:49669 [::]:0 LISTENING 3524
TCP [::]:49688 [::]:0 LISTENING 744
TCP [::]:49758 [::]:0 LISTENING 756
TCP [::1]:12025 [::]:0 LISTENING 1900
TCP [::1]:12110 [::]:0 LISTENING 1900
TCP [::1]:12119 [::]:0 LISTENING 1900
TCP [::1]:12143 [::]:0 LISTENING 1900
TCP [::1]:12465 [::]:0 LISTENING 1900
TCP [::1]:12563 [::]:0 LISTENING 1900
TCP [::1]:12993 [::]:0 LISTENING 1900
TCP [::1]:12995 [::]:0 LISTENING 1900
TCP [::1]:27275 [::]:0 LISTENING 1900
TCP [::1]:49892 [::]:0 LISTENING 9656
TCP [2600:8807:82c0:9c00:280a:7831:800d:32f6]:51880 [2607:f8b0:4000:80a::2008]:443 TIME_WAIT 0
TCP [2600:8807:82c0:9c00:280a:7831:800d:32f6]:51884 [2607:f8b0:4000:80a::2008]:443 ESTABLISHED 7548
TCP [2600:8807:82c0:9c00:280a:7831:800d:32f6]:51898 [2607:f8b0:4002:c03::93]:443 ESTABLISHED 6204
TCP [2600:8807:82c0:9c00:280a:7831:800d:32f6]:51899 [2607:f8b0:4000:80a::200e]:443 ESTABLISHED 6204
TCP [2600:8807:82c0:9c00:280a:7831:800d:32f6]:51923 [2607:f8b0:4000:803::200e]:443 ESTABLISHED 6204
TCP [2600:8807:82c0:9c00:280a:7831:800d:32f6]:51924 [2607:f8b0:4000:802::200e]:443 ESTABLISHED 6204
TCP [2600:8807:82c0:9c00:280a:7831:800d:32f6]:52063 [2607:f8b0:4000:80a::2003]:443 ESTABLISHED 6204
TCP [2600:8807:82c0:9c00:280a:7831:800d:32f6]:52064 [2607:f8b0:4000:801::200a]:80 ESTABLISHED 6204
TCP [2600:8807:82c0:9c00:280a:7831:800d:32f6]:52065 [2607:f8b0:4000:801::200a]:80 ESTABLISHED 6204
TCP [2600:8807:82c0:9c00:280a:7831:800d:32f6]:52066 [2607:f8b0:4000:801::200a]:80 ESTABLISHED 6204
TCP [2600:8807:82c0:9c00:280a:7831:800d:32f6]:52070 [2607:f8b0:4000:80c::2002]:80 ESTABLISHED 6204
TCP [2600:8807:82c0:9c00:280a:7831:800d:32f6]:52071 [2607:f8b0:4000:80c::2002]:80 ESTABLISHED 6204
TCP [2600:8807:82c0:9c00:280a:7831:800d:32f6]:52072 [2607:f8b0:4000:80c::2002]:80 ESTABLISHED 6204
TCP [2600:8807:82c0:9c00:280a:7831:800d:32f6]:52085 [2607:f8b0:4000:80c::2002]:80 ESTABLISHED 6204
TCP [2600:8807:82c0:9c00:280a:7831:800d:32f6]:52086 [2607:f8b0:4000:80c::2002]:80 ESTABLISHED 6204
TCP [2600:8807:82c0:9c00:280a:7831:800d:32f6]:52087 [2607:f8b0:4000:80c::2002]:80 ESTABLISHED 6204
TCP [2600:8807:82c0:9c00:280a:7831:800d:32f6]:52088 [2607:f8b0:4000:800::2001]:80 ESTABLISHED 6204
TCP [2600:8807:82c0:9c00:280a:7831:800d:32f6]:52089 [2607:f8b0:4000:800::2001]:80 ESTABLISHED 6204
TCP [2600:8807:82c0:9c00:280a:7831:800d:32f6]:52090 [2607:f8b0:4000:800::2001]:80 ESTABLISHED 6204
TCP [2600:8807:82c0:9c00:280a:7831:800d:32f6]:52097 [2607:f8b0:4003:c03::9c]:443 ESTABLISHED 6204
UDP 0.0.0.0:3544 *:* 812
UDP 0.0.0.0:3702 *:* 1432
UDP 0.0.0.0:3702 *:* 1432
UDP 0.0.0.0:3702 *:* 6140
UDP 0.0.0.0:3702 *:* 6140
UDP 0.0.0.0:3702 *:* 2996
UDP 0.0.0.0:3702 *:* 2996
UDP 0.0.0.0:5050 *:* 1432
UDP 0.0.0.0:5353 *:* 6204
UDP 0.0.0.0:5353 *:* 1848
UDP 0.0.0.0:5353 *:* 6204
UDP 0.0.0.0:5353 *:* 6204
UDP 0.0.0.0:5355 *:* 1848
UDP 0.0.0.0:21328 *:* 3284
UDP 0.0.0.0:27036 *:* 8420
UDP 0.0.0.0:51498 *:* 8420
UDP 0.0.0.0:51757 *:* 1900
UDP 0.0.0.0:57454 *:* 3216
UDP 0.0.0.0:57456 *:* 2060
UDP 0.0.0.0:57457 *:* 3284
UDP 0.0.0.0:59924 *:* 2060
UDP 0.0.0.0:60986 *:* 1900
UDP 0.0.0.0:60987 *:* 1900
UDP 0.0.0.0:62023 *:* 1432
UDP 0.0.0.0:62027 *:* 2996
UDP 0.0.0.0:62755 *:* 6140
UDP 0.0.0.0:63243 *:* 8420
UDP 0.0.0.0:64327 *:* 6204
UDP 0.0.0.0:64329 *:* 6204
UDP 127.0.0.1:1900 *:* 6140
UDP 127.0.0.1:48200 *:* 5832
UDP 127.0.0.1:48201 *:* 6280
UDP 127.0.0.1:48202 *:* 8088
UDP 127.0.0.1:50091 *:* 8088
UDP 127.0.0.1:50092 *:* 8088
UDP 127.0.0.1:50093 *:* 8088
UDP 127.0.0.1:50094 *:* 8088
UDP 127.0.0.1:50095 *:* 8088
UDP 127.0.0.1:50096 *:* 8088
UDP 127.0.0.1:50097 *:* 8088
UDP 127.0.0.1:50098 *:* 8088
UDP 127.0.0.1:55607 *:* 1900
UDP 127.0.0.1:55609 *:* 1900
UDP 127.0.0.1:56097 *:* 8088
UDP 127.0.0.1:56098 *:* 8088
UDP 127.0.0.1:57458 *:* 6308
UDP 127.0.0.1:57459 *:* 6308
UDP 127.0.0.1:57460 *:* 6308
UDP 127.0.0.1:57461 *:* 6308
UDP 127.0.0.1:59150 *:* 3508
UDP 127.0.0.1:59848 *:* 8088
UDP 127.0.0.1:62022 *:* 6140
UDP 127.0.0.1:63726 *:* 7804
UDP 127.0.0.1:65000 *:* 3508
UDP 192.168.0.4:137 *:* 4
UDP 192.168.0.4:138 *:* 4
UDP 192.168.0.4:1900 *:* 6140
UDP 192.168.0.4:5353 *:* 3216
UDP 192.168.0.4:51395 *:* 812
UDP 192.168.0.4:62021 *:* 6140
UDP [::]:3702 *:* 1432
UDP [::]:3702 *:* 2996
UDP [::]:3702 *:* 6140
UDP [::]:3702 *:* 6140
UDP [::]:3702 *:* 1432
UDP [::]:3702 *:* 2996
UDP [::]:5353 *:* 1848
UDP [::]:5353 *:* 6204
UDP [::]:5353 *:* 6204
UDP [::]:5355 *:* 1848
UDP [::]:57455 *:* 3216
UDP [::]:62024 *:* 1432
UDP [::]:62028 *:* 2996
UDP [::]:62756 *:* 6140
UDP [::]:64327 *:* 6204
UDP [::]:64329 *:* 6204
UDP [::1]:1900 *:* 6140
UDP [::1]:5353 *:* 3216
UDP [::1]:62020 *:* 6140
UDP [fe80::e06c:5c18:410f:f77b%4]:1900 *:* 6140
UDP [fe80::e06c:5c18:410f:f77b%4]:62019 *:* 6140

C:\Users\mike>

Valued Contributor II

 • 

2.8K Messages

9 years ago

There is some normal web traffic in the results, making it harder to read. Could you do it again, but this time make sure to close all browser tabs and windows, including this one before doing the test? That way it only shows traffic you aren't directly using. 

Also make sure to use netstat -a and not just netstat so it shows all the connections.

Finally, feel free to edit your previous post with the new data to keep things tidy.

Recent Discussions

View More

Loading...