Constant DHCP Conflicts on Windows 2003 Server

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

Hi,

I seem to be having big problems on our windows 2003 active directory,
with dhcp addresses on our client machines. Despite the fact that the
ip scope far exceeds the number of ip addresses we need, we are getting
ip conflicts on many of our machines (we have around 700 machines in
total, 95% of which are running Windows XP SP2). When you manually
release and renew the ip address on the PC, it gives the following
error message:

Windows IP Configuration

An error occurred while renewing interface Local Area Connection : The
DHCP client has obtained an IP address that is already in use on the
network. The local interface will be disabled until the DHCP client can
obtain a new address.

Trying to do an ipconfig -release and then an ipconfig -renew comes up
with the same error. After doing several ipconfig -renew commands, it
finally gets an ip address, but usually the one it had before, which is
having the conflict.

I originally thought that this was because we had two dhcp servers, one
which was NT4 and not registered with AD. I disabled this server, but
still got the same problems. I have then created another dhcp server
within the AD, running on Server 2k3, but as before, the problems
reoccur.

This is causing major problems with packets dropping and the PCs being
very slow on the network, along with various error messages which are
annoying the users, but I cannot work out what the problem is.

Has anyone had this same problem or something similar, or more
importantly, anyone know how to resolve it?

Many thanks,

Laurence

.

Relevant Pages

  • Re: newbie - client not replying to DHCPOFFER
    ... > I did write earlier about my dhcp woes. ... > the windows client and the firewall is disabled when i try with dhcpd. ... well on both Linux and Windows. ...
    (comp.os.linux.networking)
  • Re: Windows 7 doesnt update PTR
    ... I just noticed, I have a windows 7 client that never updates its PTR, evenn after a ipconfig /registerdns. ... By default, the client registers the A record, and DHCP registers the PTR. ... Clients that are running Windows Server 2003, Windows 2000, or Windows XP DHCP interact with DNS dynamic update protocol in the following manner: ...
    (microsoft.public.windows.server.dns)
  • Re: Windows 7 doesnt update PTR
    ... I just noticed, I have a windows 7 client that never updates its PTR, ... the client registers the A record, and DHCP registers the PTR. ... Clients that are running Windows Server 2003, Windows 2000, or Windows XP ...
    (microsoft.public.windows.server.dns)
  • DNS Problem-Please help
    ... I have a client that has a small LAN with 8 Users ... connecting to the internet via a SMB class router that is ... acting as a DHCP server. ... Win 98 machines will connect and resolve correctly on the ...
    (microsoft.public.windowsxp.general)
  • Problems with OWA login from W2K
    ... Windows 2000 Pro SP4 machines and Windows XP Pro SP2 machines. ... 2003 client as well as our SharePoint intranet runs without problems on ...
    (microsoft.public.windows.server.sbs)