DHCP private IP address

[edmundoab]

Dear AT experts,
I would require some advice on this issue.

Recently, my D-Link Router DI-624+ had an adapter that was faulty.
I replaced it with a new adapter rated at 5 V, 2.5A

Unfortunately, when I booted both my PCs
It showed that gateway had been changed to 169.254.178.114

I tried to manually insert the correct IP address (192.168.0.1), subnet mask, gateway and DNS servers into the TCP/IP properties but it still could not communicate with the router

- Pinging 169.254.178.114 worked fine
- Lights lit up when the cables are plugged into the router
- The WAN , Status and Power is on
- Tried to connect directly to one PC for a dial up connection and it works. (so the modem is working fine)

Would could really be the issue? faulty router?

 

[bsobel]

The 169* address are auto configuration addresses, it means the computers picked them themselves since they couldnt see the DHCP server. None of those addresses have anything to do with the router (so the gateway address you are seeing is NOT the router)

Sounds like the router is not working, you sure those voltages are correct? It might simply have been fried by the failing adapter....

 

[edmundoab]

Well I bought a universal one and adjusted it the voltage required
If that doesn't work, I might have to buy a new one.
Just didnt want to waste this router if its still working

how do you suggest I troubleshoot this Dlink before chucking it to the bin?

 

[RebateMonger]

Originally posted by: edmundoab
how do you suggest I troubleshoot this Dlink before chucking it to the bin?

Reset the router to Default settings by following the manufacturers recommendation. Set our PCs' TCP/IP properties so that they get their IP addresses via DHCP. Attach the PCs to LAN ports on the router using known-good network cables (not a home-made one).

If you boot your PCs and none of them get a "standard" IP address (typically something like 192.168.xxx.xxx), then it's likely your router is bad.