Re: DHCP not working on Windows 2003 Server

Discussion in 'Windows Server' started by Joseph J. Hand, Jun 4, 2004.

  1. 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



     
    Joseph J. Hand, Jun 4, 2004
    #1
    1. Advertisements

  2. Joseph J. Hand

    rhenriksen Guest

    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.

    ??
     
    rhenriksen, Oct 8, 2004
    #2
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.