Re: DHCP not working on Windows 2003 Server

Richard,

First, the way to force a client to see the new DHCP server is simple...
Reboot it. If that is not an option, do an "ipconfig /release" and an
"ipconfig /renew" at the command line. If it is a client side issue, these
should work. Now that the obvious is out of the way, did you create a
domain? or upgrade to a new AD Win2003 domain from an older NT4 domain? The
issue may be Authorization. A DHCP server in the old days could just pop in
anytime. In Win2000 and Win2003 you have to Authorize it to allow it to
accept client requests.

From the DHCP Help File:
To authorize a DHCP server in Active Directory

1.. Open DHCP.
2.. In the console tree, click DHCP.
3.. On the Action menu, click Manage authorized servers.
The Manage Authorized Servers dialog box appears.

4.. Click Authorize.
5.. When prompted, type the name or IP address of the DHCP server to be
authorized, and then click OK.
Notes

a.. For a DHCP server to be authorized in an Active Directory domain
environment, you must first be logged on as a member of the Enterprise
Admins group for the enterprise where the server is being added.
b.. To open DHCP, click Start, click Settings, click Control Panel,
double-click Administrative Tools, and then double-click DHCP.
c.. This procedure is usually only needed if you are running a DHCP server
on a member server. In most cases, if you are installing a DHCP server on a
computer also running as a domain controller, the server is automatically
authorized the first time you add the server to the DHCP console.
d.. The fully qualified domain name (FQDN) of the DHCP server cannot
exceed 64 characters. If the FQDN of the DHCP server exceeds 64 characters,
the attempt to authorize the server fails with the error message, "A
constraint violation has occurred." If your DHCP server FQDN exceeds 64
characters, authorize the server using the IP address of the server instead
of its FQDN.
e.. DHCP servers running Windows 2000 cannot be authorized using the
Windows Server 2003 administrative tools (the DHCP console and the Netsh
commands for DHCP) unless Windows 2000 Server Service Pack 2 is installed.
Hope this helps,

jh



"Richard" <> wrote in message
news: om...
> The following is copied from an older thread, to whichI cannot reply
> unfortunately. I have the same problem right now, lots of discovers, a
> bunch of NACKs, but no offers being made, and no clients getting an IP
> address.
> Anyone familiar with this?
> --------------------------------------------------------------------------
>
> Greetings, currently in the process of upgrading domain to 2003 from
> NT. We installed a 2003 server at one of our sights and joined it to
> the 2003 domain. We configured dhcp to be the same as the NT server
> that was there. When we turn off the old nt server and turn on dhcp
> on the new server dchp fails. There are no events in the event
> viewer, DHCP is running on the new server. In statistics of new
> server it shows that discovers have been made and has some nacks but
> no acks and the clients fail to get an IP address. Is there some
> secret to getting the clients to know that a new dhcp server has been
> put in place? Thanks!
> Message 2 in thread
> From: Sharad Naik ()
> Subject: Re: DHCP not working on Windows 2003 Server
>
>
> View this article only
> Newsgroups: microsoft.public.windows.server.general
> Date: 2004-03-08 08:52:52 PST
>
>
> Did you Authorise the DHCP AND Activated the Scope?
> (In DHCP manager, right click on servername - Authorize, Right click
> on
> Scope- Activate)
>
> Sharad
> "netscience" <> wrote in message
> news: m...
> > Greetings, currently in the process of upgrading domain to 2003 from
> > NT. We installed a 2003 server at one of our sights and joined it to
> > the 2003 domain. We configured dhcp to be the same as the NT server
> > that was there. When we turn off the old nt server and turn on dhcp
> > on the new server dchp fails. There are no events in the event
> > viewer, DHCP is running on the new server. In statistics of new
> > server it shows that discovers have been made and has some nacks but
> > no acks and the clients fail to get an IP address. Is there some
> > secret to getting the clients to know that a new dhcp server has been
> > put in place? Thanks!
> Message 3 in thread
> From: Lanwench [MVP - Exchange]
> ( ahoo.com)
> Subject: Re: DHCP not working on Windows 2003 Server
>
>
> View this article only
> Newsgroups: microsoft.public.windows.server.general
> Date: 2004-03-08 08:55:39 PST
>
>
> Did you authorize the new DCHP server on the W2003 server? Make sure
> the
> scope was active?
>
> netscience wrote:
> > Greetings, currently in the process of upgrading domain to 2003 from
> > NT. We installed a 2003 server at one of our sights and joined it to
> > the 2003 domain. We configured dhcp to be the same as the NT server
> > that was there. When we turn off the old nt server and turn on dhcp
> > on the new server dchp fails. There are no events in the event
> > viewer, DHCP is running on the new server. In statistics of new
> > server it shows that discovers have been made and has some nacks but
> > no acks and the clients fail to get an IP address. Is there some
> > secret to getting the clients to know that a new dhcp server has been
> > put in place? Thanks!
> Message 4 in thread
> From: netscience ()
> Subject: Re: DHCP not working on Windows 2003 Server
>
>
> View this article only
> Newsgroups: microsoft.public.windows.server.general
> Date: 2004-03-09 06:02:02 PST
>
>
> yes I activated the scope without a problem. When I turned the dhcp
> off on the NT machine and started the new 2003 machine you could see
> (dhcp stats) that is was recieving requests but no offers were made.

I'm seeing the same problem right now. I've got a pair of Win2k3 server
acting as DC/GC in a native Win2k3 domain. The DHCP server crashe
(IRQL_NOT_LESS_OR_EQUAL, Stop 0x0a), and so I installed DHCP on th
second DC/GC, authorized/activated the scope. No joy, clients stil
cannot lease an address.
Used last known good to get the original DHCP server to boot
removed/reinstalled DHCP, setup the original scope information
reactivated it.
Put a sniffer on the connection to the original DHCP server, see lot
of discovery broadcasts, a small number of requests, and NAKs only
This matches what I see on the server's DHCP log - only NAKs.

??

--
rhenrikse
-----------------------------------------------------------------------
rhenriksen's Profile: http://extremetechsupport.com/forum/...html?userid=55
View this thread: http://extremetechsupport.com/forum/...d.phtml?t=1577