Dns ошибка 407

  • Remove From My Forums

  • Question

  • Hi,

    I have windows server 2008r2 running Active directory and DNS for active directory.

    I keep getting dns error 404 and 407. I only have one network adapter.

    If you could help that would be great and thanks in advance

    Here is my ipconfig

    Windows IP Configuration

       Host Name . . . . . . . . . . . . : Carters-Server
       Primary Dns Suffix  . . . . . . . : cjcdsb.com
       Node Type . . . . . . . . . . . . : Hybrid
       IP Routing Enabled. . . . . . . . : No
       WINS Proxy Enabled. . . . . . . . : No
       DNS Suffix Search List. . . . . . : cjcdsb.com
                                           cgocable.net

    Ethernet adapter Local Area Connection:

       Connection-specific DNS Suffix  . : cgocable.net
       Description . . . . . . . . . . . : Realtek PCIe GBE Family Controller
       Physical Address. . . . . . . . . : 94-DE-80-C9-72-0F
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes
       IPv6 Address. . . . . . . . . . . : 2001:1970:46c1:3201:f42f:ec8:9488:e1f7(Preferred)
       Link-local IPv6 Address . . . . . : fe80::f42f:ec8:9488:e1f7%10(Preferred)
       IPv4 Address. . . . . . . . . . . : 192.168.0.2(Preferred)
       Subnet Mask . . . . . . . . . . . : 255.255.255.0
       Default Gateway . . . . . . . . . : fe80::cad3:a3ff:fe69:90c7%10
                                           192.168.0.1
       DHCPv6 IAID . . . . . . . . . . . : 244637312
       DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1A-39-F1-97-94-DE-80-C9-72-0F
       DNS Servers . . . . . . . . . . . : 2001:1970:c000::53
                                           192.168.0.2
                                           127.0.0.1
       NetBIOS over Tcpip. . . . . . . . : Disabled
       Connection-specific DNS Suffix Search List :
                                           cgocable.net
                                           cjcdsb.com

    Tunnel adapter isatap.{E8EDE964-1B44-4F5F-9DF3-92A102B7321A}:

       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Microsoft ISATAP Adapter
       Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes

    Tunnel adapter Teredo Tunneling Pseudo-Interface:

       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
       Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes

    • Edited by

      Sunday, May 18, 2014 1:58 AM
      Mistake

Answers

  • You can try unchecking IPv6 in network connection properties, reboot and check it again.

    Regards, Dave Patrick ….
    Microsoft Certified Professional
    Microsoft MVP [Windows]

    Disclaimer: This posting is provided «AS IS» with no warranties or guarantees , and confers no rights.

    • Edited by
      Dave PatrickMVP
      Wednesday, May 21, 2014 12:36 AM
    • Proposed as answer by
      Susie Long
      Tuesday, May 27, 2014 3:03 AM
    • Marked as answer by
      Susie Long
      Tuesday, June 10, 2014 2:02 AM

Источник
  • 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 DNS\Parameters\ 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

  • 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

Источник

Есть сервер с 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-сервер может не запуститься по причине описанной ошибки. В этому случае удалите значение DNS\Parameters\ 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) ?

Источник

Ever since I installed this new server I get some reoccurring errors. Within the DNS portion I get the above event ID’s. None of which I am smart enough to track down and fix. Does anyone know where to make the changes? Of course the link to Microsoft goes to a «page cannot be found»

407 — The DNS server could not bind a User Datagram Protocol (UDP) socket to 10.0.0.3. The event data is the error code. Restart the DNS server or reboot your computer.

then

408 — The DNS server could not open socket for address 10.0.0.3.
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 DNS\Parameters\ 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.

then

404 — The DNS server could not bind a Transmission Control Protocol (TCP) socket to address 10.0.0.3. The event data is the error code. An IP address of 0.0.0.0 can indicate a valid «any address» configuration in which all configured IP addresses on the computer are available for use.
Restart the DNS server or reboot the computer.

Then they repeat a couple of times  and end with ID 4013

4013 — The DNS server is waiting for Active Directory Domain Services (AD DS) to signal that the initial synchronization of the directory has been completed. The DNS server service cannot start until the initial synchronization is complete because critical DNS data might not yet be replicated onto this domain controller. If events in the AD DS event log indicate that there is a problem with DNS name resolution, consider adding the IP address of another DNS server for this domain to the DNS server list in the Internet Protocol properties of this computer. This event will be logged every two minutes until AD DS has signaled that the initial synchronization has successfully completed.

Источник

I’m trying to setup AD/DNS on my new server running Windows 2012 R2. I’ve installed the roles, configured a static ip, made forward and reverse zones, etc. In the events list I see 408, 407, and 404 errors. When running dcdiag it fails on the connectivity test:

Testing server: Default-First-Site-Name\DCName
   Starting test: Connectivity
      The host <numbers>._msdcs.domain.foo could not be resolved to an IP address. Check
      the DNS server, DHCP, server name, etc.
      Got error while checking LDAP and RPC connectivity. Please check your firewall settings.
      ......................... DCName failed test Connectivity

I’m concerned that perhaps the ip address is not configured correctly should the static ip and «DNS server» be the same?

Could it perhaps have something to do with the fact this is running as a virtual machine isolated from the internet?

EDIT

Event Text:
407 The DNS server could not bind a User Datagram Protocol (UDP) socket to <server ip>. The event data is the error code. Restart the DNS server or reboot your computer.

408 

The DNS server could not open socket for address <server ip>. 
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 DNS\Parameters\ 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.

404 

The DNS server could not bind a Transmission Control Protocol (TCP) socket to address <server ip>.  The event data is the error code.  An IP address of 0.0.0.0 can indicate a valid "any address" configuration in which all configured IP addresses on the computer are available for use. 
Restart the DNS server or reboot the computer.

Источник

Понравилась статья? Поделить с друзьями:
  • Dns ошибка 404
  • Dns ошибка 403
  • Dns ошибка 4015
  • Dns probe started ошибка
  • Dns имя не существует код ошибки 0х0000232b