frazierwa
join:2001-12-14
Redmond, WA
1 edit | [AZ] Frequent and intermittent loss of connectivity
I have had an issue when attempting to access my computer in AZ on the COX network via RDP. After connecting to the computer it will spontaneously disconnect after a minute or two and I can't connect again for a couple of minutes.
I set up an infinite ping to yahoo.com from the computer on the Cox network and found that the latency was good for several minutes and then it would time out for several minutes, then start receiving replies again. This cycle continues over and over.
I checked the log on my cable modem (Moto Surfboard) and found several repeating entries such as:
(1)Map Reject - Downstream Traffic Flow Not Mapped to BPI+ SAID (EC=8)
(2) 5-Warning D103.0 DHCP RENEW WARNING - Field invalid in response
(3) 5-Warning B605.10 Map Reject - Downstream Traffic Flow Not Mapped to BPI+ SAID (EC=8)
Any idea what is going on?
Thanks,
Howard Frazier |
|
CoxTOC1
join:2007-05-15
Newport News, VA | You can safely ignore those errors, they are for features that your modem does not support. |
|
RINetworkGuy
join:2008-12-29
Providence, RI
| reply to frazierwa
Standard Questions: Is the computer your connecting to on WiFi or using an Ethernet cable? Have you been able to reproduce the error when you bypass your router (assuming you have one) and connect the PC directly to the Modem?
I've had friends and family make this same statement, and most of the time when they bypass their router, or go from WiFi to a cable the problem goes away.
--
All posts are my own opinion and do not represent anything other that that. |
|
frazierwa
join:2001-12-14
Redmond, WA
| reply to frazierwa
My computer is connected via Ethernet cable to a Dlink DIR-655 router and that router is connected directly to my cable modem.
I see the same type of intermittent failure whether I ping from the computer on the Cox network to the Internet or from the Internet to the computer on the Cox network. It appears that the communication link between my cable modem and the the Internet is regularly failing. |
|
RINetworkGuy
join:2008-12-29
Providence, RI | But have you bypassed your router and connected the PC directly to the modem?
--
All posts are my own opinion and do not represent anything other that that. |
|
frazierwa
join:2001-12-14
Redmond, WA
| reply to RINetworkGuy
I am currently out of the area so I can't change the physical connection. I was able to administratively connect to the Dlink router and configure it to respond to ping. When I ping that router (which is directly connected to the cable modem) I get the same results. I haven't heard any reports about the DIR-655 router having chronic issues such as the symptoms I am experiencing. |
|
CoxTech1
VIP
join:2002-04-25
Chesapeake, VA
2 edits | When I ping your modem I get this:
PING xx.xx.xx.xx (xx.xx.xx.xx) 600(628) bytes of data.
608 bytes from xx.xx.xx.xx: icmp_seq=0 ttl=58 time=12.2 ms
608 bytes from xx.xx.xx.xx: icmp_seq=1 ttl=58 time=15.8 ms
608 bytes from xx.xx.xx.xx: icmp_seq=2 ttl=58 time=13.9 ms
608 bytes from xx.xx.xx.xx: icmp_seq=3 ttl=58 time=15.9 ms
608 bytes from xx.xx.xx.xx: icmp_seq=4 ttl=58 time=15.9 ms
608 bytes from xx.xx.xx.xx: icmp_seq=5 ttl=58 time=13.9 ms
608 bytes from xx.xx.xx.xx: icmp_seq=6 ttl=58 time=11.3 ms
And now that your router is pingable I get this:
Pinging xx.xx.xx.xx with 32 bytes of data:
Reply from xx.xx.xx.xx: bytes=32 time=67ms TTL=57
Reply from xx.xx.xx.xx: bytes=32 time=64ms TTL=56
Reply from xx.xx.xx.xx: bytes=32 time=67ms TTL=57
Reply from xx.xx.xx.xx: bytes=32 time=104ms TTL=56
Reply from xx.xx.xx.xx: bytes=32 time=79ms TTL=56
Reply from xx.xx.xx.xx: bytes=32 time=68ms TTL=57
Reply from xx.xx.xx.xx: bytes=32 time=73ms TTL=56
Reply from xx.xx.xx.xx: bytes=32 time=647ms TTL=57
Reply from xx.xx.xx.xx: bytes=32 time=77ms TTL=57
Ping statistics for 72.222.248.243:
Packets: Sent = 9, Received = 9, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 64ms, Maximum = 647ms, Average = 138ms
This leads me to believe that the problem is something between the modem and the router. From experience I would say most likely the router although a modem problem cannot be ruled out until the router is bypassed and the connection tested again. Unfortunately I don't think you're going to be able to remotely resolve this issue.
Also, it still appears that there is no service listening on the default RDP port suggesting that either you're using a different port, the router isn't properly forwarding traffic, or the intended PC isn't listening. |
|
frazierwa
join:2001-12-14
Redmond, WA
| First, thanks very much for looking into this... it is a pain to troubleshoot this remotely.
Yes, I changed the port to 3391 to avoid using the standard and RPC is working although when the first period of 'drop out' occurs, it kills the session and it takes several minutes to reconnect.
The snippet you sent from your ping test is not surprising since it takes a couple of minutes for the first cluster of dropped pings occurs. Below is part of a longer test with the summary at the bottom and is typical of what I have been seeing (14% loss). What is particularly strange is the very predicable and repeatable pattern of; good connectivity, total loss, resumed connectivity. Even the short bouts of slightly higher latency repeats in a predicable pattern.
Reply from 72.222.248.243: bytes=32 time=701ms TTL=52
Reply from 72.222.248.243: bytes=32 time=64ms TTL=52
Reply from 72.222.248.243: bytes=32 time=1282ms TTL=52
Reply from 72.222.248.243: bytes=32 time=55ms TTL=52
Reply from 72.222.248.243: bytes=32 time=1415ms TTL=52
Reply from 72.222.248.243: bytes=32 time=55ms TTL=52
Request timed out.
Request timed out.
Request timed out.
Reply from 72.222.248.243: bytes=32 time=56ms TTL=52
Reply from 72.222.248.243: bytes=32 time=63ms TTL=52
Reply from 72.222.248.243: bytes=32 time=59ms TTL=52
Reply from 72.222.248.243: bytes=32 time=58ms TTL=52
Reply from 72.222.248.243: bytes=32 time=58ms TTL=52
Reply from 72.222.248.243: bytes=32 time=60ms TTL=52
Reply from 72.222.248.243: bytes=32 time=58ms TTL=52
Reply from 72.222.248.243: bytes=32 time=58ms TTL=52
Reply from 72.222.248.243: bytes=32 time=59ms TTL=52
Reply from 72.222.248.243: bytes=32 time=59ms TTL=52
Reply from 72.222.248.243: bytes=32 time=58ms TTL=52
Reply from 72.222.248.243: bytes=32 time=56ms TTL=52
Reply from 72.222.248.243: bytes=32 time=59ms TTL=52
Reply from 72.222.248.243: bytes=32 time=55ms TTL=52
Reply from 72.222.248.243: bytes=32 time=70ms TTL=52
Reply from 72.222.248.243: bytes=32 time=96ms TTL=52
Reply from 72.222.248.243: bytes=32 time=60ms TTL=52
Reply from 72.222.248.243: bytes=32 time=58ms TTL=52
Reply from 72.222.248.243: bytes=32 time=57ms TTL=52
Reply from 72.222.248.243: bytes=32 time=751ms TTL=52
Reply from 72.222.248.243: bytes=32 time=61ms TTL=52
Reply from 72.222.248.243: bytes=32 time=1519ms TTL=52
Reply from 72.222.248.243: bytes=32 time=58ms TTL=52
Reply from 72.222.248.243: bytes=32 time=1800ms TTL=52
Reply from 72.222.248.243: bytes=32 time=57ms TTL=52
Reply from 72.222.248.243: bytes=32 time=1715ms TTL=52
Reply from 72.222.248.243: bytes=32 time=58ms TTL=52
Reply from 72.222.248.243: bytes=32 time=59ms TTL=52
Reply from 72.222.248.243: bytes=32 time=58ms TTL=52
Reply from 72.222.248.243: bytes=32 time=57ms TTL=52
Reply from 72.222.248.243: bytes=32 time=55ms TTL=52
Reply from 72.222.248.243: bytes=32 time=58ms TTL=52
Reply from 72.222.248.243: bytes=32 time=54ms TTL=52
Reply from 72.222.248.243: bytes=32 time=58ms TTL=52
Reply from 72.222.248.243: bytes=32 time=56ms TTL=52
Reply from 72.222.248.243: bytes=32 time=59ms TTL=52
Reply from 72.222.248.243: bytes=32 time=66ms TTL=52
Reply from 72.222.248.243: bytes=32 time=57ms TTL=52
Reply from 72.222.248.243: bytes=32 time=59ms TTL=52
Reply from 72.222.248.243: bytes=32 time=61ms TTL=52
Reply from 72.222.248.243: bytes=32 time=59ms TTL=52
Reply from 72.222.248.243: bytes=32 time=56ms TTL=52
Reply from 72.222.248.243: bytes=32 time=61ms TTL=52
Reply from 72.222.248.243: bytes=32 time=61ms TTL=52
Reply from 72.222.248.243: bytes=32 time=57ms TTL=52
Reply from 72.222.248.243: bytes=32 time=60ms TTL=52
Reply from 72.222.248.243: bytes=32 time=60ms TTL=52
Reply from 72.222.248.243: bytes=32 time=68ms TTL=52
Reply from 72.222.248.243: bytes=32 time=59ms TTL=52
Reply from 72.222.248.243: bytes=32 time=57ms TTL=52
Reply from 72.222.248.243: bytes=32 time=59ms TTL=52
Reply from 72.222.248.243: bytes=32 time=57ms TTL=52
Reply from 72.222.248.243: bytes=32 time=57ms TTL=52
Reply from 72.222.248.243: bytes=32 time=55ms TTL=52
Reply from 72.222.248.243: bytes=32 time=74ms TTL=52
Reply from 72.222.248.243: bytes=32 time=56ms TTL=52
Reply from 72.222.248.243: bytes=32 time=86ms TTL=52
Reply from 72.222.248.243: bytes=32 time=58ms TTL=52
Reply from 72.222.248.243: bytes=32 time=73ms TTL=52
Reply from 72.222.248.243: bytes=32 time=60ms TTL=52
Reply from 72.222.248.243: bytes=32 time=57ms TTL=52
Reply from 72.222.248.243: bytes=32 time=62ms TTL=52
Reply from 72.222.248.243: bytes=32 time=55ms TTL=52
Reply from 72.222.248.243: bytes=32 time=58ms TTL=52
Reply from 72.222.248.243: bytes=32 time=62ms TTL=52
Reply from 72.222.248.243: bytes=32 time=59ms TTL=52
Reply from 72.222.248.243: bytes=32 time=62ms TTL=52
Reply from 72.222.248.243: bytes=32 time=60ms TTL=52
Reply from 72.222.248.243: bytes=32 time=57ms TTL=52
Reply from 72.222.248.243: bytes=32 time=57ms TTL=52
Reply from 72.222.248.243: bytes=32 time=58ms TTL=52
Reply from 72.222.248.243: bytes=32 time=59ms TTL=52
Reply from 72.222.248.243: bytes=32 time=67ms TTL=52
Reply from 72.222.248.243: bytes=32 time=59ms TTL=52
Reply from 72.222.248.243: bytes=32 time=59ms TTL=52
Reply from 72.222.248.243: bytes=32 time=94ms TTL=52
Reply from 72.222.248.243: bytes=32 time=260ms TTL=52
Reply from 72.222.248.243: bytes=32 time=80ms TTL=52
Reply from 72.222.248.243: bytes=32 time=73ms TTL=52
Reply from 72.222.248.243: bytes=32 time=65ms TTL=52
Reply from 72.222.248.243: bytes=32 time=105ms TTL=52
Reply from 72.222.248.243: bytes=32 time=55ms TTL=52
Reply from 72.222.248.243: bytes=32 time=76ms TTL=52
Reply from 72.222.248.243: bytes=32 time=70ms TTL=52
Reply from 72.222.248.243: bytes=32 time=58ms TTL=52
Reply from 72.222.248.243: bytes=32 time=87ms TTL=52
Reply from 72.222.248.243: bytes=32 time=82ms TTL=52
Reply from 72.222.248.243: bytes=32 time=60ms TTL=52
Reply from 72.222.248.243: bytes=32 time=73ms TTL=52
Reply from 72.222.248.243: bytes=32 time=71ms TTL=52
Reply from 72.222.248.243: bytes=32 time=61ms TTL=52
Reply from 72.222.248.243: bytes=32 time=73ms TTL=52
Reply from 72.222.248.243: bytes=32 time=65ms TTL=52
Reply from 72.222.248.243: bytes=32 time=73ms TTL=52
Reply from 72.222.248.243: bytes=32 time=79ms TTL=52
Reply from 72.222.248.243: bytes=32 time=65ms TTL=52
Reply from 72.222.248.243: bytes=32 time=57ms TTL=52
Reply from 72.222.248.243: bytes=32 time=58ms TTL=52
Reply from 72.222.248.243: bytes=32 time=74ms TTL=52
Reply from 72.222.248.243: bytes=32 time=64ms TTL=52
Reply from 72.222.248.243: bytes=32 time=61ms TTL=52
Reply from 72.222.248.243: bytes=32 time=63ms TTL=52
Reply from 72.222.248.243: bytes=32 time=73ms TTL=52
Reply from 72.222.248.243: bytes=32 time=65ms TTL=52
Reply from 72.222.248.243: bytes=32 time=68ms TTL=52
Reply from 72.222.248.243: bytes=32 time=55ms TTL=52
Reply from 72.222.248.243: bytes=32 time=68ms TTL=52
Reply from 72.222.248.243: bytes=32 time=57ms TTL=52
Reply from 72.222.248.243: bytes=32 time=74ms TTL=52
Reply from 72.222.248.243: bytes=32 time=82ms TTL=52
Reply from 72.222.248.243: bytes=32 time=68ms TTL=52
Reply from 72.222.248.243: bytes=32 time=59ms TTL=52
Reply from 72.222.248.243: bytes=32 time=66ms TTL=52
Reply from 72.222.248.243: bytes=32 time=62ms TTL=52
Reply from 72.222.248.243: bytes=32 time=57ms TTL=52
Reply from 72.222.248.243: bytes=32 time=58ms TTL=52
Reply from 72.222.248.243: bytes=32 time=64ms TTL=52
Reply from 72.222.248.243: bytes=32 time=72ms TTL=52
Reply from 72.222.248.243: bytes=32 time=125ms TTL=52
Reply from 72.222.248.243: bytes=32 time=67ms TTL=52
Reply from 72.222.248.243: bytes=32 time=59ms TTL=52
Reply from 72.222.248.243: bytes=32 time=64ms TTL=52
Reply from 72.222.248.243: bytes=32 time=59ms TTL=52
Reply from 72.222.248.243: bytes=32 time=59ms TTL=52
Reply from 72.222.248.243: bytes=32 time=71ms TTL=52
Reply from 72.222.248.243: bytes=32 time=68ms TTL=52
Reply from 72.222.248.243: bytes=32 time=69ms TTL=52
Request timed out.
Request timed out.
Reply from 72.222.248.243: bytes=32 time=73ms TTL=52
Reply from 72.222.248.243: bytes=32 time=58ms TTL=52
Reply from 72.222.248.243: bytes=32 time=57ms TTL=52
Reply from 72.222.248.243: bytes=32 time=58ms TTL=52
Reply from 72.222.248.243: bytes=32 time=55ms TTL=52
Reply from 72.222.248.243: bytes=32 time=57ms TTL=52
Reply from 72.222.248.243: bytes=32 time=55ms TTL=52
Reply from 72.222.248.243: bytes=32 time=57ms TTL=52
Reply from 72.222.248.243: bytes=32 time=54ms TTL=52
Reply from 72.222.248.243: bytes=32 time=56ms TTL=52
Reply from 72.222.248.243: bytes=32 time=55ms TTL=52
Reply from 72.222.248.243: bytes=32 time=56ms TTL=52
Reply from 72.222.248.243: bytes=32 time=61ms TTL=52
Reply from 72.222.248.243: bytes=32 time=66ms TTL=52
Reply from 72.222.248.243: bytes=32 time=57ms TTL=52
Reply from 72.222.248.243: bytes=32 time=55ms TTL=52
Reply from 72.222.248.243: bytes=32 time=59ms TTL=52
Reply from 72.222.248.243: bytes=32 time=56ms TTL=52
Reply from 72.222.248.243: bytes=32 time=58ms TTL=52
Reply from 72.222.248.243: bytes=32 time=153ms TTL=52
Reply from 72.222.248.243: bytes=32 time=75ms TTL=52
Reply from 72.222.248.243: bytes=32 time=59ms TTL=52
Reply from 72.222.248.243: bytes=32 time=57ms TTL=52
Reply from 72.222.248.243: bytes=32 time=841ms TTL=52
Reply from 72.222.248.243: bytes=32 time=56ms TTL=52
Reply from 72.222.248.243: bytes=32 time=1659ms TTL=52
Reply from 72.222.248.243: bytes=32 time=60ms TTL=52
Reply from 72.222.248.243: bytes=32 time=1853ms TTL=52
Reply from 72.222.248.243: bytes=32 time=62ms TTL=52
Reply from 72.222.248.243: bytes=32 time=1753ms TTL=52
Reply from 72.222.248.243: bytes=32 time=57ms TTL=52
Reply from 72.222.248.243: bytes=32 time=56ms TTL=52
Reply from 72.222.248.243: bytes=32 time=57ms TTL=52
Reply from 72.222.248.243: bytes=32 time=59ms TTL=52
Reply from 72.222.248.243: bytes=32 time=57ms TTL=52
Reply from 72.222.248.243: bytes=32 time=67ms TTL=52
Reply from 72.222.248.243: bytes=32 time=63ms TTL=52
Reply from 72.222.248.243: bytes=32 time=66ms TTL=52
Reply from 72.222.248.243: bytes=32 time=59ms TTL=52
Reply from 72.222.248.243: bytes=32 time=69ms TTL=52
Reply from 72.222.248.243: bytes=32 time=65ms TTL=52
Reply from 72.222.248.243: bytes=32 time=70ms TTL=52
Reply from 72.222.248.243: bytes=32 time=68ms TTL=52
Reply from 72.222.248.243: bytes=32 time=66ms TTL=52
Reply from 72.222.248.243: bytes=32 time=58ms TTL=52
Reply from 72.222.248.243: bytes=32 time=68ms TTL=52
Ping statistics for 72.222.248.243:
Packets: Sent = 304, Received = 259, Lost = 45 (14% loss),
Approximate round trip times in milli-seconds:
Minimum = 54ms, Maximum = 2045ms, Average = 163ms
Control-C |
|
CoxTech1
VIP
join:2002-04-25
Chesapeake, VA | Off hand, it sounds like the router is getting saturated with too much traffic. Is there somebody on site that can try bypassing it to see if the problem still occurs? |
|
frazierwa
join:2001-12-14
Redmond, WA | Nobody there for about a week and then I can try the bypass. The traffic on the router interface should be very low since the only traffic is what I generate when I connect via RDP.
Thanks again for your efforts.
Howard |
|
DrThodt_
@cox.net | Try to remotely reboot your router. It's definitely congested. And check your LAN to make sure no strays are on your wifi. |
|
frazierwa
join:2001-12-14
Redmond, WA
| I rebooted the router, verified that there is one PC on the LAN and two IP cameras communicating with the PC (DVR). None of that video should be going across the WAN... just LAN traffic. One of the cameras is WiFi and that is the only wireless client on the router.
Based on that observation, I wouldn't expect congestion except possibly on the LAN which shouldn't affect ping performance over the WAN. Also, the video traffic is pretty consistent and the ping loss is intermittent. I'm officially stumped. My guess is that either the router or the cable modem is bad since Cox has verified healthy communication on their link. |
|
CoxTech1
VIP
join:2002-04-25
Chesapeake, VA
| There could be something to the video issue. Even though that traffic isn't crossing to the WAN side of the router the router still has to processs that traffic and make the decision as to whether or not it needs to cross the WAN. Switches built into routers don't quite function the same as a dedicated switch and in some cases performance issues can result. |
|
frazierwa
join:2001-12-14
Redmond, WA
| Good point... I'll disable the cameras and see if there is an improvement.
FYI, after trolling around on the dlink support site, I tried a couple of their suggestions:
Reduced MTU from 1500 to 1400
Set the WAN port speed to 10Mbps (from the default of auto select)
After a reboot of the router, no improvement was evident. |
|
CoxTech1
VIP
join:2002-04-25
Chesapeake, VA | Setting your WAN port to 10Mbit would only serve to slow you down even further. You're provisioned for a 9Mbit/sec connection on the downstream and capping your router at 10 would only disable PowerBoost. |
|
frazierwa
join:2001-12-14
Redmond, WA
| I disabled the cameras to reduce the LAN traffic and then repeated the ping tests. No substantial change occurred. 12% loss from host PC to the Internet and 10% loss from the Internet to the router. When I return next week I'll repeat the tests when connected directly to the cable modem to try to isolate the fault.
I changed my WAN port speed back to "auto-select" to take advantage of PowerBoost.... I guess I thought that was a marketing term rather than a technology  . |
|
