D-Link Forums
The Graveyard - Products No Longer Supported => Routers / COVR => DIR-655 => Topic started by: ShawnTRD on January 08, 2009, 10:26:27 AM
-
I've always had Linksys router in the past. Yesterday I got a 655 from bestbuy and it came with FW 1.20. I turned off my compute, unplugged the Motorola modem, and removed my Linksys WRT54GS. I plugged in the Motorola modem, waited for that to boot. Plugged the Motorola modem into my 655, and my computer (wired) into the 655. Plus the power into the 655. Waited about 1 minute and started my computer. I could login to the 655, but I had no internet. Any ideas?
-
power the router on first. Then wait for it to boot then power up the modem.
-
Didn't work.. I'm just going to return it and stick with Linksys.
-
ShawnTRD,
Did you try upgrading the firmware? I noticed in the beginning of the thread you said you were running 1.20 from the box.
-
Didn't work.. I'm just going to return it and stick with Linksys.
You might want to change some settings in http://192.168.0.1/Basic/WAN.shtml (My internet connection is...). Some ISP's require you to set it to PPoE. 8 out of 10 ISP don't require that, but you might be one of the others (no extra info made available so just guessing here. Some extra info would be nice to help you)
PLug an Play does not work in the direction (modem to router) you envision it: routers will not always (see 2 out of 10 situations) automatically recognize your modem when they require a 'special' connection setting. Have a look here what Plug and Play really is all about: http://en.wikipedia.org/wiki/Plug_and_play
Plug and play is a PC (Windows) feature.
-
ok so I upgrade to FW ver. 1.21 and it was working. But My wifes wireless couldn't surf with it. It said it was connected. She had full G signal. But go to websites and they would load very slow if at all. My Wired desktop was working great. I tried loading FW Ver. 1.11 because I heard people saying there very good, but the 655 Ver.4 wouldn't let me.
-
No, A4 hardware will not downgrade. Because of the parts used I would say.
Anyway, try disabliong "DNS Relay" (http://192.168.0.1/Basic/network.shtml) and manually enter DNS servers (http://192.168.0.1/Basic/WAN.shtml) of your ISP or OpenDNS.
-
Same thing happened to me..Unplug your modem,I think I have the same one you do..There is a reset you need to use a paper clip on to reset..Plug the power back in and let it cycle..The cable modem is still seeing your last routers ip address. After you do this it will work..
-
...My wifes wireless couldn't surf with it. It said it was connected. She had full G signal. But go to websites and they would load very slow if at all.
change the SSID and make sure your SSID is broadcasting (Setup - Wireless - Manual Wireless Setup - Visibility Status: visible).
If this helps, it's because her saved settings for the old G network weren't compatible with your new Access Point.
-
change the SSID and make sure your SSID is broadcasting (Setup - Wireless - Manual Wireless Setup - Visibility Status: visible).
If this helps, it's because her saved settings for the old G network weren't compatible with your new Access Point.
I know it was set to visible. The SSID is dlink or whatever the default is. She had wireless, but every now and then she would not load sites. Even though it was still saying connected. That was unsecured. So then I tried secured and it was worse. I'm thinking there is a problem with Hardware Version 4, but I need to look into this more.
-
Try disabling DNS relay and manually enter DNS servers. Seems to fix a lot of issues on the DIR655.
-
manually enter DNS servers? Who do I do that?
Try disabling DNS relay and manually enter DNS servers. Seems to fix a lot of issues on the DIR655.
-
Just look on this page, one of my earlier posts...January 13...
-
looks like Hardware Version A4 has problem. This shouldn't be this hard. >:(
-
looks like Hardware Version A4 has problem. This shouldn't be this hard. >:(
Did you accomplish it?
If not, then do the following:
1. Go to Setup - Network Settings and UNCHECK Enable DNS Relay, Save Settings but do not reboot.
2. Go to Status - Device Info and write down the IP Addresses under "WAN" for Primary DNS Server and Secondary DNS Server.
3. Go to Setup - Internet - Manual Internet Connection Setup and input the Primary DNS Server and Secondary DNS Server noted in the earlier step, Save Settings and reboot.
4. Restart your network devices so that they will obtain new DHCP leases.
Note: If any of your devices do not get their IP address assignment from the DIR-655, they will need to be manually configured to use the IP addresses you recorded in step 2 for DNS.
If this helps, it's because your network devices are directly using the DNS server addresses now instead of relaying queries through the buggy "DNS Relay" feature (http://forums.dlink.com/index.php?topic=2737.0) in the DIR-655. Steps 2 and 3 are necessary because of another bug (http://forums.dlink.com/index.php?topic=2737.msg16650#msg16650) where the reboot sequence timing might or might not result in DHCP clients not receiving any addresses at all for DNS (http://forums.dlink.com/index.php?topic=2737.msg16650#msg16650). Step 4 is often not necessary, but some network devices may not renew leases and get these changes if they fail to detect that the router has momentarily gone offline.
-
looks like Hardware Version A4 has problem. This shouldn't be this hard. >:(
A router (any brand) working 100% out-of-the-box is not standard practice. They did not put the options in for nothing. Every network config might need minor adjustment. This is just one of them.
-
Thanks Guy's
But I went to BestBuy today and found they had a A3 version on the shelf. So I exchanged it and it's been up got about 2 hours on here wiresless with no problems. No manual settings adjustment. Now I'm happy. (I think) ;D P.S. need better quality smiles on this board. hahaha
A router (any brand) working 100% out-of-the-box is not standard practice. They did not put the options in for nothing. Every network config might need minor adjustment. This is just one of them.
Did you accomplish it?
If not, then do the following:
1. Go to Setup - Network Settings and UNCHECK Enable DNS Relay, Save Settings but do not reboot.
2. Go to Status - Device Info and write down the IP Addresses under "WAN" for Primary DNS Server and Secondary DNS Server.
3. Go to Setup - Internet - Manual Internet Connection Setup and input the Primary DNS Server and Secondary DNS Server noted in the earlier step, Save Settings and reboot.
4. Restart your network devices so that they will obtain new DHCP leases.
Note: If any of your devices do not get their IP address assignment from the DIR-655, they will need to be manually configured to use the IP addresses you recorded in step 2 for DNS.
If this helps, it's because your network devices are directly using the DNS server addresses now instead of relaying queries through the buggy "DNS Relay" feature (http://forums.dlink.com/index.php?topic=2737.0) in the DIR-655. Steps 2 and 3 are necessary because of another bug (http://forums.dlink.com/index.php?topic=2737.msg16650#msg16650) where the reboot sequence timing might or might not result in DHCP clients not receiving any addresses at all for DNS (http://forums.dlink.com/index.php?topic=2737.msg16650#msg16650). Step 4 is often not necessary, but some network devices may not renew leases and get these changes if they fail to detect that the router has momentarily gone offline.
-
Ok so I have had this for about a week and everything is ok. But we are/were still noticing sites that had trouble loading (myspace, facebook, and others). So I can back here and tried funchords advice. So far everything seems good.
Did you accomplish it?
If not, then do the following:
1. Go to Setup - Network Settings and UNCHECK Enable DNS Relay, Save Settings but do not reboot.
2. Go to Status - Device Info and write down the IP Addresses under "WAN" for Primary DNS Server and Secondary DNS Server.
3. Go to Setup - Internet - Manual Internet Connection Setup and input the Primary DNS Server and Secondary DNS Server noted in the earlier step, Save Settings and reboot.
4. Restart your network devices so that they will obtain new DHCP leases.
Note: If any of your devices do not get their IP address assignment from the DIR-655, they will need to be manually configured to use the IP addresses you recorded in step 2 for DNS.
If this helps, it's because your network devices are directly using the DNS server addresses now instead of relaying queries through the buggy "DNS Relay" feature (http://forums.dlink.com/index.php?topic=2737.0) in the DIR-655. Steps 2 and 3 are necessary because of another bug (http://forums.dlink.com/index.php?topic=2737.msg16650#msg16650) where the reboot sequence timing might or might not result in DHCP clients not receiving any addresses at all for DNS (http://forums.dlink.com/index.php?topic=2737.msg16650#msg16650). Step 4 is often not necessary, but some network devices may not renew leases and get these changes if they fail to detect that the router has momentarily gone offline.