Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Tuesday, February 23, 2016 8:24 AM
Hello,
i came across this error while installing the AD services.
The manager shows an APIPA address instead of the server ip.
I found several "solutions" but none of these work for me. The server adapter that could have an APIPA was disabled during install. In ipconfig /all there is no 169.* ip address
I also removed and reinstalled the DHCP server.
Now i don't know what to do.
Anyone who could help me with this?
Regards Stephan
All replies (4)
Tuesday, February 23, 2016 8:30 AM ✅Answered | 1 vote
Sorry for the inconvenience.
Another adapter was not connected at all (no physical connection). After disabling this one it works ....
If a DHCP server needs a static ip (which is quite logical) why not programming the server to only listen on adapters with static ips?
Regards Stephan
Wednesday, February 24, 2016 4:48 AM
Hi Stephan,
Technically, multihomed domain controller is supported. However, it’s not recommended as numerous issues can occur in such an environment.
Thank you for sharing us whit your problem.If you have any other questions,feel free to post here.
Best Regards,
Cartman
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected].
Wednesday, February 24, 2016 8:33 AM
Hi Cartman,
i didn't want to create a multihomed domain controller.
The server has 4 LAN ports 2 disabed and 1 wasn't connected. This caused the error.
Which is not right. How can an adapter get an APIPA address when it is not connected and has a link? In my opinion this should be fixed.
Regards Stephan
Wednesday, February 24, 2016 9:26 AM
Hi Stephan,
As far as I know,when a DHCP server cannot be contacted,client will automaticly self-configure an IP address with APIPA.That unused NIC knows there is a DHCP server on the device,but it can't contact because it has no connection,so it get a 169.X IP address.So the best practice is disable the unused NIC on DHCP server.
Best Regards,
Cartman
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected].