dlink router issue

[kurtismonger]

I have a DLink DI-524 wireless router that wont connect to a modem and accept an IP address. This is a new router that hasn't been used, but is several months old so I can't return it.
I have tried connecting it to both a DSL modem and a cable modem that work fine with other routers, with the same result. The wireless works fine, but it never shows an IP in the status window.
I have upgraded the firmware, which did not fix anything.

 

[smah]

First - you're sure the cable connecting the router to the modem is ok, right? And, if you can connect to it wirelessly from inside your network and administer it, try changing it's IP address from the default 192.168.0.1 to something like 192.168.2.1. Reboot the router, reboot your computer & test.

Steve

 

[kurtismonger]

Yes, I have tried different cables, including one that is working fine on another modem/router setup. Changing IP of router doesn't have any effect.

 

[cdogg]

OK, just so we're clear, you configured the router with your logon information for your ISP, and used the proper protocol like PPPoE for DSL?

What does the status screen say on the router (is it trying to connect)?

Are you powering the DSL or cable modem off/on when connecting the router? This is necessary to reset the MAC address that the modem thinks it's talking to. Just swapping the cable to another device isn't enough.

~cdogg
"Insanity: doing the same thing over and over again and expecting different results." - Albert Einstein
[tab][navy]For general rules and guidelines to get better answers, click here:[/navy] faq219-2884

 

[kurtismonger]

Yes, thanks for the clarification, I should have mentioned that. I configured the router for the DSL modem with user and password for PPPoE. I also tried it with a cable modem and changed it to dynamic IP.

The status screen reads either connecting or disconnected. If I press the connect button, the screen refreshed but IP, mask etc. all stay at 0.0.0.0. Status light also continues to just blink.

I have tried cycling the power on the modem (both the DSL and the cable) and then bringing up the router. Same result.

 

[cdogg]

Have you performed a full reset on the router setting everything back to the defaults?

Personally, this is what I'd do next:

1) Disconnect everything from the router except the power source. Reset it.

2) Connect a PC over ethernet to the router (worry about wireless last)

3) Configure the router as necessary for the ISP in question. Don't enable the "autoconnect" or "keep alive" setting yet. Make sure that every setting on the router stays at the defaults, except the ones that you ABSOLUTELY have to change to connect. So the IP of the router should still be at 192.168.0.1 and using DHCP for the LAN.

4) Leave the router powered on and connect the ISP's modem. Make sure the modem is in a powered off state when connecting it to the WAN port, then power it on.

5) Hit the "connect" option from the router config screen


I don't know if this will help, but making things really simple when you do them sometimes reveals what's going wrong. I know I do that all the time and kick myself later for not realizing what I did in the first place. The "extra" little things that you do out of order such as configuring the WAN or changing DHCP to static, sometimes bite you in the end...

~cdogg
"Insanity: doing the same thing over and over again and expecting different results." - Albert Einstein
[tab][navy]For general rules and guidelines to get better answers, click here:[/navy] faq219-2884

 

[kurtismonger]

Turned out it was the 2Wire DSL modem provided by SBC. It was configured as a router and wouldn't play nice with the DLink. SBC had me change settings in the modem so it would be a bridge and pass the dynamic IP to the router. This failed and they gave up, blaming DLink as is typical with these companies. Suspecting that it was the modem I continued to mess around in the modems settings and found that I needed to disable PVC search (I have no idea what it does) in addition to setting it to direct IP and disabling routing.

Thanks for your help in troubleshooting.