System cannot receive address from DHCP server

  • Thread starter Thread starter bt
  • Start date Start date
B

bt

I have a system that is no longer able to communicte with
the server. It does not receive an IP address from the
DHCP server. It is not a cabling or connection issue. I
can release and renew other systems so I know the DHCP
server is running fine. It is not an address pool issue.
I have tried a new NIC and receive the same error. Any
suggestions?
 
What do you get when you try to renew your IP?
Any errors in your event logs?
Tried a winsock repair tool?
 
When my PC starts up it cannot receive a DHCP address so
it "autoconfigures" and gives itself an address. As a
result, when I try to release or renew it tells me it is
unable to perfrom the operation b/c no socket exists.

My event log does have errors, it starts with a DHCP error
that says it was unable to contact the DHCP server. The
other errorsappear to be related to that fact.

I have physically moved this PC to ensure it has NOTHING
to do with cabling, etc. I am now on a connection that I
know to be good.

I am running Win 2000 on this system.

I just tried to remove myself from the domain and assign
the PC to a workgroup. I then tried to reconnect to the
domain. I use the wizard or go through properties and it
tells me it is unable to contact the domain "XXXX.XXX" it
says it is unavailable? or does not exist.

Any ideas????
 
I also had the same problem. We moved the DHCP server to a new box that had
the same IP address as the old box. Must have caused confusion with the DHCP
client.

I went to every machine and disabled the Network connection, then enabled
it. We were ok after that.

I think the registries had 2 entries for the one NIC. One record was
"pointing" to the old server. The disable/enable cleaned up the registry.
 
Thanks for your response. I typed this query a while ago, and then I found a
solution that worked.

Basically, I had to go into the registry and rename the winsock to make keep
it as an older version and then allow a new winsock to be created. The exact
details escape me--I had the precise instructions that I found from the
thread on editing the registry for this, etc.

What caused this problem was eliminating the needed registry winsock entries
from the anti-spyware.
 
Back
Top