1

Using Windows Server 2008 R2

Found an issue with my Domain Controller 1. Setup is basic and the main domain controller is hosting AD and DNS. The secondary cannot find the primary.

dcgetdcname failed error 1355

As well as computers that are on the domain show the network as Unidentified Network

DC1 shows the correct domain it is connected to and working correctly. DCDIAG on the DC1 shows everything running correctly. DC1 can also ping domain joined computers without a problem but cannot ping DC2.

DC2 also is the backup AD and DNS.

Googled everything under the sun but I can't get DC2 to see DC1 and the computers on the network to see the domain name correctly. I can't join computers to domain either as it says it cannot find the domain.

I can remote to the DC1 from any domain joined computer without a problem but I can't get to any fileshares on the DC1 either. Neither of the DCs are running NAT. This network is not internet joined.

Can anyone help?

EDIT1: NSLOOKUP cannot find the DNS servers. They time out.

EDIT2: DC1 and DC2 are using themselves as the DNS servers as they are marked as secondary's because they cannot reach each other to register each other as DNS servers for each other.

EDIT3: Update got DNS working only not sure how but now no computers on the network can reach the fileshares on the server itself. Firewalls are disabled and I can't find any issue with reaching them.

  • 4
    Are you running NT4? Because that's the last time there was ever a PDC/BDC. Where are you actually seeing the term "Primary Domain Controller" within your infrastructure? – Wesley Aug 19 '15 at 18:09
  • @Wesley sorry I am calling it the "Primary Domain Controller". I am running Windows Server 2008 R2 – JukEboX Aug 19 '15 at 18:15
  • What do the DC's use for primary and secondary DNS? What do the domain clients use for primary and secondary DNS? – joeqwerty Aug 19 '15 at 18:19
  • 3
    There is no such thing as a PDC or BDC anymore, you should avoid using these terms as you will only confuse people (and yourself). – Michael Hampton Aug 19 '15 at 18:32
  • 1
    @Jukebox: Best practice dictates that each DC use it's partner DC for primary DNS, itself for secondary DNS and 127.0.0.1 for tertiary DNS. Make sure that's how you have them configured. On the domain clients set the PDCe (the DC that holds the Primary Domain Controller Emulator FSMO role) as the primary DNS and the other DC as the secondary DNS. Then reboot your DC's one at a time and then reboot your clients. Then test again. – joeqwerty Aug 19 '15 at 18:44
1

My first guess is that you have routing or numbering issues. Check the IP addresses of the servers and ensure that they are getting them from DHCP. If the DCs are not on the same subnet, there needs to be a router in between them (if only a router on a stick). Check that they can actually ping one another. Check that firewalls, local and network, are not restricting necessary traffic like RPC and DNS.

From what you've posted, it really just looks like DC2 doesn't have a working network connection or lacks a route to and from DC1.

  • There is no DHCP. Everything is static. They are all on the same network with no subnets. Nodes can ping each other and the DCs. Oddly enough DC1 can't ping DC2 by name but it can by address. DNS and RPC are being allowed through firewall correctly on both DCs. – JukEboX Aug 20 '15 at 11:52

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.