DHCP server will not bind to Network Interface.

[Bob H.]

I upgraded My Windows 2000 Advanced Server to Windows Server 2003
Enterprise Edition. Now my DHCP server will not bind to my Network
Interface.

My server is a Dell Poweredge 500SC, using the onboard NIC (Intel
Pro). This happened immediately after the upgrade. The System Log in
the Event Log shows the following error event:

Source: DhcpServer
Event ID: 1041
Description: The DHCP service is not servicing any clients because
none of the active network interfaces have statically configured IP
addresses, or there are no active interfaces.

Of course, my NIC does have a static IP address.

The problem I am having is similar to that described in MS KB article
832689.

Per MS article 298490, I can bring up the DHCP console, right click on
the Server and select properties, go to the Advanced tab, and click on
Bindings. It shows my Local Area Connection as unchecked. I can check
this and click OK, but if I go back into bindings, it is still
unchecked.

I did the following in an attempt to fix this:

1. Uninstalled the NIC and reinstalled it. No effect.
2. Uninstalled the DHCP service and then reinstalled and reconfigured
it. No effect.
3. Verified that MediaLink Sense is Disabled (see MS KB article
832689).
4. Installed Hotfix mentioned in MS KB article 832689. This had no
effect.
5. Installed a new PCI network adapter (Linksys LNE100TX). When first
installed, the DHCP console indicated the server would bind to this
adapter. However, as soon as I rebooted, it would no longer bind to
it.

So, I still cannot get my DHCP server to service any clients.

Has anyone else seen this behavior after an upgrade? Any fix to the
binding problem?

As an aside, during this I also tried to connect a couple USB wireless
adaptors to see if I could get another interface to bind. However, I
could never get a "Wireless Network" tab on my adapter properties
dialog. I don't know if this is related, or just another problem with
the W2K to W2K3 upgrade (I assume the later).

Thank you,
Bob H.
MCSE
bo...@lajollait.com

[Bob H.]

I found my own answer. Dell OpenManage RIS was running on the server
and grabbing the DHCP server port before the DHCP server could do so.
Apparently, the situation was reversed under Windows 2000. I found
this by running netstat -a -n -o to find the process that was grabbing
port 67 (DHCP Server) and then deleting that program from the server.
It is working just as expected now.

Still no resolution on the Wireless adapter connection, but a look at
the Microsoft HCL for Windows server 2003 shows no compatible wireless
adaptors.

FYI,
Bob

bo...@lajollait.com (Bob H.) wrote in message news:<ccccebf8.04021...@posting.google.com>...