In Servers --- all servers I get a target name resolution error

 configuration refresh failed with the following error: the metadata failed to be retrieved from the server with the following error: the WinRM client cannot process the request because the server name cannot be resolved

Any Ideas I tried to add a VM to the servers in the server manager.

It could be DNS issue. Any errors when running nslookup?

Bob is correct, based on the error message it is a DNS issue. Any news on this issue?

If you are getting the error for all servers, the problem is likely related to the DNS server settings on the NIC. Check these to make sure they are correct.

-Greg

• Proposed as answer by Aiden_CaoMicrosoft community contributor, Moderator Thursday, September 20, 2012 6:41 AM
• Marked as answer by Shaon ShanMicrosoft contingent staff, Moderator Thursday, September 20, 2012 7:22 AM

Hi, 

Try with the IP address...if you are  able to connect... then the issue with DNS !!!

• Proposed as answer by Aiden_CaoMicrosoft community contributor, Moderator Thursday, September 20, 2012 6:41 AM
• Marked as answer by Shaon ShanMicrosoft contingent staff, Moderator Thursday, September 20, 2012 7:22 AM

same here- if using AD, "target name resolution error"

if added using IP/DNS, "Kerberos target resolution error"

same AD domain, same DNS domain, can resolve each other by nslookup, find each other in 'add servers' by AD and DNS/IP, etc.

Refresh fails after adding, too. both come up as online and have remote management installed.

All fixes say to ensure DNS is working. It is - now what? Nothing in documentation...

I had the same problem with a build I did. To resolve the problem I reconfigured the network interface cards (NIC) so that each NIC could communication with the correct network. I'm fairly certain that the network interface cards are not configured correctly.

Hi All,

I faced the same issue after renaming the Win2012 4 node cluster.

Solution is : Just open Server Manager Console, click All Server and Right click and Remove the Previous Cluster Name Entry and clear task from Flag.

You need to do it on all cluster nodes.

I have the same issue

2 node cluster with 8 nic cards

2 x iSCSI private IP

2 x Live Migration -Cluster comms Teamed private IP

3 x Hyper-V teamed no ip settings for hyper-v guests

1 x MGT Lan port with dns and lan access

I can ping the cluster name the servers name and IP address from each server and all okay. So it does not look like a DNS issue

On my windows 8 pc I can add all the server and they show okay. So it only displays the error on both nodes of the cluster

the strange thing is that I can right click the server and computer management and it opens the computer management of the server it can't resolve

• Edited by Sparky_001 Wednesday, September 18, 2013 11:54 AM

Hi Mr. Kirpal,

I have created 2 VMs on my windows 8 Hyper-V. On first VM, I have installed windows server 2012 full GUI (server 1) and on second VM windows server 2012 core (server 2) and both virtual machines are in workgroup. I configured static IP on both machines and they are pinging fine to each other. I want to configure and manage server 2 (core) from server 1 (GUI) with the help of server manager but when I add server 2, server 1's server manager throws an error with error message "DNS name resolution error"

Let me know if you need any other information.

Please give me a solution.

Thanks, AKHILESH

• Edited by Akhilesh Kandpal Friday, October 04, 2013 6:10 PM

I solved my experience with this error by removing the server from server manager and adding it back. This seems to have resolved DNS issues related to the computer name change I performed on my target server.

-James

If you are on your Active Directory domain controller with integrated DNS, check if your primary DNS server is 127.0.0.1 in your network adapter settings. 

In your DNS settings, you should setup an external DNS server as forwarder. (for instance, 8.8.8.8 for google DNS server)

Hi everyone,

To be honest, im just a new learner in Window Server 2012. Apart of that, currently I'm working in Server Manager for connecting two servers namely primary and secondary. But the problem arises when I'm need to configure the two servers, I unable to find the secondary server when dealing in primary server and vice versa for clustering .

The error came out is "Kerberos Target Resolution Error". How to solve this kind of problem? 



I already done;

- "Manage As" that i required to insert the username and password to another server
- "RPC" to remote another server
- disable firewall

but its still unsuccessful.. 



At the All Server of the Server manager, it unable to detect IP Address of the secondary server as depicted above. Is it the cause of an error?

I also had this error. Solved by removing server and adding it using DNS query (not AD)

Regards,

Gediminas

hi guys. i am having the same error. what do you mean there is a dns problem? how do i resulve it?

hi guys. i am having the same error. what do you mean there is a dns problem? how do i resulve it?

When you add a Server, it has a name.

But to use that name, it needs to go through a Dynamic Name Server, to lookup the proper address.

A computer only understands 01010101010011111010000111010101.....

So a name like: MyServerToBeManaged, although you understand the name, the computer will start doing... nothing!  Because it needs this name to be translated into bits, zeros and ones.

To make even this more visuable to a human reader, you get IP Addresses in the sense of

172.22.x.x for a class B network on the Netmask 255.255.0.0 or if you like class A you get 192.168.x.x on the 255.255.255.0

But although the computer can translate Hex into binary automatically, it can't with the names.

Thus you need a server, a dynamic name server, to translate the name for the computer.

I have an easy setup with only 2 AD DC, so I have one as first DNS for the 2nd and the 2nd has the first DNS pointing the first.

i.e. DC 172.22.56.2, router at 172.22.56.1

The other computer on the other subnet is at 172.22.57.2 and it's router at 172.22.57.1

They are bind by oVPN to a class B network.

To make sure they see each other, the first DC has 2 DNS:

172.22.57.2

172.22.56.1

and the 2nd DC has also 2 DNS:

172.22.56.2

172.22.57.1

So both first look for their partner for DNS queries *had to do that to make sure the local.domain.com would be resolved properly, because if you have the routers DNS first, your DC start looking for each other in online DNS resolvers for the WWW, which you don't want them to!

You first point them to each other, and first if THEY can't resolve it, they look online..

This setup is very bad practice if you have more then 2 DC though, but it's an easy setup for home users.

Kerberos target resolution error:

Right-click the target server in the Servers tile of the All Servers page, and then click Manage As to provide explicit credentials