We have multiple scopes on windows 2012 R2 servers. I had a scope that was having issues with database cleanup (it would say that it was out of available addresses even though there were still 150 addresses available). In troubleshooting I deleted the scope and recreated it. When I tried to configure the failover it failed on the «creation of failover configuration on host server» then it says «the DHCP failover relationship state is not normal. Configure failover failed. Error: 20120». I have been unable to find anything useful on the error 20120. All the rest of my scopes are not having problems with failover.
DHCPWindows Server 2012
- Remove From My Forums
-
Question
-
hello all,
thanks for the time. i am configuring a 2node dhcp hot standby failover. the problem is that i can get a couple of scopes to be configured for failover but then after a bit it loses connections. and then picks up communication. and then fails. this
is constant in the event logs. i have removed the partnerships and tried a few times… but same results. i can telnet from dc01 to dc02 on port 647. should i add a firewall excpetion for it? below are the logs. any help, suggestion,
thought is appreciated.Primary DHCP Server
Log Name: DhcpAdminEvents
Source: Microsoft-Windows-DHCP-Server
Event ID: 20267
Task Category: DHCP Failover
Level: Error
Keywords:
User: NETWORK SERVICE
Description:
Failover protocol message CONNECTACK from server 192.168.1.2 for failover relationship dc01.contoso.com-192.168.1.2 was rejected because message digest failed to compare.Log Name: DhcpAdminEvents
Source: Microsoft-Windows-DHCP-Server
Event ID: 20254
Task Category: DHCP Failover
Level: Information
Keywords:
User: NETWORK SERVICEDescription:
Server has established contact with failover partner server 192.168.1.2 for relationship dc01.contoso.com-192.168.1.2Partner Server Logs:
Log Name: DhcpAdminEvents
Source: Microsoft-Windows-DHCP-Server
Event ID: 20259
Task Category: DHCP Failover
Level: Information
Keywords:
User: NETWORK SERVICEDescription:
The failover state of server: dc01.contoso.com for failover relationship: dc01.contoso.com-192.168.1.2 changed to : COMMUNICATION_INT.Log Name: DhcpAdminEvents
Source: Microsoft-Windows-DHCP-Server
Event ID: 20255
Task Category: DHCP Failover
Level: Error
Keywords:
User: NETWORK SERVICEDescription:
Server has lost contact with failover partner server 192.168.1.1 for relationship dc01.contoso.com-192.168.1.2 .Event ID: 20254
Task Category: DHCP Failover
Level: Information
Keywords:
User: NETWORK SERVICE
Description:
Server has established contact with failover partner server 192.168.1.1 for relationship dc01.contoso.com-192.168.1.2 .
Answers
-
the resolution was setting the MTU to 1500.
netsh interface ipv4 set subinterface «Local Area Connection» mtu=1500 store=persistent
-
Marked as answer by
Monday, February 29, 2016 1:09 AM
-
Marked as answer by
We’re gonna solve the DHCP server authorization issue in this post. Error code looks like below:
“The authorization of DHCP Server failed with Error Code: 20070. The DHCP service couldn’t contact Active Directory.”
This is possibly due to user permissions on AD. Ensure you input Domain Administrator (DA) Credentials in the DHCP Commit dialog box, instead of proceeding with logged in account. There are chances that though you logged into DC using some user credentials, it doesn’t necessarily mean you are DA/EA. It could just be an account Admin locally, but not on Domain/forest. Check the DA user in ADUC and ensure you input those credentials to solve this.
Other things you should try if the credentials are DA is, ensure AD services are up and running. Check launching ADUC, Try Restarting DHCP Server services, Try re-installing DHCP from server manager. If you still encounter any issues, please message here, so we can further look into it to get it resolved.
Cheers!
Chaladi
Hi,
This is not a VMware issue but a configuration problem in your virtual Windows 2012 server.
I’m not a Windows administrator, but I think that your initial preferred DNS server should at least point to your own server instead of to google’s DNS.
You might even have to start over, can’t remember exactly as it’s been a while since I configured one of those, but you have to choose the correct steps for active directory in the wizard while setting up your DHCP server.
I think you’ll have more luck posting this specific issue in one of microsoft’s forums.
—
Wil
| Author of Vimalin. The virtual machine Backup app for VMware Fusion, VMware Workstation and Player |
| More info at vimalin.com | Twitter @wilva
Перейти к содержимому
Windows Server 2012 позволяет довольно просто организовать отказоустойчивую конфигурацию из двух DHCP серверов. Выбираем в контекстном меню протокола или конкретной области «Configure Failover…», указываем тип конфигурации (балансировка нагрузки или режим горячей замены) и настраиваем соответствующие параметры (период синхронизации базы, процент обслуживаемых клиентов и т.д.). После этого все настройки первого сервера (области, параметры) автоматически переезжают на второй сервер.
Но, как всегда, есть нюансы.
В моём случае это вылилось в появление ошибки
Error: 20010. The specified option does not exist.
Причина оказалась в том, что для некоторых областей были созданы кастомные параметры (для телефонии). А как выяснилось, параметры, созданные вручную, сервер не может воссоздать автоматически на партнёре. Прописать на областях может, а создать — нет.
Решение — зайти в «Set Predefined Options…» на втором сервере и воссоздать вручную все кастомные параметры, прописанные на первом сервере. Если создавали их не вы, то отличить кастомные параметры от встроенных поможет кнопка «Delete», которая становится активной только в случае выбора параметра, созданного вручную (см второй скриншот). В моём случае, помимо параметров, пришлось прописать ещё и дополнительный Vendor Class. После чего всё успешно отреплицировалось и заработало.
- Remove From My Forums
-
Общие обсуждения
-
Здрасьте. Есть два DC (основной и резервный) оба на Windows 2003 Server R2 EE SP1. Если выключить серваки, а потом включать их, то возникает проблемка. Служба DHCPServer зависит от службы каталогов. При запуске сервака DHCPServer стартует раньше службы каталогов, не находит AD и благополучно умирает, записав в EventLog сообщения об ошибках 1059, 1046, 1059. Именно в этой последовательности.
Ошибка 1059: «The DHCP service failed to see a directory server for authorization.» Источник: DhcpServer
Ошибка 1046: » The DHCP/BINL service on the local machine, belonging to the Windows Administrative domain office.mediapark, has determined that it is not authorized to start. It has stopped servicing clients. The following are some possible reasons for this:
This machine is part of a directory service enterprise and is not authorized in the same domain. (See help on the DHCP Service Management Tool for additional information).
This machine cannot reach its directory service enterprise and it has encountered another DHCP service on the network belonging to a directory service enterprise on which the local machine is not authorized.
Some unexpected network error occurred. Источник: DhcpServer
Оживает DHCР только после ручного перезапуска службы DHCPServer.
Подскажите, как заставить службы, зависимые от AD стартовать после запуска AD. Такая ситуация наблюдается еще и со службами W32Time и LSASRV, но, как я понял, на стабильность работы это не влияет и Microsoft предлагает не обращать на это внимания (http://support.microsoft.com/kb/823712/).
Заранее спасибо.
-
Изменен тип
12 декабря 2010 г. 17:01
-
Изменен тип
I’m running two Server 2012 Standard DC’s with DHCP running on them. For the most part, DHCP failover has been working great for my main workstation scope. I added two scopes recently, and noticed that the 2nd server was not seeing them as part of the failover. No problem, it seems logical that each scope needs to be added to the failover arrangement. I went through the config screens to do that, and all looks good (used existing failover relationship), and then when it brings up the confirmation screen, I get the following errors:
Add Scopes on partner server………….successful
Disable scopes on partner server……..successful
Creation of failover configuraiton on host server…….Failed
The DHCP failover relationship state is NOT NORMAL
Roll back delete scopes on partner server…….successful
Configure failover failed: Error: 201210. The DHCP failover relationship state is NOT NORMAL.
The
KB2756872 is already applied, which fixes some issues related to this. I restarted DHCP services on both, and double checked my scope config and all looks good. It’s a very simple scope setup. No reservations, or anything.
I am hesitant to delete the failover relationship and recreate it, because in the past, I have seen that break DHCP altogether. Any advice?
O.C
I had an experience where an active directory controller was forcibly removed from the domain, fortunately it didn’t have any FSMO Roles associated to it but it was setup as a backup/failover DHCP server. This assumes you have a backup or secondary AD Server and it is authorized to be a DHCP server.
First you have to create all scope options from your primary DHCP server to the backup/failover dhcp server. If you try to run failover without setting up custom options then you will get Error 20010. The specified option does not exist.
 |
| Active Directory DHCP Error 20010. The specified option does not exist |
You will have to login to your failover (or secondary) AD controller and replicate the options. This is pretty straight forward except for the Mitel Phone Config on option 43. On my post about Setting up Mitel Phones with PFSense I have all the info here for doing that but with AD it’s a bit trickier.
 |
| Replicate DHCP Scope options from the primary DHCP server to the backup. Must be done by hand. |
Select your IPv4 and right click and select «Define Vendor Classes…»
 |
| Define Vendor Classes… |
Select Add
Display Name — «Mitel IP Phone Options»
Description: Mitel Specific Options for IP phone provisioning
in the ASCII type without quotes
«ipphone.mitel.com»
in the binary add 00 after the 6D. If you don’t you’ll have problems because the phone is looking for that null value.
 |
| Create Mitel IP Phone Class |
Next go back to your IPv4 and right click and select predefined options as shown below.
 |
| Set Mitel Predefined options |
In «Option class», drop down «Mitel IP Phone Options»
 |
| «Option class», drop down «Mitel IP Phone Options» |
Click [Add]
For name, enter «Mitel Phone Config»
For data type, choose String
For Code, enter 43
For description, enter «Mitel configuration string»
 |
| Mitel Predefined Options and Values |
Click [OK] to commit
You can now add the Mitel Scope Options to the scope by going to «scope options» right click select «Configure Scope Options» then go to advanced and select the vendor class we created called «Mitel Phone Options» and make sure it is checked and add your Mitel Configuration String.
 |
| Mitel Scope Options |
Once we setup all our scope options on the failover/secondary AD controller we can then run the failover and it should succeed.
Now in this instance I had an issue with the reconcile database but if you didn’t have a failover dhcp server before you should be good to go. Below I go over how to fix the an issue with the DHCP database where it is not reconciling properly.
Fixing the Reconcile Database
The Primary DHCP server was still trying to reconsile to the old failover DHCP server, as shown below.
 |
| Reconcile DHCP Database |
 |
| DHCP Reconcile IP |
To fix this (because our scope won’t properly reconcile) we need to use netsh.
go to the netsh prompt by typing «netsh» without quotes then press enter.
 |
| netsh list command |
Once you verified the list and you can then remove the offending ip by using
netsh> dhcp server scope $youripscope delete lease $ipaddress
 |
| netsh delete cmd |
now do a netsh list command to verify the offending IP is gone
Once verified you can go to your DHCP server and reconcile your DHCP and you should get a message «The database is consistent»
 |
| Error is removed database reads on consistent. |
Sources:
http://blog.solar.co.uk/dhcp-options-for-mitel-phones
https://docs.microsoft.com/en-us/previous-versions/windows/it-pro/windows-xp/bb490941(v=technet.10)
http://www.unixwiz.net/techtips/mitel-ipphone-networking.html
Перейти к содержимому
Windows Server 2012 позволяет довольно просто организовать отказоустойчивую конфигурацию из двух DHCP серверов. Выбираем в контекстном меню протокола или конкретной области «Configure Failover…», указываем тип конфигурации (балансировка нагрузки или режим горячей замены) и настраиваем соответствующие параметры (период синхронизации базы, процент обслуживаемых клиентов и т.д.). После этого все настройки первого сервера (области, параметры) автоматически переезжают на второй сервер.
Но, как всегда, есть нюансы.
В моём случае это вылилось в появление ошибки
Error: 20010. The specified option does not exist.
Причина оказалась в том, что для некоторых областей были созданы кастомные параметры (для телефонии). А как выяснилось, параметры, созданные вручную, сервер не может воссоздать автоматически на партнёре. Прописать на областях может, а создать — нет.
Решение — зайти в «Set Predefined Options…» на втором сервере и воссоздать вручную все кастомные параметры, прописанные на первом сервере. Если создавали их не вы, то отличить кастомные параметры от встроенных поможет кнопка «Delete», которая становится активной только в случае выбора параметра, созданного вручную (см второй скриншот). В моём случае, помимо параметров, пришлось прописать ещё и дополнительный Vendor Class. После чего всё успешно отреплицировалось и заработало.