D-Link Forums
The Graveyard - Products No Longer Supported => Routers / COVR => DIR-655 => Topic started by: ekalbach on December 19, 2007, 06:32:23 PM
-
Have a new 655 running the latest code. In the house we have 2 desktops, 3 laptops, and a gaming bridge. Currently the AP is configured for WEP on the wirless side and 2 of the laptops connect to and get an ip address via dhcp. The 2 desktops are hardwired and do not have a problem getting an ip address via dhcp. We have 1 laptop (Gateway) that refuses to pull an ip address from the new 655. At first I thought it might be a laptop issue until I plugged in my old linkksys box and the problome laptop got an ip address without a prblem. The problem exists on the wireless and the cabled side. Laptop is running XP SP2.
Anyone have any suggestions?
Thanks...
-
Whats the channel width set to, you could try changing that to 20/40, or just 20 depending on what default is. I'm not going to default mine out right now just to check.
Also, if you're only connecting B/G clients lock down the radio to B/G only, or even G only depending on what you are connecting.
you mentioned wired as well....
Do you have MAC filtering running on your router? Static IPs set on your laptop?
Maybe call Gateway.....Sounds like your routers working. You may be statically set to the linksys router you mentioned worked. Check the IP config, make sure you're set to Obtain Automatically.
-
Problem is on both wired and wireless. I'm going to play width channel width tomorrow but since the problem is on both that is more than likely not the problem. No MAC filtering running or static ip set. Tried locking to B only, BG, and all. Same problem as before. I am not ready to cast blame on the 655 as logically the problem seems to be PC related. We also disable all security on the PC but have not gotten around to resetting the ip stack. It shall be a fun day of troubleshooting tomorrow. Thanks for the response.
-
Problem was resolved by locking the radios to B/G only and turning n off. Thanks to those who assisted.
-
Amazing solution. Did modifying the wireless setting of your router also fix the your inability to obtain an IP address from the wired connection as well?
-
That was an entirely different problem that had nothing to do with the 655. I was not provided with all of related information which led me to believe that both the wired and wireless adapters were invloved. Ya get the wrong information and you come out with the incorrect answers. Perhaps my questions to the wife were not adequate.
-
Then you lose my "amazing" endorsement. I thought you were on to something wild.
Glad to hear you are up and running. I applaud you for working through the troubleshooting to solve the real problems you we having.
-
I was browsing these old forums and found this. This perhaps, is a bigger problem than what it seems, it's compatibility issue of DIR-655 with 802.11b wireless client device. I have similar situation with my older Toshiba Tecra 8200 with built-in 802.11b. Switching the wireless mode from 802.11N/G/b to 802.11G/b fixed the problem. But doing this beat the purpose of buying an N router in the first place.
I am creating a new topic on this issue.
-
please do not 'cross post' in different threads with the same question. See the thread you opened for a possible answer (no solution...).