DHCP server times out

[Guest]

Here's my situation: I have a hand-built Athlon XP 2200+ system, running Windows XP Home with an integrated SIS 900 NIC. It works perfectly on my school's network (a T1 with its own servers), but won't connect to my home router (3 functioning computers + my idiot computer) hooked up to a cable modem
My computer seems to like the IP adress "169.254.x.x" with a subnet mask of "255.255.0.0". I have tried removing/reinstalling the drivers for my network card. Using "ipconfig /release, ipconfig /renew" simply gives me the message "unable to contact your DHCP server. Request has timed out." Replacing "winsock" and "winsock2" entries in the registry (which like to get corrupted) fixes all my problems at school, but none at home. Disabling and then enabling the connection gives me an IP of 0.0.0.0 for about 2 minutes, then the computer "finds" the 169.254.x.x number. Manually inputting the IP information displays all of the info I input, but aparently doesn't use it as no DHCP is available to give a lease. I have done basically everything short of plugging my computer straight into the cable modem
I have scoured every corner of the Knowledge Base for help, and, finding none, have now turned to the boards. I am thinking that I will ultimately have to re-install windows, but I can't get at my windows disk for another month. If anyone can lend a hand, I will be endebted to your service forever.

 

[John]

What luck. You have written my question for me. I have the
exact same problem....to a T. Reinstalling TCP/IP does not
help either following the winsock reinstall. Please,
anyone, help us!!!!!

-----Original Message-----
Here's my situation: I have a hand-built Athlon XP 2200+

system, running Windows XP Home with an integrated SIS 900
NIC. It works perfectly on my school's network (a T1 with
its own servers), but won't connect to my home router (3
functioning computers + my idiot computer) hooked up to a
cable modem.

My computer seems to like the IP adress "169.254.x.x"

with a subnet mask of "255.255.0.0". I have tried
removing/reinstalling the drivers for my network card.
Using "ipconfig /release, ipconfig /renew" simply gives me
the message "unable to contact your DHCP server. Request
has timed out." Replacing "winsock" and "winsock2"
entries in the registry (which like to get corrupted)
fixes all my problems at school, but none at home.
Disabling and then enabling the connection gives me an IP
of 0.0.0.0 for about 2 minutes, then the computer "finds"
the 169.254.x.x number. Manually inputting the IP
information displays all of the info I input, but
aparently doesn't use it as no DHCP is available to give a
lease. I have done basically everything short of plugging
my computer straight into the cable modem.

I have scoured every corner of the Knowledge Base for

help, and, finding none, have now turned to the boards. I
am thinking that I will ultimately have to re-install
windows, but I can't get at my windows disk for another
month. If anyone can lend a hand, I will be endebted to
your service forever.

 

[Paul Russell]

As a first step here lets try to re-establish connectivity to the router.

Since I am not sure which router you have (assuming linksys) you can
statically configure your PC to 192.168.1.x (where x >= 2 but not 1).

After you do this see if you can access the router management tool via the
web interface (http://192.168.1.1)

Assuming you have the logon password you should be able to verify that the
DHCP server on the device is running (consult your router manual for
interface specifics).

If it is not running simply re-enable DHCP Server ... if DHCP is not an
available option you should take it back to the store or complain to your
manufacturer since providing basic service like DHCP is a requirement for
IGD/UPnP enabled routers.

Start there and let us know how it goes.

Here's my situation: I have a hand-built Athlon XP 2200+ system, running

Windows XP Home with an integrated SIS 900 NIC. It works perfectly on my
school's network (a T1 with its own servers), but won't connect to my home
router (3 functioning computers + my idiot computer) hooked up to a cable
modem.

My computer seems to like the IP adress "169.254.x.x" with a subnet mask

of "255.255.0.0". I have tried removing/reinstalling the drivers for my
network card. Using "ipconfig /release, ipconfig /renew" simply gives me
the message "unable to contact your DHCP server. Request has timed out."
Replacing "winsock" and "winsock2" entries in the registry (which like to
get corrupted) fixes all my problems at school, but none at home. Disabling
and then enabling the connection gives me an IP of 0.0.0.0 for about 2
minutes, then the computer "finds" the 169.254.x.x number. Manually
inputting the IP information displays all of the info I input, but aparently
doesn't use it as no DHCP is available to give a lease. I have done
basically everything short of plugging my computer straight into the cable
modem.

I have scoured every corner of the Knowledge Base for help, and, finding

none, have now turned to the boards. I am thinking that I will ultimately
have to re-install windows, but I can't get at my windows disk for another
month. If anyone can lend a hand, I will be endebted to your service
forever.

 

[Guest]

Well Paul, I tried that. Got the router menu up on a working machine
and everything's in order. I even manually set my dead machine to
an IP in the router's range, but to no avail, just get a good old "DNS
server not found" in explorer. I've heard that removing SP1 can fix
this problem, but can you do that to an edition of windows with SP1
embedded? Hmm, sounds like a whole new thread.
Oh yea, my router is a Linksys, just so ya know.

 

[Guest]

Hold on, new development here.... I now get the error
message "The requested service provider could not be
loaded or initialized" when running "ipconfig /renew" in
the command prompt. Don't you just love computers?

 

[Paul Russell]

Hi Andy,

sounds good.

What you need to do now is verify your WAN side settings of the router is
enabled and configured correctly (per your ISP). That should solve this
issue.

The 'Requested service provider" message, not sure what that is about.
Generally if your router is providing PPPoE (which I am infering here) than
you should not have to enable any PPPoE stuff on Windows. Give us more
details here..

("Don't you just love computers?" yes

 

[Steve]

if I may join in the fun, have nearly identical problem...
Have W-XP home edition. Everytime I boot up, takes a long time to let me
have access to PC functions such as launching an app or opening Hard drive..
Found in Event Log that DHCP cannot get an IP address so after about
1.5mins, assigns its own IP. What normally booted up in 30 secs, now takes
2 mins plus.

PC is Ethernet connected to Linksys Router.
Also tried connecting it directly to DSL SPeedStream modem, same result.

Note: after 2 mins or so, I have full internet access at high speed.

Earthlink had me reset all TCP/IP connections using NETSH command.
Deleted Network Adaptor and had PC reinstall.
Also tried to assign my own IP address and DNS instead of automatic but
problem still exists.

So on the positive side, after about 2 mins, I get Internet Connectivity but
this problem started out of nowhere two weeks ago. I'm wondering.....did MS
send us a Windows Update that we all downloaded and now experiencing DHCP
problems?

 

[Guest]

Steve, I wish my problem was identical to yours. But alas, it is not.
I have now set up the router myself (after killing it on accident) and
everything is working properly on that end, so my problem is not
with my router. I even skipped the router and went straight into
the cable modem, but still no luck. PPoE is enabled, the LAN and
WAN setups are fine, and the DHCP and DNS are working with the
three other computers on the network. I am going to try and install
new NIC drivers direct from SIS next and see if that helps, but I'm
not too hopeful.
-Andy Spicer

 

[Guest]

Well, new NIC drivers did not resolve my woes... I
am now going to use an old copy of XP on top of
mine and hope that it will fix my problems. Thanks
for all the help, but it seems that re-installing
windows is yet to be a thing of the past.
-Andy Spicer

 

[Guest]

FINALLY I'VE FIXED IT! It seems that re-installing windows
updating drivers, and even putting in a new NIC had n
effect on my situation. What did was flashing my BIO
then fixing my sockets. Thanks for all your help guys

-Andy Spicer