Win2k not getting DHCP IP.

  • Thread starter Thread starter David
  • Start date Start date
D

David

Hi,

A roommate here with a Win2K system had to reinstall
his OS after replacing his motherboard. After the
reinstall, we can no longer get it to lease an IP from
the DHCP server (DSL router). Instead, it 'magically'
comes up with its own dynamic IP. Any attempts to
release or renew it are refused, either with a "DHCP
address cannot be relesed" or a "socket does not exist".

We are able to see other computers in the workgroup
when we punch in a valid static IP.

Any ideas? thanks

-David
 
David said:
Hi,

A roommate here with a Win2K system had to reinstall
his OS after replacing his motherboard. After the
reinstall, we can no longer get it to lease an IP from
the DHCP server (DSL router). Instead, it 'magically'
comes up with its own dynamic IP. Any attempts to
release or renew it are refused, either with a "DHCP
address cannot be relesed" or a "socket does not exist".

We are able to see other computers in the workgroup
when we punch in a valid static IP.

Any ideas? thanks

-David
Click to expand...

The important question is not so much if you can see other
computers but if you can see the DSL router. Can you ping it?
 
Are you getting a 169.x.x.x address? That's not really a dynamic IP in the
sense you want - it's an autoconfigured address you'll get when the computer
can't get a DHCP address. Check your NIC driver, cabling, everything.....
 
-----Original Message-----
Are you getting a 169.x.x.x address? That's not really a dynamic IP in the
sense you want - it's an autoconfigured address you'll get when the computer
can't get a DHCP address. Check your NIC driver,
Click to expand...
cabling, everything.....

Okay.. it is a 169.* So that's a sort of default.. though
I notice it generates it randomly. I was wondering if
the computer was doing it's own DHCP service somehow.

Will have to look into a driver update.. tough when it
can't get through to the internet. :)

-David
 
The important question is not so much if you can see other
computers but if you can see the DSL router. Can you
Click to expand...
ping it?

We can ping it (and see other computers) only when we
force a static IP on it (192.168.x.x) that matches the
type the router's DHCP uses. I can probably pull a
solution of registering the static IP on the router for
that computer.. but I /really/ want the computer to just
get it from the router's DHCP.
When the computer's on its default 169.x.x.x IP (aka,
set to dynamic IP, but failing to reach router).. we
can't ping the router, nor see any other computer.

Not sure what more to do.. any suggestions?

-David
 
David said:
ping it?

We can ping it (and see other computers) only when we
force a static IP on it (192.168.x.x) that matches the
type the router's DHCP uses. I can probably pull a
solution of registering the static IP on the router for
that computer.. but I /really/ want the computer to just
get it from the router's DHCP.
When the computer's on its default 169.x.x.x IP (aka,
set to dynamic IP, but failing to reach router).. we
can't ping the router, nor see any other computer.

Not sure what more to do.. any suggestions?

-David
Click to expand...

While your PC uses an address of 169.x.x.x, it will
never see any other PC or your router, because
its address is in the wrong subnet. To communicate
successfully with the other PCs, it must be in the same
subnet as they are, i.e. 192.168.? (you never told us the
third element of your IP addresses).

About your DHCP problem: It appears that your PC
is unable to reach your DHCP server. This is why
it fails to get an automatic address. I once had the
same problem: My ADSL router refused to allocate
IP addresses to some operating systems on a
multi-booting PC but did OK for other OSs.

I solved the problem in the short run by using a
fixed address for the problem OS. In the long run
the ADSL router decided to come to its senses and
do what it was supposed to do. Rebooting it might
help.

You could also get into the setup screen of your
router, turn off DHCP, save the settings, then turn
DHCP back on again and save the new settings.
 
Thanks for the response.. sounds like a finicky thing
without a clear-cut answer. Off to static IP I go.

-David
 
Back
Top