We have a poweredge 1950 with Win2k3 Enterprise, and it has active directory configured on it. DHCP, however, doesn't work. Right now the router is acting as DHCP server (always has), but once I disable it's DHCP server and enable the Win2k3 server, the network falls apart. I ran a protocol analyzer on the connection and it does see the DISCOVER packets - but gives no response.
I have tried reinstalling the NIC drivers, the TCP stack, DHCP server (fresh config), and DHCP service (remove & add program). Nothing seems to work.
We have a Win2k server that can run DHCP just fine (which I configured, without this problem).
Any ideas?
2007-07-13 16:33:44 · 2 answers · asked by k_thorpe_2000 2 in Computers & Internet ➔ Computer Networking
The Win2k server is being replaced by the 2k3. Either way, it does not do DHCP for the network (I tried it but wanted to wait), and is not an AD controller - so it can't be elevating to PDC, since that is gone in AD
2007-07-13 16:55:22 · update #1
Have you authorized the DHCP server? DHCP servers must be authorized by an admin with Enterprise Admin credentials before the DHCP server will start handing out addresses. You can install and configure the DHCP server with Domain Admin rights but until it's been authorized in AD by an Enterprise Admin it will not function. In the DHCP Server snap-in, right click on the DHCP server and select "Authorize" from the context menu.
The above poster is simply wrong. DHCP can run on ANY server on the network. It does not need to run on a DC. And there's no such thing as a PDC in AD -- that went away with NT. (There is a PDC Emulator FSMO role but the DHCP server service does NOT need to run on the PDC Emulator role holder.)
2007-07-14 04:30:27 · answer #1 · answered by Bostonian In MO 7 · 0⤊ 0⤋
You are are going to have to set the 2003 server up as the primary domain controller server.
2007-07-13 23:39:00 · answer #2 · answered by sosguy 7 · 0⤊ 1⤋