- Remove From My Forums
-
Question
-
The DNS server could not open socket for address 192.168.0.2.
Verify that this is a valid IP address for the server computer. If it is NOT valid use the Interfaces dialog under Server Properties in the DNS Manager to remove it from the list of IP interfaces. Then stop and restart the DNS server. (If this was
the only IP interface on this machine and the DNS server may not have started as a result of this error. In that case remove the DNSParameters ListenAddress value in the services section of the registry and restart.)
If this is a valid IP address for this machine, make sure that no other application (e.g. another DNS server) is running that would attempt to use the DNS port.
For more information, see «DNS server log reference» in the online Help.
Event Xml:
<Event xmlns=»http://schemas.microsoft.com/win/2004/08/events/event»>
<System>
<Provider Name=»Microsoft-Windows-DNS-Server-Service» Guid=»{71A551F5-C893-4849-886B-B5EC8502641E}» EventSourceName=»DNS» />
<EventID Qualifiers=»49152″>408</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime=»2011-09-13T11:16:30.000000000Z» />
<EventRecordID>264</EventRecordID>
<Correlation />
<Execution ProcessID=»0″ ThreadID=»0″ />
<Channel>DNS Server</Channel>
<Computer>DCSRV.parkergroup.com</Computer>
<Security />
</System>
<EventData Name=»DNS_EVENT_OPEN_SOCKET_FOR_ADDRESS»>
<Data Name=»param1″>192.168.0.2</Data>
<Binary>
</Binary>
</EventData>
</Event>
Arvind
Answers
-
Hello,
please proceed like mentioned.
Use DNS manager and remove the IP address 192.168.0.2 from the list of interfaces that are listening to DNS clients. Once done, restart DNS.
This
posting is provided «AS IS» with no warranties or guarantees , and confers no rights.Microsoft Student
Partner 2010 / 2011
Microsoft Certified Professional
Microsoft Certified Systems Administrator:
Security
Microsoft Certified Systems Engineer:
Security
Microsoft Certified Technology Specialist:
Windows Server 2008 Active Directory, Configuration
Microsoft Certified Technology Specialist:
Windows Server 2008 Network Infrastructure, Configuration
Microsoft Certified Technology Specialist:
Windows Server 2008 Applications Infrastructure, Configuration
Microsoft Certified Technology Specialist:
Windows 7, Configuring
Microsoft Certified IT Professional: Enterprise
Administrator
Microsoft Certified IT Professional: Server Administrator-
Marked as answer by
Tuesday, September 20, 2011 2:16 AM
-
Marked as answer by
-
Hi Arvind,
Thank you for your post.
As MrX posted, DNS server use invalid IP address to listen DNS traffic. Please refer to
Event ID 408 article to resolve your issue.
If there are more inquiries on this issue, please feel free to let us know.
Regards,
Rick Tan-
Marked as answer by
Rick Tan
Tuesday, September 20, 2011 2:16 AM
-
Marked as answer by
In this tutorial, which is a special case, I will explain how to solve the 404, 407 and 408 error that can occur on a DNS server with Windows Server under the following conditions:
- Being on a virtual machine
- Being on a Hyper-V host
- Have configured NIC teaming, which is configured as an external virtual switch with management enabled.
If you are in this particular configuration, it is possible that on your DNS server, you encounter the error 404, 407 and 408 at the level of the DNS server:
After several searches on the Internet and on the Microsoft doc, a resolution of this error is proposed here:https://docs.microsoft.com/fr-fr/troubleshoot/windows-server/networking/events-407-408-in-dns-server-event-log
Not fitting in this case, so I continued my research, having another DNS server running on another hyper-v host and this one having no problem, so I decided to look on the side of the Hyper-V host that hosts the DNS server that has this error.
Almost at the same time, on the Hyper-V host, an error is logged: MsLbfoSysEvtProvider (16945), which indicates a MAC address conflict.
After some research, this is a known problem at Microsoft and occurs when using network card teaming, which is used as a virtual switch WITH management enabled.
In a PowerShell command prompt, use the following cmdlet:
Get-NetAdapter | sort MacAddress
As you can see the MAC address of the “active” card is used on:
- The Virtual Switch (Teaming)
- The virtual network adapter (Ethernet (VM)) that is attached to the host.
Now that the observation is made, this problem must be solved, for this there are several solutions:
If the Hyper-V host is under Windows Server 2012R2 and +: it is possible to modify the MAC address of the Teaming cardhttps://social.technet.microsoft.com/wiki/contents/articles/31357.hyper-v-troubleshooting-mac-address-conflict-event-16945.aspx
If the Hyper-V host is running Windows Server 2016 or newer, configure teaming with a SET switch : https://rdr-it.com/hyper-v-commutateur-virtuel-avec-agregat-de-port-switch-embedded-teaming-set/
Есть сервер с Windows Server 2008R2 в роли контроллера домена с DNS-сервером.
Сетевая конфигурация выглядит так:
IP-адрес: 172.17.1.3
Маска сети: 255.255.255.0
Шлюз: 172.17.1.1 (роутер)
В логах все время появляются следующие ошибки:
Код ошибки: 407
DNS-серверу не удалось связать сокет для работы по протоколу UDP с 172.17.1.3. В данных события содержится код ошибки. Перезапустите DNS-сервер или перезагрузите компьютер.
Код ошибки: 408
DNS-серверу не удалось открыть сокет для адреса «172.17.1.3».
Убедитесь, что данный адрес является допустимым IP-адресом компьютера сервера. Если он не является допустимым, используйте диалог «Интерфейсы» на вкладке «Свойства сервера» диспетчера DNS для удаления его из списка IP-интерфейсов. После этого остановите и снова запустите DNS-сервер. (Если этот IP-интерфейс единственный на компьютере, DNS-сервер может не запуститься по причине описанной ошибки. В этому случае удалите значение DNSParameters ListenAddress в разделе служб реестра и перезапустите сервер.)
Если указанный IP-адрес является допустимым для данного компьютера, убедитесь, что не запущены другие приложения (например, другой DNS-сервер), которые могут использовать DNS-порт.
Код ошибки: 404
DNS-серверу не удалось связать сокет для работы по протоколу TCP с адресом 172.17.1.3. В данных события содержится код ошибки. IP-адрес 0.0.0.0 может означать допустимый «любой адрес», в котором все настроенные IP-адреса для компьютера доступны для использования.
Перезапустите DNS-сервер или перезагрузите компьютер.
Другие компьютеры, подключенные к домену, и с настройками DNS 172.17.1.3, могут открывать страницы Интернет (хотя, может из-за того, что в качестве шлюза указан 172.17.1.1?)
Собственно вопрос: страшны ли ошибки, и если да, то как лечить?
Или мне не надо указывать в сетевых настройках компьютера-сервера с установленным DNS-сервером в качестве DNS адрес 172.17.1.3, а вписать только петлевой (127.0.01) ?
Skip to content
Situation: The client keeps having a DNS problem. Sometimes, users have a problem to access some LAN resources.
Troubleshooting: We find there is Event error relate to DNS.
Log Name: DNS Server
Event ID: 408
Description:
The DNS server could not open socket for address 10.0.0.84.
Verify that this is a valid IP address for the server computer. If it is NOT valid use the Interfaces dialog under Server Properties in the DNS Manager to remove it from the list of IP interfaces. Then stop and restart the DNS server. (If this was the only IP interface on this machine and the DNS server may not have started as a result of this error. In that case remove the DNSParameters ListenAddress value in the services section of the registry and restart.)
If this is a valid IP address for this machine, make sure that no other application (e.g. another DNS server) is running that would attempt to use the DNS port.
In checking DNS, we find one DC uses two IP addresses. One of IP address belongs to another DC. In the IPv4 Property>Advanced>IP Settings, we find there are two IP addresses. We assume they want to enter two DCs’ IP addresses but put them in wrong place. Removing another IP address fixes the problem.
Bob Lin
Bob Lin, Chicagotech-MVP, MCSE & CNE
Data recovery, Windows OS Recovery, Networking, and Computer Troubleshooting on
http://www.ChicagoTech.net
How to Install and Configure Windows, VMware, Virtualization and Cisco on
http://www.HowToNetworking.com
View all posts by Bob Lin