Similar DHCP conflict

[Bart]

Hey guys, I noticed some people have been having
problems very similar to one I'm seeing.
I've got a workstation that's not grabbing an IP from
our server. I've verified that the DHCP services are
started on the server, I have the machine set to pick up
an IP and the domain controller automatically. When I set
the machine static it can connect to the server with no
problems, but when I switch back to DHCP and do ipconfig I
get:

Windows 2000 IP Configuration

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Autoconfiguration IP Address. . . : 169.254.125.74
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . :

So obviously, the computer doesn't know its connected
to anything. What I found perplexing was what I saw when I
tried to release the IP:

Windows 2000 IP Configuration

All adapters bound to DHCP do not have DHCP addresses. The
addresses were automatically configured and can not be
released.

I checked out the server, I have plenty of free IPs and
everything.
What do you think?

 

[Dale Weiss]

Hello,

Are we sure that the DHCP client service is running on the workstation?

Is/Are the NIC(s) set for autosensing? If so, manually configure 10 versus
100 etc.

Dale Weiss MCSA MCSE CISSP
PSS Security

This posting is provided "AS IS" with no warranties, and confers no rights.
Any opinions or policies stated within are my own and do not necessarily
constitute those of my employer. Use of included script samples are subject
to the terms
specified at http://www.microsoft.com/info/cpyright.htm