Quantcast
Channel: Cox forum - dslreports.com
Viewing all articles
Browse latest Browse all 5880

Getting Slow Routing Connecticut -> Rhode Island -> NYC -> Boston

$
0
0
I'm using Cox internet in Connecticut. Another person using Cox four towns away complained to me about slow response using Windows remote desktop services to a server outside of Boston that's connected through Verizon FIOS service. I logged in to the server and see the same problem. I can press a key several times, and it takes a couple seconds to see the result. Mouse clicks have a long delay too. I did a tracert from my location, and see that there's a problem in New York. If I do the tracert starting at the Boston location, it looks fine. Connecticut to Boston trace: Tracing route to static-71-184-xxx-xxx.bstnma.fios.verizon.net [71.184.xxx.xxx] over a maximum of 30 hops: 1 4 ms 4 ms 4 ms XXXXXX [192.168.1.1] 2 839 ms 21 ms 17 ms 10.4.16.1 3 19 ms 19 ms 19 ms ip98-190-33-34.ri.ri.cox.net [98.190.33.34] 4 18 ms 18 ms 17 ms ip98-190-33-34.ri.ri.cox.net [98.190.33.34] 5 823 ms 22 ms 24 ms nyrkbprj01-ae3.0.rd.ny.cox.net [68.1.5.157] 6 1739 ms 1369 ms 2243 ms lag-22.ear2.NewYork1.Level3.net [4.35.90.1] 7 23 ms 24 ms 1359 ms 0.ae12.BR2.NYC4.ALTER.NET [204.255.173.53] 8 * * * Request timed out. 9 * * * Request timed out. 10 42 ms 39 ms 42 ms static-71-184-xxx-xxx.bstnma.fios.verizon.net [71.184.xxx.xxx] Trace complete. Boston to Connectcut trace: Tracing route to ip68-0-xxx.xxx.ri.ri.cox.net [68.0.xxx.xxx] over a maximum of 30 hops: 1 1 ms 1 ms 1 ms 192.168.2.1 2 6 ms 7 ms 7 ms L300.BSTNMA-VFTTP-121.verizon-gni.net [98.118.41.1] 3 11 ms 12 ms 12 ms G101-0-0-30.BSTNMA-LCR-21.verizon-gni.net [100.41.208.88] 4 * * * Request timed out. 5 * * * Request timed out. 6 17 ms 17 ms 16 ms 0.ae3.BR2.NYC4.ALTER.NET [140.222.231.133] 7 * * * Request timed out. 8 17 ms 17 ms 17 ms 4.35.90.2 9 23 ms 21 ms 21 ms provdsrj02-ae0.0.rd.ri.cox.net [68.1.0.49] 10 26 ms 25 ms 27 ms ip98-190-163-109.ri.ri.cox.net [98.190.163.109] 11 26 ms 24 ms 23 ms ip98-190-163-109.ri.ri.cox.net [98.190.163.109] 12 44 ms 34 ms 45 ms ip68-0-228-225.ri.ri.cox.net [68.0.xxx.xxx] Trace complete. I tried doing an online chat with Cox, but after several "Thank you for your patience" messages, the session terminated after about an hour with no result. I stopped by a Cox store this evening, and they're going to send someone over tomorrow. I'm 99.9% sure there's nothing wrong here, since it looks to me like the problem is somewhere between Cox and Level 3 in New York. I figure the "Request timed out" stops are the NSA routers in there :-) Even a Ping directly to 4.35.90.1 gives me times between 22ms and over 700ms. Does anyone know how to get this situation looked at? Thanks, Paul

Viewing all articles
Browse latest Browse all 5880

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>