16th June 11:35
dns test failed in netdiag
I know you want to resolve it. We want to help.
DCs with more than one NIC are very problematic. It is because both NICs for
the one DC get registered into DNS. You said earlier that DNS registration
is ok. Well, if both interfaces are registered, that is not ok. This is
because of the external interface is registered, and the client gets the
external IP, the client cannot reach the DC. This is also true for the other
DC when trying to communicate. It also causes a duplicate name issue with
NetBIOS names. There are many, many other issues that arise from multiple
NICs on a DC.
If it is for internet access, what I recommend, and many here will agree,
the best way is to disable one of the NICs, and get an inexpensive router to
handle internet access (NAT role). Otherwise, a multihomed DC will require
registry and other changes in order to make sure AD functions on it
properly. I have the steps to make these changes, but it is highly
recommended to not make all the changes and just get a router.
Also, it is much easier to use DHCP for your 60 clients to insure they all
get the proper configuration. I have seen many times over and over where
errors are made when manually setting IP configurations on many clients.
Can you elaborate on why there are two NICs, please? Explain its role.
Post the errors you are seeing in netdiag, please. Also run a dcdiag /v and
post those errors as well.
Also, please provide an unedited ipconfig /all from the two DCs, as well as
one sample workstation. This will help us with understanding how you've
configured your AD infrastructure.