Windows 2003 R2 DHCP Server Not Responding to DHCPRequests
- From: oogieboogie23@xxxxxxxxx
- Date: 4 Feb 2007 12:11:36 -0800
Hello everyone,
Having a nasty problem with a windows 2003 DHCP server, and I am
totally stumped at this point. I'm hoping I dont need to move to
statically assigned IPs.
I have a Windows 2003 R2 server running AD, a DNS server, and a DHCP
server. I've turned off the Routing & Remote Access service to avoid
any possible conflicts. All the services are integrated with AD.
The problem is that the server is not providing IP addresses to DHCP
clients. The DHCP service is running and is configurable. Its been
authorized in active directory and everything appears fine in that
respect.
I've monitored the network using ethereal/wireshark during a DHCP
negotiation and found that the server does not respond to DHCPRequest
packets with a DHCPAck. I've run the capture from the server, and
from clients on both WLAN and wired ethernet. Basically what happens
is as follows:
Seconds Message
6.184872 DHCP Discover 0.0.0.0 to broadcast
6.188911 DHCP Offer 192.168.2.2 to broadcast
6.193704 DHCP Request 0.0.0.0 to broadcast
11.18407 DHCP Request 0.0.0.0 to broadcast
20.18464 DHCP Request 0.0.0.0 to broadcast
36.18587 DHCP Request 0.0.0.0 to broadcast
All are of the same transaction ID. After that time period, the
windows client gives up and gives a "Limited or no connectivity" and
assigns an address using AIPAA or sets itself to 0.0.0.0.
I've looked at all the packet data, and nothing seems to be amiss.
The provided address is the first in the assigned range (192.168.2.3
is provided from 192.168.2.3-200).
Looking at the DHCP server "Display Statistics" option, I see that the
server doesnt seem to know its getting those request packets.
Discovers 57
Offers 57
Requests 5
Acks 7
Nacks, Declines, & Releases - 0
The server is running a firewall, but I first set rules to allow
traffic specific to DHCP (UDP 67,68 from 0.0.0.0, etc) and then simply
allowed all UDP traffic from anywhere, to uninstalling the firewall,
all to no avail. So the firewall does not seem to be the issue.
I've also ensured the DHCP bindings are to the active network card,
which they are. All other interfaces are completely disabled
including some VMWare virtual adapters. I've also tried disabling DNS
autoupdates to check if maybe the problem was with permissions to the
DNS records. I've uninstalled and completely reset the DHCP settings
from scratch. I'd rather not clear start the entire AD/DNS from
scratch for nothing so I havent done that yet.
Is there anything I might be missing in the server configuration, such
as security/authentication options?
The network was previously running on a Windows 2000 Server machine as
a 'Windows 2000 mixed' domain. The new domain is of type 'Windows
2000 native' and has a different fully qualified and NETBIOS name (its
totally new).
Each of the clients was migrated over to the new domain, but only some
of them kept their old IP addresses (I am not sure if the DHCP failed
for these as well, but they do show up in the DNS and in DHCP as
leased addresses). When I try to renew these clients manually, they
fail to get an IP from the server, and continue using their old
'Assigned by DHCP' IP.
This problem has been driving me crazy for about a week now... :-
( I'm both stumped and incredibly tired of looking at hundreds of
irrelevant google results :-D
I'm hoping someone can rescue me here.
Thanks in advance for any help or suggestions.
.
- Follow-Ups:
- Prev by Date: Re: Error When Printing More Than 20 Pages...Dell 1100 on WinServer2003
- Next by Date: Re: 2003 RRAS as home router
- Previous by thread: ESENT error on Domain Controller
- Next by thread: RE: Windows 2003 R2 DHCP Server Not Responding to DHCPRequests
- Index(es):
Relevant Pages
|
