DHCP Server issues. Help needed!!

hj2k_x

hj2k_x

Honorary Master
Joined
Jan 22, 2006
Messages
32,137
Reaction score
1,893
Location
/\/¯¯¯¯¯\/\
Howzit. Have just reinstalled Windows on my desktop and since then i cannot get to my dhcp server and thus i cannot access my router.

I do the whole 'ipconfig/release' thing and that works, but then when doing 'ipconfig/renew' i get the error message saying "unable to contact dhcp server request timed out".

Have tried various things, such as rebooting and even resetting my router and have also googled a fair bit as well, but so far, no luck.

*edit. Have also tried to repair the LAN connection but that did not work either...

Can anyone help me??

Windows XP Pro (no service pack)
router: SMC 7904BRA "Barricade"

Any advice would be much appreciated!! :)
 
Yer router's DHCP functionality has given up, or your network cable is borked, or not plugged in properly.

What is your router's IP Address?

Try to manually set your IP address to 192.168.0.2 ... i'm assuming that your router is on 192.168.0.100 or .1 [i.e. your pc must have the same 3 digits as your router, with the last one being different]

Once this is done, try to ping your router. If you cannot ping your router, reset it to factory default settings, and then try again. Once you've got it, enter it's configuration facility and re-congifure it.

If all this fails .. either your NW card, cable or your router is borked.
 
stoke said:
Yer router's DHCP functionality has given up, or your network cable is borked, or not plugged in properly.

What is your router's IP Address?

Try to manually set your IP address to 192.168.0.2 ... i'm assuming that your router is on 192.168.0.100 or .1 [i.e. your pc must have the same 3 digits as your router, with the last one being different]

Once this is done, try to ping your router. If you cannot ping your router, reset it to factory default settings, and then try again. Once you've got it, enter it's configuration facility and re-congifure it.

If all this fails .. either your NW card, cable or your router is borked.
Click to expand...

Awesome. Thanks for the advice. I shall give this all a try and report back :)
 
Oops .. once it's configured, consider allowing your PC to get it's IP address from the router again by setting it back to auto-configure instead of hard coded.
 
make sure the DHCP Client service in WIndows has been started
 
stoke said:
Oops .. once it's configured, consider allowing your PC to get it's IP address from the router again by setting it back to auto-configure instead of hard coded.
Click to expand...

Erm once i set the Ip address manually and the subnet mask and default gateway, what do i set the DNS server to?
 
Control panel - > administrative tools -> services

U will see the DHCP Client service.Right click -> start.If it fails u will need to look into the Event viewer.If u donr understand the error message go to www.eventid.net and enter the Event ID number.It will show you how to fix it.
 
ubercal said:
Control panel - > administrative tools -> services

U will see the DHCP Client service.Right click -> start.If it fails u will need to look into the Event viewer.If u donr understand the error message go to www.eventid.net and enter the Event ID number.It will show you how to fix it.
Click to expand...

I tried that as well . It was running, so i stopped it and restarted it. Still no joy :(
 
Ye, sounds like a subnet / routing thing (the first 3 octets stoke was talking about), i.e. 192.168.0.x

Dunno if you know but your router's default config and DHCP might have been changed from the default.
It can also be setup to only serve DHCP on a certain IP range, which your newly pc should get if the router, NIC and cable is fine.
Safe / reserved hosts for specific IP's could also have been setup based on MAC, but then this should also still work if you did not change hardware.

Maybe you need new NIC driver after the Windows installation?

If all else fails you should be able reset the router to default config by pressing a button (check manual) or maybe flashing it to a previous firmware release.

After this you should at least be able to access the admin console (if pc, NIC, cable is fine of course) and check WTF ;)
You may even be up and running again after this cause router will assign IP automatically (if no IP has been hardcoded on the NIC)

Oh, and don't discount browsers, I have had stange happenings with certain browsers accessing router consoles.

There are local tests you can do to test NIC and windows, like ping tests, localhost checks, ping localhost or 127.0.0.1, etc.
Ping the IP of the router. Did you responses? You know that kinda stuff. ;)

This will at least start somewhere and tell you if pc / windows or NIC is buggered, routing messed up...

Good luck :)
 
lilDeath said:
Ye, sounds like a subnet / routing thing (the first 3 octets stoke was talking about), i.e. 192.168.0.x

Dunno if you know but your router's default config and DHCP might have been changed from the default.
It can also be setup to only serve DHCP on a certain IP range, which your newly pc should get if the router, NIC and cable is fine.
Safe / reserved hosts for specific IP's could also have been setup based on MAC, but then this should also still work if you did not change hardware.

Maybe you need new NIC driver after the Windows installation?

If all else fails you should be able reset the router to default config by pressing a button (check manual) or maybe flashing it to a previous firmware release.

After this you should at least be able to access the admin console (if pc, NIC, cable is fine of course) and check WTF ;)
You may even be up and running again after this cause router will assign IP automatically (if no IP has been hardcoded on the NIC)

Oh, and don't discount browsers, I have had stange happenings with certain browsers accessing router consoles.

There are local tests you can do to test NIC and windows, like ping tests, localhost checks, ping localhost or 127.0.0.1, etc.
Ping the IP of the router. Did you responses? You know that kinda stuff. ;)

This will at least start somewhere and tell you if pc / windows or NIC is buggered, routing messed up...

Good luck :)
Click to expand...

Thanks for the detailed reponse :)

Should have mentioned that the router is a week old. Swapped it out because it became faulty after a year of hard usage...So hopefully that is not the problem...

Will try the NIC driver idea ...
 
hj2k_x said:
Erm once i set the Ip address manually and the subnet mask and default gateway, what do i set the DNS server to?
Click to expand...
You don't really need a DNS server setting in your router's config for your local pc. When the router dials to the ISP it will receive your ISP's DNS settings, which is what your pc will use for general browsing and downloading mail and the like.

Some people only configure DNS on the router when they have specific requirements, like having to work around the 'floating IP" thing of ADSL, which is where DynDNS comes in. This is typically used for web servers and mail servers.
 
hj2k_x said:
Thanks for the detailed reponse :)

Should have mentioned that the router is a week old. Swapped it out because it became faulty after a year of hard usage...So hopefully that is not the problem...

Will try the NIC driver idea ...
Click to expand...
hhhmmm ... ok, well then it means your router is new and so is your OS, i.e. no customizations ... This should be ez ;)

All the routers I have worked with are basically plug-and-play, once you connect them up and follow instructions in the manual, you should be up and running in minutes, especially in accessing the admin console and setting it up the way you want.

and if you aren't even getting this far ... well then it points to cable / nic (driver or possibly hardware)

Rather odd still.
 
Maybe TCP/IP Stack has been corrupted somehow.Try reset it with the following command

netsh int ip reset resetlog.txt
 
ubercal said:
Maybe TCP/IP Stack has been corrupted somehow.Try reset it with the following command

netsh int ip reset resetlog.txt
Click to expand...

Ok, tried that. Also no change. Installed the latest NIC drivers now as well- also no change...

Will try the whole static IP idea...
 
If that doesnt work do the following

1. reset router back to factory default

2. Check manual for default IP

3. Set IP on workstation on the same IP Range as the Router.

4. If u cant find IP of router try

10.0.0.1 , 172.16.10.1 , 192.168.0.1 or 192.168.1.1
 
ubercal said:
If that doesnt work do the following

1. reset router back to factory default

2. Check manual for default IP

3. Set IP on workstation on the same IP Range as the Router.

4. If u cant find IP of router try

10.0.0.1 , 172.16.10.1 , 192.168.0.1 or 192.168.1.1
Click to expand...

Static Ip didnt work either....Have just tried what u just suggested here uber(modem's ip is 192.168.2.1)...I am at my wits end with this! :(
 
Don't know if this makes any difference- i didn't think it would - I am currently connected via a dialup dsl connection running over raspppoe. This is working fine, but i need to get into my modem to set it to bridge mode so that i can use Ant1b0dy's routesentry to run two connections concurrently...It was working perfectly this morning BEFORE i decided to format and reinstall windows...*sigh*
 
Intersting...DHCP still not working and i cannot access the router at all but routesentry is now up and running and both connections are working 100%. Wierd....:confused:
 
I am back. My dsl has been working fine since my last post. Both connections work fine over routesentry and all ahs been well...

BUT now i need to get into my router's config page to set it back to router mode so i can hook up my mom's laptop to the internet via a network type setup, and i still cannot access the setup page from any browser....

Any ideas??

Any help would be much appreciated!
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X