COMCAST!!

[Stephanie Belser]

Same here. I couldn't log in until I switched over to a VPN.

Same old, same old.

[Terry Carraway]

Still no issues here, with or without ExpressVPN. My Comcast works fine.

[Russell Holton]

Still having issues at work. Seems fine in the morning, but before end of day it goes out. It's almost like I'm being routed though someone's work machine on the East Coast.

[Ralph Jones]

It's almost like I'm being routed though someone's work machine on the East Coast.

What's the last URL you see when you do a tracert dev.avsig.com, and the final IP address that it doesn't reach?

[Russell Holton]

The last named hop (#14) eqix-da1.a100.1.com
the last listed IP (#26) 52.95.2.194

[Ralph Jones]

OK, that differs from the one where I lose it, so this is something happening in multiple places.

[Ray Tackett]

I would love to bring some tracert data here for the experts, but tracert never gets anywhere, even with perfectly reachable sites. Out of 30 hops, I get 20+ timeouts, which is definitely not the case when I use a browser to visit a site. It's generally instantaneous. I looked at the tracert command line options, but none seemed relevant to the issue.

[John O'Shaughnessy [FCM]]

I'm not having any issues reaching the forum. I'm also on Comcast. Here's a screen grab from PingPlotter -- a neat tool combing Ping and Traceroute output. The destination is unreachable with Ping, so ICMP echo must be disabled somewhere along the route, but at least it shows my path through Comcast to whatever network is 52.93.x.y

[Russell Holton]

I would love to bring some tracert data here for the experts, but tracert never gets anywhere, even with perfectly reachable sites. Out of 30 hops, I get 20+ timeouts, which is definitely not the case when I use a browser to visit a site. It's generally instantaneous. I looked at the tracert command line options, but none seemed relevant to the issue.

Don't know much about routing, but I wouldn't be surprised if a bad table sends my packets in to a dead-end tree where the only route is the one it just came from.

[Terry Carraway]

Here are my Tracert without and with my VPN.

The one starting with IP 192.168.1.1 is without VPN

[Ray Tackett]

Here are my Tracert without and with my VPN.

Similar to mine. Took a lot of time, and you never arrived at the destination IP. You'll see the same for something local to you, like a local TV station. Doesn't matter whether a site is actually reachable via a browser, that's the stuff you get from tracert.

[Terry Carraway]

It does only 30 lines. So that can limit things.

[Stephanie Belser]

is there a way to stop the Tracert window from closing? There're other places that I reach in a dozen hops or so. Avsig, not so much.

[Russell Holton]

is there a way to stop the Tracert window from closing? There're other places that I reach in a dozen hops or so. Avsig, not so much.

Open a "CMD" (aka DOS Box) and then do Tracert from there. When Tracert is done, it drops you back to the command line and the box stays open.

[Stephanie Belser]

Open a "CMD" (aka DOS Box) and then do Tracert from there. When Tracert is done, it drops you back to the command line and the box stays open.

Thanks. It worked. Here's Avsig and the Pistol Forum for comparison:






I use Opera's VPN, I'm presuming that tracert is running outside of it.