Server 2003 DHCP server port hangs

I have a Server 2003 configured as a local (home) network DHCP server (among
other functions). The server is also sharing its DSL connection (on a second
port controller) to other clients on the local network.

At least once a day, the DHCP server port "hangs". Local clients cannot
establish connections to the server, cannot connect to the internet through
the server via the DSL connection, cannot obtain a DHCP IP address, the
server does not appear as a member of the local group from other clients,
etc. The DHCP port appears to be normal from the server, and the internet via
DSL is accessable from the server. Performing a "repair" operation on the
server's DHCP port does not fix the problem. Disabling and then Enabling the
port fixes the problem.

Any help appreciated...

Check that your DSL router has DHCP disabled. Windows will stop its DHCP
server if it detects another on the network.

"LarryPullingTeeth" wrote:

> I have a Server 2003 configured as a local (home) network DHCP server (among
> other functions). The server is also sharing its DSL connection (on a second
> port controller) to other clients on the local network.
>
> At least once a day, the DHCP server port "hangs". Local clients cannot
> establish connections to the server, cannot connect to the internet through
> the server via the DSL connection, cannot obtain a DHCP IP address, the
> server does not appear as a member of the local group from other clients,
> etc. The DHCP port appears to be normal from the server, and the internet via
> DSL is accessable from the server. Performing a "repair" operation on the
> server's DHCP port does not fix the problem. Disabling and then Enabling the
> port fixes the problem.
>
> Any help appreciated...

Thanks, Wendel,

While that seems like a possibility, I don't have a DSL router. My DSL modem
connects directly to a port on the server, and the server "shares" the DSL
connection to the local network via a second port - a "standard"
configuration, from what I can tell by reading the documentation. The server
receives its IP address via DHCP from the ISP through the DSL connection (an
address in the ISP's domain), and provides DHCP service to the local network
- a standard "local" (168.192.0.x) network. This worked for several years
using a WinXP system as the server, but the Server 2003 system seems to
exhibit this problem. In fact, the Server 2003 system seemed OK for several
months, and then this behavior began. It may be related to some security
update... not sure, because I didn't keep records of this problem for several
months. At first, it only happened every couple of weeks - now it's amost
(but not quite) a daily occurrence.

"Wendel Hamilton" wrote:

> Check that your DSL router has DHCP disabled. Windows will stop its DHCP
> server if it detects another on the network.
>

Does DHCP log any events?

"LarryPullingTeeth" wrote:

> Thanks, Wendel,
>
> While that seems like a possibility, I don't have a DSL router. My DSL modem
> connects directly to a port on the server, and the server "shares" the DSL
> connection to the local network via a second port - a "standard"
> configuration, from what I can tell by reading the documentation. The server
> receives its IP address via DHCP from the ISP through the DSL connection (an
> address in the ISP's domain), and provides DHCP service to the local network
> - a standard "local" (168.192.0.x) network. This worked for several years
> using a WinXP system as the server, but the Server 2003 system seems to
> exhibit this problem. In fact, the Server 2003 system seemed OK for several
> months, and then this behavior began. It may be related to some security
> update... not sure, because I didn't keep records of this problem for several
> months. At first, it only happened every couple of weeks - now it's amost
> (but not quite) a daily occurrence.
>
> "Wendel Hamilton" wrote:
>
> > Check that your DSL router has DHCP disabled. Windows will stop its DHCP
> > server if it detects another on the network.
> >
>