Target name resolution error

Target name resolution error

This forum has migrated to Microsoft Q&A. Visit Microsoft Q&A to post new questions.

Answered by:

Question

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.

Answers

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.

• Proposed as answer by Aiden_Cao Thursday, September 20, 2012 6:41 AM
• Marked as answer by MedicalS Microsoft contingent staff Thursday, September 20, 2012 7:22 AM

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

• Proposed as answer by Aiden_Cao Thursday, September 20, 2012 6:41 AM
• Marked as answer by MedicalS Microsoft contingent staff Thursday, September 20, 2012 7:22 AM

Bob Lin, MVP, MCSE & CNE Networking, Internet, Routing, VPN Troubleshooting on

How to Setup Windows, Network, VPN & Remote Access on

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.

• Proposed as answer by Aiden_Cao Thursday, September 20, 2012 6:41 AM
• Marked as answer by MedicalS Microsoft contingent staff Thursday, September 20, 2012 7:22 AM

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

• Proposed as answer by Aiden_Cao Thursday, September 20, 2012 6:41 AM
• Marked as answer by MedicalS Microsoft contingent staff 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.

Mark R Bracking

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

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.

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.

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)

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?

— «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)

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:

and the 2nd DC has also 2 DNS:

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.

Источник

Target name resolution error

This forum has migrated to Microsoft Q&A. Visit Microsoft Q&A to post new questions.

Answered by:

Question

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.

Answers

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.

• Proposed as answer by Aiden_Cao Thursday, September 20, 2012 6:41 AM
• Marked as answer by MedicalS Microsoft contingent staff Thursday, September 20, 2012 7:22 AM

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

• Proposed as answer by Aiden_Cao Thursday, September 20, 2012 6:41 AM
• Marked as answer by MedicalS Microsoft contingent staff Thursday, September 20, 2012 7:22 AM

Bob Lin, MVP, MCSE & CNE Networking, Internet, Routing, VPN Troubleshooting on

How to Setup Windows, Network, VPN & Remote Access on

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.

• Proposed as answer by Aiden_Cao Thursday, September 20, 2012 6:41 AM
• Marked as answer by MedicalS Microsoft contingent staff Thursday, September 20, 2012 7:22 AM

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

• Proposed as answer by Aiden_Cao Thursday, September 20, 2012 6:41 AM
• Marked as answer by MedicalS Microsoft contingent staff 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.

Mark R Bracking

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

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.

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.

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)

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?

— «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)

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:

and the 2nd DC has also 2 DNS:

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.

Источник

Windows Server 2012 Thread, Server Manager — Target Name Resolution Error in Technical; Morning,

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

I’m trying to add a …

Target name resolution error в windows server

This forum has migrated to Microsoft Q&A. Visit Microsoft Q&A to post new questions.

Answered by:

Question

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.

Answers

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.

Bob Lin, MVP, MCSE & CNE Networking, Internet, Routing, VPN Troubleshooting on

How to Setup Windows, Network, VPN & Remote Access on

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.

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.

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.

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

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

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.

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.

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)

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

— «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)

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:

and the 2nd DC has also 2 DNS:

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.

Источник

Проблемы с разрешением имен и подключением на сервере маршрутов и удаленного доступа, который также выполняет DNS или WINS

В этой статье предоставляется решение проблем с разрешением и подключением имен на сервере маршрутов и удаленного доступа, который также выполняет DNS или WINS.

Применяется к: Windows Server 2012 R2, Windows Server 2016
Исходный номер КБ: 292822

Симптомы

Компьютер под управлением Microsoft Windows 2000 Server или Microsoft Windows Server 2003 может иметь проблемы с подключением, если сервер настроен следующим образом:

После подключения удаленного компьютера к серверу маршрутов и удаленного доступа с помощью подключения к виртуальной частной сети (VPN) может возникать один или несколько следующих симптомов:

Если на сервере маршрутиза и удаленного доступа также работает сервер Microsoft Internet Security and Acceleration (ISA) Server 2000, вы не можете просматривать веб-страницы с клиентских компьютеров в локальной сети независимо от того, настроены ли компьютеры на использование веб-прокси или клиент межсетевого экрана (Майкрософт). Например, «Страница не может отображаться» может отображаться в веб-браузере с сообщением об ошибке «не удается найти сервер или DNS».

Если на сервере маршрутиза и удаленного доступа работает ISA Server 2000, а пользователь на клиентской компьютере выбирает обновление теперь в диалоговом окне Параметры брандмауэра, пользователь получает следующее сообщение об ошибке:

Сервер не отвечает, когда клиент запрашивает обновление.
Возможные причины:
-Сервер не является сервером ISA.
-Сервер не съехался.

При попытке с помощью сервера маршрутизов и удаленного доступа с локального компьютера с помощью имени NetBIOS сервера или полностью квалифицированного доменного имени (FQDN) компьютер пытается цитировать неправильный IP-адрес.

Если сервер маршрутивки и удаленного доступа является магистралным браузером для сети, вы не можете просматривать список компьютеров в сетевом соседстве или в местах моей сети.

Вы не можете подключиться кhttp:// server_name/myconsole
веб-сайт на компьютере Small Business Server 2000.

На сервере маршрутов и удаленного доступа вы получаете сообщение о событии, аналогичное следующему:

Вы получаете сообщения об ошибках при попытке открыть файлы или сетевые диски на сервер маршрутивке и удаленном доступе.

Если сервер маршрутирования и удаленного доступа также является контроллером домена, при попытке войти в сеть вы получите сообщения об ошибках.

Если сервер маршрутирования и удаленного доступа является контроллером домена, вы получаете сообщения об ошибках при попытке открыть общие файлы или сетевые диски на любой общий ресурс в сети. Например, компьютеры с microsoft Windows 2000 Professional или Microsoft Windows XP Professional получают сообщение об ошибке, аналогичное следующему:

Нет серверов Logon, доступных для обслуживания вашего запроса logon

Эта проблема обычно затрагивает компьютеры с сервером малого бизнеса, так как эта версия Windows Server часто является единственным сервером в сети. Однако эта проблема может затронуть Windows 2000-сервер или любой сервер на Windows Server 2003 и сервер удаленного доступа, работающий с DNS или службой WINS.

Причина

Когда удаленный компьютер подключается к серверу маршрутного и удаленного доступа с помощью набора или VPN-подключения, сервер создает адаптер протокола точки к точке для связи с удаленным компьютером. Затем сервер может зарегистрировать IP-адрес этого адаптера PPP в DNS или базе данных WINS.

Когда сервер маршрутивки и удаленного доступа регистрирует IP-адрес своего адаптера PPP в DNS или WINS, при попытке подключения к серверу на локальных компьютерах могут возникнуть ошибки. Вы получаете эти ошибки, так как серверы DNS или WINS могут возвращать IP-адрес адаптеров PPP на компьютеры, запрашивающий DNS или WINS для IP-адреса сервера. Затем компьютеры пытаются подключиться к IP-адресу адаптеров PPP. Из-за того, что локальные компьютеры не могут достичь адаптеров PPP, подключение не удается.

Решение

В этот раздел, описание метода или задачи включены действия, содержащие указания по изменению параметров реестра. Однако неправильное изменение параметров реестра может привести к возникновению серьезных проблем. Поэтому следует в точности выполнять приведенные инструкции. Для дополнительной защиты создайте резервную копию реестра, прежде чем редактировать его. Так вы сможете восстановить реестр, если возникнет проблема. Дополнительные сведения см. в дополнительных сведениях о том, как создать и восстановить реестр в Windows

Чтобы устранить эту проблему, настройте сервер маршрутов и удаленного доступа, чтобы он не зарегистрировал IP-адрес адаптеров PPP в DNS или базе данных WINS. Для этого выполните следующие действия:

Настройка сервера маршрутов и удаленного доступа для публикации только IP-адреса локального сетевого адаптера в DNS

Выполните действия в этом разделе только в том случае, если на сервере маршрутики и удаленного доступа работает служба DNS. Если на сервере не работает служба DNS, перейдите к серверу Настройка маршрутного и удаленного доступа, чтобы зарегистрировать только IP-адрес локального сетевого адаптера в разделе WINS.

Добавление значений реестра PublishAddresses и RegisterDnsARecords для служб DNS и Netlogon

Выберите Начните, выберите Выполнить, введите regedit, а затем выберите ОК.

Найдите и выберите следующий подкай реестра: HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesDNSParameters

В меню Редактирование указать значение New, а затем выберите строковую ценность, чтобы добавить следующее значение реестра:

Имя значения: PublishAddresses
Тип данных: REG_SZ
Данные о значении: IP-адрес локального сетевого адаптера сервера. Если необходимо указать несколько IP-адресов, разделять адреса с пробелами.

Найдите и выберите следующий подкай реестра: HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesNetlogonParameters

В меню Редактирование указать значение New, а затем выберите значение DWORD, чтобы добавить следующее значение реестра:

Имя значения: RegisterDnsARecords
Тип данных: REG_DWORD
Данные значения: 0

Закрой редактор реестра, а затем перезапустите службы DNS и Netlogon. Чтобы перезапустить службу, выберите Пуск, указать на программы или все программы, указать на административные средства, а затем выбрать службы. В консоли Services щелкните правой кнопкой мыши службу и выберите перезапуск.

Добавление записей A в DNS

Выполните эти действия только в том случае, если сервер маршрутивки и удаленного доступа является контроллером домена.

Выберите Начните, указать на программы или все программы, указать на административные средства, а затем выберите DNS.

В консоли DNS раздвигаем объект сервера, расширяем папку Зоны смотра вперед, а затем выберите папку для локального домена.

В меню Действия выберите Новый хост.

В текстовом поле IP-адреса введите IP-адрес локального сетевого адаптера сервера.

Оставьте поле Имя пустым, выберите Создать связанную запись PTR, а затем выберите Add Host.

Когда вы получаете «(так же, как родительская папка) не является допустимым имя хоста. Вы уверены, что хотите добавить эту запись? сообщение, выберите Да.

Если сервер является глобальным сервером каталогов, перейдите к шагу 7. Если сервер не является глобальным сервером каталогов, вам не нужно выполнить действия с 7 по 11. Чтобы определить, является ли сервер глобальным сервером каталогов, выполните следующие действия:

В папке Зоны forward Lookup в консоли DNS разложите папку для локального домена, разложите папку MSDCS и выберите папку GC.

В меню Действия выберите Новый хост.

В поле IP-адрес введите IP-адрес локального сетевого адаптера сервера.

Оставьте поле Имя пустым, выберите Создать связанную запись PTR, а затем выберите Add Host.

Когда вы получаете «(так же, как родительская папка) не является допустимым имя хоста. Вы уверены, что хотите добавить эту запись? сообщение, выберите Да.

Настройка сервера маршрутов и удаленного доступа для регистрации только IP-адреса локального сетевого адаптера в WINS

Выполните действия в этом разделе только в том случае, если на сервере маршрутов и удаленного доступа работает служба WINS. Кроме того, если на сервере работает сервер малого бизнеса 2000 SP1, сервер малого бизнеса 2000 SP1a или Windows Small Business Server 2003, вам не нужно завершать действия в этом разделе. По умолчанию эти версии сервера Windows настраиваются, чтобы предотвратить регистрацию IP-адреса адаптеров PPP в базе данных WINS.

Добавление значения реестра DisableNetbiosOverTcpip для службы маршрутизации и удаленного доступа

Значение реестра DisableNetbiosOverTcpip отключает протокол NetBIOS по TCP/IP (NetBT) для подключений к удаленному доступу. Таким образом, сервер не будет регистрировать адаптер PPP в базе данных WINS. Знайте, что при добавлении этого значения клиенты удаленного доступа не могут просматривать локализованную сеть через «Мои сетевые места» или «Сетевое соседство». Иногда это также может привести к неудаче подключения к удаленному доступу на компьютерах с более старыми версиями Windows. Например, подключение к удаленному доступу может быть неудачным на 98 компьютерах Microsoft Windows и на компьютерах microsoft Windows NT 4.0 Workstation. Альтернативу использованию реестра DisableNetbiosOverTcpip см. в разделе Обходное решение.

Если сервер работает Windows 2000 Server SP2 или более ранней версии, необходимо обновить сервер с помощью SP3 или SP4, чтобы значение реестра DisableNetbiosOverTcpip работало. Если не обновить сервер, служба маршрутинга и удаленного доступа не будет использовать это значение реестра, и проблема не будет устранена.

Выберите Начните, выберите Выполнить, введите regedit, а затем выберите ОК.

Найдите и выберите следующий подкай реестра: HKEY_LOCAL_MACHINESystemCurrentControlSetServicesRemoteAccessParametersIP

В меню Редактирование указать значение New, а затем выберите значение DWORD, чтобы добавить следующее значение реестра:

Имя значения: DisableNetbiosOverTcpip
Тип данных: REG_DWORD
Данные значения: 1

Закрой редактор реестра, а затем перезапустите службу маршрутов и удаленного доступа. Чтобы перезапустить службу, выберите Пуск, указать на программы или все программы, указать на административные средства, а затем выбрать службы. В консоли Services щелкните правой кнопкой мыши службу и выберите перезапуск.

Очистка базы данных WINS

Обходной путь

В качестве обхода этой проблемы можно настроить подключения удаленного доступа к статическому пулу IP-адресов, который находится на другой подсети IP, чем на локальных компьютерах. В этом случае локальные компьютеры не будут пытаться подключиться к адаптеру PPP, если он регистрируется в DNS или WINS, так как адаптер PPP находится на другой подсети IP.

Чтобы указать статичный пул адресов в консоли маршрутизировать и удаленный доступ, щелкните правой кнопкой мыши ServerName, выберите Свойства, выберите вкладку IP, выберите пул статических адресов, а затем выберите Добавить. Добавьте диапазон, который не использует ту же подсеть IP, что и локальные компьютеры. Например, если локальные компьютеры используют подсеть 10.0.0.0, добавьте статический пул, использующий подсеть 172.168.0.0. Если на сервере маршрутизации и удаленного доступа работает ISA Server 2000, необходимо добавить эту подсеть в локализованную адресную таблицу. Этот сценарий наиболее распространен в small Business Server 2000.

Источник

Target name resolution error в windows server

This forum has migrated to Microsoft Q&A. Visit Microsoft Q&A to post new questions.

Answered by:

Question

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.

Answers

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.

Bob Lin, MVP, MCSE & CNE Networking, Internet, Routing, VPN Troubleshooting on

How to Setup Windows, Network, VPN & Remote Access on

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.

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.

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.

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

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

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.

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.

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)

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

— «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)

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:

and the 2nd DC has also 2 DNS:

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.

Источник