Server Manager - Target Name Resolution Error

[RowlandoGloom]

Morning,

 

I currently have a 2012R2 DC servicing a small network of about 50 PCs.

 

I'm trying to add a second, so installed Windows Server on the second machine - set it's IP and DNS entries etc. When trying to access it in server manager - I receive an error, "Target Name Resolution Error". When I try to connect via PS, "...the server name cannot be resolved".

 

On both servers, running an NSLOOKUP on both the IP and PC Name show the correct info:

 

nslookup servername

Server: FQDN

Address: w.x.y.x

 

nslookup w.x.y.z

Server: FQDN

Address: w.x.y.z

 

It's got me stumped. I've restarted both servers, flushed the DNS caches, I can PING bother servers from each other etc., no firewall, WINRM is running and enabled, -no avail.

 

Any help would

be great.

 

Cheers,

Paul.

[RowlandoGloom]

So then I try to enter-psession on the existing server to itself and it gives the same: "..server name cannot be resolved"

 

So it can't resolve it's own name through server manager or PS - but can via NSLOOKUP. Cleared the DNS cache etc.

 

I tried to add a role to itself and it gave an error suggesting it can't modify the registry settings because "the serv....."

 

Grrrr.

[IanT]

https://social.technet.microsoft.com/Forums/windowsserver/en-US/1deba106-16fc-4247-9d6b-d10fca4d9e9f/target-name-resolution-error

[RowlandoGloom]

Already tried that Ian,

 

As I say, everything resolves via DNS, both NETBIOS name, FQDN and IP all resolve each other properly.