Auto Diagnosing on Internet Connection Problem

Thundordan

n00b
Joined
Feb 12, 2010
Messages
29
Hello,

Not sure if I should post this here or in the Networking section, but it's pretty much a software/OS thing.

My ISP is apparently in the habit of frequently changing my IP or Gateway (I'm using a router and a modem, router works fine, receives the new gateway but windows doesn't). I often leave the pc on with something to download and come back in a couple of hours expecting it to be finished only to find that my internet connection had been interrupted due to "Gateway not available" just after I had left..

When this happens, I have to "diagnose" the connection problems and Windows 7 automatically notices what's wrong and Fixes it.

NOW,

Since Windows 7 also automatically notices when/if your connection to the internet has interrupted, is there any way I can "tell" windows to automatically diagnose the network adapter(s) after it detects a problem? Doesn't make sense for me to have to do that manually if everything else is automated.:confused:

If there isn't such a setting, is it possible to write a script that will refresh the adapters if(connection == "lost") and with a timer or an event? (so I can run it while I'm not at the PC). I'm handy with code, but I'm not familiar with anything microsoft-windows-related (how to get a hold of the network adapters and read/write settings)..

Thank you.
 
Last edited:
Why is your IP/gateway going to change? Your router should get a new IP/Gateway to ISP every time your ISP changes it, but your internal IP/gateway shouldn't change.
 
Windows can't do much if the router is dropping the WAN connection for whatever reason.

also, the network adapters on the computer shouldn't be losing the connection; if it is going to "network cable disconnected" or "limited or no connectivity" then the issue is between the computer and router, and not necessarily the modem.
If the network adapter status isn't changing, you just lose access to the internet, all Windows diagnostic will tell you is that the gateway is bad; but won't be able to do anything about it.
 
I have Verizon DSL and something similar happens to me every few months. The only way to fix it is to completely pull the plug out of the modem, wait 30 seconds, then plug it back in. Rebooting the modem does not fix it.
 
No, my router is fine, it gets the new info, I do not lose connectivity, it's just that Windows keeps using the old gateway until I refresh and it realizes that it changed. The troubleshooting usually shows the "Gateway not available - Fixed" message. And it's definitely from my ISP.

A simple refresh of the network adapter fixes the problem as it requests the information again rather than trying to use the old gateway.
And it sucks that Windows 7 has replaced the "reconnect/refresh (whatever it was called) adapter" from XP with "troubleshoot problems" which takes 5 minutes and doesn't tell you what it's doing until it's done.

Anyway, Windows notices the connection has been interrupted when the gateway changes, but CAN I tell it to automatically refresh the adapter when that happens?

PS: I don't have to unplug anything!
 
Last edited:
Windows should be pointing to the router's IP as the gateway, not the ISP's gateway.
 
What Gateway IP is your router using?

What Gateway IP is your computer using?

If these IP addresses are the same, your router is not setup properly.
 
Windows should be pointing to the router's IP as the gateway, not the ISP's gateway.

What he said. You should be using your router IP as your gateways for all your computers on your network, then your router's gateway will be the ISP assigned gateway.
 
I just ipconfig /all'd and double checked:

IP: 192.168.0.199
Default Gateway: 192.168.0.1
DHCP Server: 192.168.0.1
DNS Servers: 95.77.94.88
192.168.0.1
Everything is configured properly and I'm pretty sure that it isn't a setup issue. Again, when my ISP gateway changes, the router receives it correctly, but Windows doesn't update the connection. Windows stays on my old gateway and thinks that the internet connection is lost somehow. After troubleshooting, it realizes the gateway has changed.

I would like to make it refresh the gateway every time the internet(not lan) connection is lost, cause it's most likely the "Gateway not available - Fixed" thing.
 
After troubleshooting, it realizes the gateway has changed.
Can you explain this part? The gateway should not change. At most, Windows should say that you've lost connection, then it will reconnect itself after a few DHCP Discovery attempts.
 
It appears the router is having issues & not Windows. How up to date is the router's firmware?

The DNS entries look off... It should either be all internal or all external. If the external DNS entry can't be accessed, then the internal won't work as well. This might create a hiccup with Windows...
 
Sounds like the router might be flaking out. What kind of router is it, brand, model number, and firmware revision and also it's age?

Another queston, what kind of connection are we talking about? Is it a Cable ISP or DSL PPoE, PPoATM?
 
Why is your IP/gateway going to change? Your router should get a new IP/Gateway to ISP every time your ISP changes it, but your internal IP/gateway shouldn't change.

he might have the router set to pass that information along instead of using it's own. the solution is to not clone the isp's information
 
Can you explain this part? The gateway should not change. At most, Windows should say that you've lost connection, then it will reconnect itself after a few DHCP Discovery attempts.
When this problem occurs, Windos 7's new Network and Sharing Center shows the LAN connection being fine (I've also verified that by pinging my laptop) but the connection to the Internet being broken. Then, since there is no refresh connection option, I hit Troubleshoot Problems which fixes the problem. It lists "Gateway not available - Fixed" in the discovered issues box when it's done.

It appears the router is having issues & not Windows. How up to date is the router's firmware?

The DNS entries look off... It should either be all internal or all external. If the external DNS entry can't be accessed, then the internal won't work as well. This might create a hiccup with Windows...
That might be it. I've never actually verified if the actual gateway changes, rather I've reached that conclusion because the error message is "Gateway not available".

Sounds like the router might be flaking out. What kind of router is it, brand, model number, and firmware revision and also it's age?

Another queston, what kind of connection are we talking about? Is it a Cable ISP or DSL PPoE, PPoATM?
D-Link DI-524, Firmware Version: V2.06 , Mon, May 07 2007. I can't remember if I updated the firmware (perhaps I have) but regardless of that, I definitely didn't have it before 2006.
It's cable, the same cable as the TV cable.


When I first bought the router, I tried setting everything up manually by the book but never could get the router to "get along" with the modem. So I ran the detection and set up wizard on the router's CD which asks me what kind of network to create and then sets everything up itself without asking any more questions; modem gets recognized and internet works. I don't remember fiddling with anything in the Router's page (http://192.168.0.1/).
[edit] actually, I did not fiddle with anything, as I reset the router a couple of weeks ago due to me forgetting my password :D

Router Screenshot: http://a.imageshack.us/img269/4955/routeryl.jpg
 
Last edited:
img01.jpg


see where it states HW Ver in the lower left of the white sticker? your router will have something similar on it's sticker. in your case your HW is B4 which does not make sense cause there is no reb B listed and the orignal rev only has 1.X software. Are you outside of the USA? if so what country are you in?

edit NVM I look up your info on a webpage you have posted in your profile

look here

http://www.d-link.ro/cs/Satellite?c...95806673826&pagename=DLinkEurope-EE/DLWrapper
 
Last edited:
does your internet connection use PPPoE for authentication?

ie, did you have to configure a username and password, provided by your ISP, into your router?
 
does your internet connection use PPPoE for authentication?

ie, did you have to configure a username and password, provided by your ISP, into your router?
No, I'm not using PPPoE.

img01.jpg


see where it states HW Ver in the lower left of the white sticker? your router will have something similar on it's sticker. in your case your HW is B4 which does not make sense cause there is no reb B listed and the orignal rev only has 1.X software. Are you outside of the USA? if so what country are you in?

edit NVM I look up your info on a webpage you have posted in your profile

look here

http://www.d-link.ro/cs/Satellite?c...95806673826&pagename=DLinkEurope-EE/DLWrapper
I had looked on the stupid Romanian site but they didn't list any firmware upgrades. But after I read your post I went to Easten Europe which pointed me out to ftp://ftp.dlink.co.uk/di_broadband_gateways/di-524/ which did have the 2.04 :D
It seems that a few years back I had upgraded the firmware to the wrong version, one from 2007..

So now I have installed "the proper" firmware, but nothing really changed, the DNS entries are the same and I'm not really sure if I can verify if the problem is fixed.

Router&cmd Screenshot after firmware upgrade: http://a.imageshack.us/img375/7441/router2.jpg
 
When this problem occurs, Windos 7's new Network and Sharing Center shows the LAN connection being fine (I've also verified that by pinging my laptop) but the connection to the Internet being broken. Then, since there is no refresh connection option, I hit Troubleshoot Problems which fixes the problem. It lists "Gateway not available - Fixed" in the discovered issues box when it's done.
There is no refresh connection button because there isn't a need for one. Windows will detect there no longer is an internet connection then it will ping back every so often until there is, then you're back up and running again. Another solution would be to set your DHCP lease time to a lower value, perhaps 1 hour if you don't have too many machines on your network, that way every hour, your computer will ask the router if it can still use its IP and will update its gateway etc at the same time.
 
There is no refresh connection button because there isn't a need for one. Windows will detect there no longer is an internet connection then it will ping back every so often until there is, then you're back up and running again. Another solution would be to set your DHCP lease time to a lower value, perhaps 1 hour if you don't have too many machines on your network, that way every hour, your computer will ask the router if it can still use its IP and will update its gateway etc at the same time.

Hey thanks mate, that kinda solves my problem; and explains a lot. I've only got my desktop and 2 laptops who log on occasionally.
So I set my DHCP lease to 1hr.
 
Yup, it'll give you that yellow triangle with an exclamation mark inside it until it detects Internet connection again and you'll be all good. Be patient!
 
iirc, that router actually has some decent built-in logging.
try checking the log, and see if it shows when the WAN IP was renewed and compare it to when the 'net starts working.

Since you are still able to access the router when the internet doesn't work, there aren't any IP-related changes on the LAN. Therefore, a release/renew, repair, etc would have no effect since the LAN access is not affected. And none of that would effect the router or WAN access.

imho, it just sounds more like a coincidence that the internet starts working after the Windows Network Troubleshooter does its' thing.
 
You might want to check the cable modem's status page and log for some anomalies.

The address should be something like http://192.168.100.1 if I recall correctly.
 
iirc, that router actually has some decent built-in logging.
try checking the log, and see if it shows when the WAN IP was renewed and compare it to when the 'net starts working.

Since you are still able to access the router when the internet doesn't work, there aren't any IP-related changes on the LAN. Therefore, a release/renew, repair, etc would have no effect since the LAN access is not affected. And none of that would effect the router or WAN access.

imho, it just sounds more like a coincidence that the internet starts working after the Windows Network Troubleshooter does its' thing.

The Troubleshooter says that it has detected that the Gateway is not available And that it Fixed it. So if it is a coincidence, then Windows is lying to me and taking credit for nothing :D

You might want to check the cable modem's status page and log for some anomalies.

The address should be something like http://192.168.100.1 if I recall correctly.
it is 192.168.0.1

I will check the logs the next time this happens.
Right now, since I've bothered to fiddle with the router, I'm trying to set up port forwarding so I can host Borderlands servers :rolleyes:
 
The Troubleshooter says that it has detected that the Gateway is not available And that it Fixed it. So if it is a coincidence, then Windows is lying to me and taking credit for nothing :D

Logically it can't find a gateway because it can't get off your LAN, technically, its being stupid. btw Did you wait it out and see if it auto-refreshes itself?
 
just out of curiosity are you cable dsl or some other form of internet (like wireless provider)?
 
it is 192.168.0.1

I will check the logs the next time this happens.
Right now, since I've bothered to fiddle with the router, I'm trying to set up port forwarding so I can host Borderlands servers :rolleyes:
No, thats the address of your router, look at the address of your cable modem's administration page, it's most commonly http://192.168.100.1/.

just out of curiosity are you cable dsl or some other form of internet (like wireless provider)?
He posted up above that it's cable, it's was easy to miss:
D-Link DI-524, Firmware Version: V2.06 , Mon, May 07 2007. I can't remember if I updated the firmware (perhaps I have) but regardless of that, I definitely didn't have it before 2006.
It's cable, the same cable as the TV cable.
 
The Troubleshooter says that it has detected that the Gateway is not available And that it Fixed it. So if it is a coincidence, then Windows is lying to me and taking credit for nothing :D

your router is the gateway.
if it says the gateway is not available, it's trying to say your router is not available.
but since you can access your router, it's lying to you ;)
 
Logically it can't find a gateway because it can't get off your LAN, technically, its being stupid. btw Did you wait it out and see if it auto-refreshes itself?

The only times that I've "waited" was when I came back to my pc and checked utorrent. One time, I started some downloads, went to bed and when I woke up in the morning, the internet connection was "gateway not available" and the downloads were at 0-10%. (they should have finished in less than 3hrs, I had slept for at least 8).

A couple of other times when this happened I was playing TF2, got kicked out, troubleshot and it got "fixed".

So what I can figure is, it at some point encounters a problem, which gets fixed almost immediately, BUT Windows doesn't "realize" that it's fixed until I Troubleshoot..

No, thats the address of your router, look at the address of your cable modem's administration page, it's most commonly http://192.168.100.1/.
You're right, I forgot what the modem address is, and I thought that you were actually referring to the router. :eek:

your router is the gateway.
if it says the gateway is not available, it's trying to say your router is not available.
but since you can access your router, it's lying to you ;)
Maybe. But also, maybe it refers to the modem as the gateway, since my lan connection is shown as OK (and works).

I have looked through my Modem's log and I can't understand a word except for "DHCP" (and I'm actually studying computer science). :(
There seem to be different Critical problems logged, but I don't really recall any other issues except the "gateway" thing. (either they're all pointing to this error or, the other errors got fixed by windows on it's own)

Modem Event Log:
Code:
Wed Aug 18 10:54:22 2010  	 Notice (6) 	 TLV-11 - unrecognized OID 
 Wed Aug 18 10:54:09 2010  	 Critical (3) 	 No Ranging Response received - T3 time-out 
 Wed Aug 18 09:51:22 2010  	 Notice (6) 	 TLV-11 - unrecognized OID 
 Time Not Established 	 Critical (3) 	 No Ranging Response received - T3 time-out 
 Thu Aug 12 11:40:14 2010  	 Critical (3) 	 DHCP FAILED - Discover sent, no offer received 
 Thu Aug 12 11:37:56 2010  	 Critical (3) 	 SYNC Timing Synchronization failure - Failed to acquire QAM/Q... 
 Thu Aug 12 11:29:59 2010  	 Critical (3) 	 Received Response to Broadcast Maintenance Request, But no Un... 
 Mon Aug 09 12:44:28 2010  	 Critical (3) 	 No Ranging Response received - T3 time-out 
 Sat Aug 07 20:49:09 2010  	 Critical (3) 	 No Ranging Response received - T3 time-out 
 Fri Aug 06 17:47:37 2010  	 Critical (3) 	 No Ranging Response received - T3 time-out 
 Fri Aug 06 06:04:53 2010  	 Critical (3) 	 Started Unicast Maintenance Ranging - No Response received - ... 
 Mon Aug 02 10:04:03 2010  	 Critical (3) 	 No Ranging Response received - T3 time-out

[EDIT] Note that on Aug 18'th, I did not have any noticeable Internet issues whatsoever. So it's definitely not the "No Ranging Response received - T3 time-out" that's bothering me.
 
Last edited:
to Windows, the gateway is whatever device is at the Default Gateway IP address; which is the router.

have you checked the logs on the router itself? When I worked for an ISP, I remember those DLinks actually having some pretty damn good logging features built-in.
 
No Ranging Response received - T3 time-out
Its an ISP problem. If you Google that, people are getting that error and some say that the ISP was doing work on the internet line.
 
Wow, that sure happens a lot. Do any of those ranging entries coincide with your router flaking out?

By the way are your line levels?
 
to Windows, the gateway is whatever device is at the Default Gateway IP address; which is the router.

have you checked the logs on the router itself? When I worked for an ISP, I remember those DLinks actually having some pretty damn good logging features built-in.
You're right.
And I checked the router log (Status->Log) (today, aug 20th), and I had 28 entries, all of them from Aug 20th:confused:
Help said that the router remembers up to 200 log entries...
One thing though, yesterday, I set a static IP and did some port forwarding on my Router. But adding new ports should definitely not have reset the device and cleared the log..

Wow, that sure happens a lot. Do any of those ranging entries coincide with your router flaking out?

By the way are your line levels?
No, as I said in my previous post, the "No Ranging Response received - T3 time-out" error doesn't show any visible interruptions to my connection to the internet.

"By the way are your line levels?" Is there a typo in that question or if not, I don't understand what are you asking?

[EDIT] By the way, I'm pretty certain that last time I had a connection problem was on the Aug 12 entry in the modem log I posted above.
 
Line levels are the coax line heading out to the cable network. Never mind though since you said that those ranging errors do no coincide with your router issue.


It looks to be your router as the culprit. You might want to try resetting it to factory defaults and seeing if that clears your issue up. You can back up your config to restore later if you would like to via the web admin interface.

If I recall correctly, you hold unplug the router and then power it back up while holding in the reset button with a paper clip.
 
If he's going to reset to the defaults, a firmware upgrade might as well happen, too. Has it been upgraded it yet, OP?
 
Back
Top