Weird Network Issue - Browser fail, Tracert works.
Posted on 2015-01-26
I have a win 2012 server with a sonic wall tz170 router that is then plugged into a comcast modem/router.
There are about 10 machines on the network, and all work fine. One server, however, has a problem I simply can't solve.
I'll remote-desktop to it and do some work for a while (I use it as a development machine) and suddenly, I won't be able to reach websites. I can't ping anything or open anything outside my network. (I can open websites on other local servers.) I can ping the gateway, but not the next gateway.
Here's the weird part:
While trying to figure it out, I did a tracert to google. No luck. HOWEVER, I did a tracert to the google IP and, after about 20 seconds of hesitation, boom. It worked fine. Pings worked, I could open the site, etc... all perfectly fine.
I have absolutely no idea what would cause that.
What would make tracert bring-back the internet, for an hour or so, and then have it go back to blocked????
It's driving me crazy, because I'll be testing systems on remote file/data systems with a local front end, think it's broken, spend 20 minutes trying to figure out the "bug", and have it turn out to be this #$*&@)(#$ network issue and I've spend all that time messing with perfectly good code!!
So, any ideas?