D-Link Forums
The Graveyard - Products No Longer Supported => Routers / COVR => DIR-655 => Topic started by: jgkurz on November 06, 2009, 10:38:29 AM
-
I am one of the many that are having DIR-655 lockup problems with firmware 1.32 firmware. It seems the fix is to disable DNS Relay. If I disable DNS Relay I lose connection to the internet. My internal LAN works fine but I cannot surf the web. I have released and renewed my IP, hard reset my router, reset my Comcast cable modem, reset my NIC and rebooted my systems. None of this troubleshooting has allowed connection to the web until I re-enable DNS Relay.
Any suggestions?
-
If your modem has a battery you need to remove it and then unplug the modem.
-
Unplug the modem? Thats not going to fix his DHCP-assigned (and cached) dns addresses.
Probably what you will see if you do status on your network connection on your PC's, or an ipconfig /all, is DNS server addresses that are 192.168.0.1 (the address of your router). Which is how its supposed to look when dns relay is enabled.
When it is disabled though, this entry should be something on the internet. An
ipconfig /release
ipconfig /renew
Should do it.
If it doesn't reboot them.
Cory
-
My Motorola SurfBoard modem does not have a battery. To reset it I just remove the power plug. Unfortunately a reset does not allow connection to the internet when DNS Relay is disabled.
Thanks for the suggestion.
-
Unplug the modem? Thats not going to fix his DHCP-assigned (and cached) dns addresses.
Probably what you will see if you do status on your network connection on your PC's, or an ipconfig /all, is DNS server addresses that are 192.168.0.1 (the address of your router). Which is how its supposed to look when dns relay is enabled.
When it is disabled though, this entry should be something on the internet. An
ipconfig /release
ipconfig /renew
Should do it.
If it doesn't reboot them.
Cory
I'll try an ipconfig /release & /renew then reboot each XP machine. Previously I disabled the NIC and enabled it which I thought did the same thing. Stay tuned....
-
^^ Well more importantly, just confirm that you are indeed actually getting new DNS values. For myself, I've certainly seen the old "192.168.0.1" setting hang around sometimes.
-
Unplug the modem? Thats not going to fix his DHCP-assigned (and cached) dns addresses.
I did not say it would.
It would however clear the MAC address from the modem which you must do with Comcast when changing to a different router or connection as Comcast only allow the modem to obtain one MAC unless you pay for multiple IP's.
The Linksys router would have a different MAC than the D-Link and until you powercycle the modem it would retain the Linksys MAC hence my suggestion.
-
also you can use the ipconfig /all to make sure that you are getting the proper DNS server numbers.
-
ipconfig /release & /renew in XP did the trick. Thank you all for your replies. I'm hoping for much more stability from my DIR-655.
-
I did not say it would.
It would however clear the MAC address from the modem which you must do with Comcast when changing to a different router or connection as Comcast only allow the modem to obtain one MAC unless you pay for multiple IP's.
The Linksys router would have a different MAC than the D-Link and until you powercycle the modem it would retain the Linksys MAC hence my suggestion.
You didn't read his post carefully. That's not what he described.