DNG2000 router not assigning IP addresses to wired connections

Associate
Joined
27 Nov 2005
Posts
336
Location
Edinburgh
My internet provider is Be Broadband and until now I have been using the standard Thomson router that they provide for internet access.

I have just picked up a Netgear DNG2000 on eBay with the plan to use the DGTeam custom firmware to allow me to have more control over my connection speed but I am having issues..

First thing I did was reset the router to its factory default settings and then setup the ADSL connection on it via wireless. I can connect to the router via wireless connections and the DHCP will assign a local IP to the wireless device and also connect to the internet without a problem. However if I use a wired ethernet connection the router fails to assign the computer an IP address (stuck with a 169 address). The ethernet light on the router is lit to show it recognises a cable is plugged in at least.. I have tried playing about with RIP router settings, tried releasing/renewing IP address on wired machine but these things don't seem to have helped.

If I plug my ethernet cable back into my Thomson router, I am assigned an IP address nearlly straight away so it must be something to do with the DNG2000? As a side, I have tried on 3 different computers: Macbook, Win 7 desktop and a WHS and all 3 have failed to be assigned an IP.

Does anyone have any bright ideas?

Cheers
 
Okay, so DHCP on the router must be working if it's assigning wireless clients an IP, and PC-side is working if you're getting an IP from your Thomson.

Hmm, did you buy the DGN2000 second-hand? These routers suffer from capacitor issues where once they start to fail, you get problems on the LAN switch. You can usually tell by opening the router and checking the capacitors for bulging tops. These can be replaced cheaply if you have a soldering iron.

If it's brand new, then I'm not sure, other than defaulting the router and trying with netgear firmware?
 
Thanks for the advice, it is a second hand router and could be the capcitor problem perhaps... I will contact the seller
 
Back
Top Bottom