HaulnSS
asked on
Migrating Server 2003 to Server 2008, cannot get DHCP to function on new server.
I added a 2008 server to the network this spring, everything has been fine. DNS was replicating well, etc. I am looking to finish moving everthing from my 2003 DC to 2008. I exported DHCP from 2003 to 2008 this morning. I imported DHCP to 2008, seemed to go ok. I transfered all my roles from 2003 server to 2008, seemed to go ok. Transfered domain naming master, PDC, Schema Master, RID master, infrastructure master.
Problem: My workstations don't see the DHCP server. The server gives me Event ID 1059, The DHCP service failed to see a directory server for authorization.
Problem: My workstations don't see the DHCP server. The server gives me Event ID 1059, The DHCP service failed to see a directory server for authorization.
on the 2008 server, from elevated command prompt do:
netsh dhcp show server
does the 2008 server show in the list?
if not, you need to authorize it
netsh dhcp add server <server.domain.com> <ip_address>
then restart dhcp server and see if event id 1044 shows in the system log saying the dhcp server is now authorized to serve clients
if it's working then you can use this to remove dhcp authorization from your 2003 server
netsh dhcp delete server <server.domain.com> <ip_address>
netsh dhcp show server
does the 2008 server show in the list?
if not, you need to authorize it
netsh dhcp add server <server.domain.com> <ip_address>
then restart dhcp server and see if event id 1044 shows in the system log saying the dhcp server is now authorized to serve clients
if it's working then you can use this to remove dhcp authorization from your 2003 server
netsh dhcp delete server <server.domain.com> <ip_address>
ASKER
netsh dhcp show server, shows my 2003 server and the new 2008 server. (also showed a really old server, deleted it using netsh dhcp delete server)
ASKER
Looking through AD, under Sites and Services, change domain controller, shows my new server as status "Unavailable"
Seems odd...doesn't it?
Follow up here, apparently this particular issue is because I disabled TCPIPv6.
Seems odd...doesn't it?
Follow up here, apparently this particular issue is because I disabled TCPIPv6.
any errors when you run dcdiag?
ASKER
dcdiag fails NCSecDesc - doesn't have replicating directory changes in filtered set access rights for the naming
DHCP/BINL service has determined that it is not authorized to start.
DHCPv6 warnings about dynamically assigned IP.
All else good.
DHCP/BINL service has determined that it is not authorized to start.
DHCPv6 warnings about dynamically assigned IP.
All else good.
NCSecDesc you can ignore if you didn't do adprep /rodcprep when you put the 2008 server in; don't need to do unless you are putting in read-only domain controllers
try deleting the dhcp authorization for that server and add again
change to using local address for dns resolution on the 2008 server; will need to do anyway since your 2003 server will go away
dhcpv6 you can ignore if you're not using IPv6
try deleting the dhcp authorization for that server and add again
change to using local address for dns resolution on the 2008 server; will need to do anyway since your 2003 server will go away
dhcpv6 you can ignore if you're not using IPv6
ASKER
I have "unauthorized" the server and authorized again, is that what you are suggesting? Didn't make a difference.
I have dns entry on 2008 NIC set to 2008 server already.
I have dns entry on 2008 NIC set to 2008 server already.
ASKER
One thought, I did copy my DHCP settings from my 2003 server and imported them.
ASKER
When I reboot server, last item item under DHCP event viewer is error 1046, when I restart DHCP when server is running, I get Event ID 1044, saying it's authorized and servicing clients, but the clients still can't get IP's.
i'm assuming you did export/import using netsh dhcp server ? if so, then that shouldn't be an issue going from 2003 to 2008. good sign the 1044 is appearing so that part is taken care of
if you reboot one of your workstations it never gets an address and just defaults to 169.254.0.0 network?
in the dhcp console, is the scope active?
if you reboot one of your workstations it never gets an address and just defaults to 169.254.0.0 network?
in the dhcp console, is the scope active?
ASKER
I did the export/import with neth dhcp server. I have since uninstalled and reinstalled DHCP, without using imported setttings, same results.
The workstation never gets an address, just the default 169.254.0.0
The scope is active
The workstation never gets an address, just the default 169.254.0.0
The scope is active
ASKER
Something else odd, I went ahead and demoted my old DC.
I can no longer open Exchange mailbox on my computer, after demoting the old server. I am using a static IP address to maintain connection with network.
Follow Up - changed DNS to new server on Exchange server, rebooted and I can open Outlook on my machine again.
I can no longer open Exchange mailbox on my computer, after demoting the old server. I am using a static IP address to maintain connection with network.
Follow Up - changed DNS to new server on Exchange server, rebooted and I can open Outlook on my machine again.
what's your server network configuration? do you have multiple interfaces? if so and the non-connected ones are not disabled, dhcp server might be binding to that
ASKER
I have multiple nics, that are bridged into one. I don't have any that are not connected.
FYI, I appreciate you sticking with me on this. I am getting close to having to visit 50 workstations and set IP's so that they work tomorrow.
FYI, I appreciate you sticking with me on this. I am getting close to having to visit 50 workstations and set IP's so that they work tomorrow.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Ultimately, it was the IP Helper address on the switch that needed changed. Once it was updated, DHCP worked just fine.
ASKER