Socket 10051 / DNS

Hello everybody,

I am getting this error of "socket: 10051" because after a migration of DNS. I am getting a problem when I open a webpage first time, server not found(404).


portqry.jpg
rmarcandierAsked:
Who is Participating?
 
rmarcandierAuthor Commented:
Hello Chris-Dent:

After a few days making a lot of tests in my DNS Server to try to resolve this problem I found the solution.

During the migration process for the new server I put 2 cables in my Dell R310 Server (LAN1 e LAN2). Because of it my DNS was crazy. I just removed that cable (LAN2), restarted the server.

Now everything is working perfectly. Thank you for all your help.
0
 
Chris DentPowerShell DeveloperCommented:
It's possible you're being directed to the wrong web-server, of course. Check:

nslookup yourwebserver

And / Or:

ping yourwebserver

If the IP is correct you can rule out DNS completely and you must start looking at your web server and why it might not be returning the page you expect.

It should also be noted that while some DNS servers listen on TCP/53 it should not be assumed to be available, and is not actually required for standard queries (only zone transfers and overflow). DNS servers typically listen for requests on UDP/53 and that's the one you need to work. NSLookup will do as a test for that.

Chris
0
 
rmarcandierAuthor Commented:
Hello Chris-Dent

Thank you very much.

Could you take a look and see if everything is ok?

Best Regards
Renato


pingxxx333.jpg
pingxxx444.jpg
0
Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

 
rmarcandierAuthor Commented:
Hello Chris-Dent

I check the command nslookup and I think its not working.
nslookup.jpg
0
 
Chris DentPowerShell DeveloperCommented:
Are you logged onto 192.168.0.3 there? You're asking whatever you're logged onto to resolve the name and that doesn't seem to be working.

If it's supposed to, is the DNS service even running (depending on your platform)?

Chris
0
 
rmarcandierAuthor Commented:
I got the problem

I performed the test on my dns server (192.168.0.3)

dcdiag /test:dns




Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

C:\Users\Administrator.MULTUK>dcdiag /test:dns

Directory Server Diagnosis

Performing initial setup:
   Trying to find home server...
   Home Server = THESTOVE
   * Identified AD Forest.
   Done gathering initial info.

Doing initial required tests

   Testing server: Default-First-Site-Name\THESTOVE
      Starting test: Connectivity
         ......................... THESTOVE passed test Connectivity

Doing primary tests

   Testing server: Default-First-Site-Name\THESTOVE

      Starting test: DNS

         DNS Tests are running and not hung. Please wait a few minutes...
         ......................... THESTOVE passed test DNS

   Running partition tests on : ForestDnsZones

   Running partition tests on : DomainDnsZones

   Running partition tests on : Schema

   Running partition tests on : Configuration

   Running partition tests on : MULTUK

   Running enterprise tests on : MULTUK.INTERNAL
      Starting test: DNS
         Test results for domain controllers:

            DC: THESTOVE.MULTUK.INTERNAL
            Domain: MULTUK.INTERNAL


               TEST: Basic (Basc)
                  Warning: Adapter 78:2B:CB:68:9D:43 has dynamic IP address
                  (can be a misconfiguration)

               TEST: Dynamic update (Dyn)
                  Warning: Failed to delete the test record dcdiag-test-record i
n zone MULTUK.INTERNAL

         Summary of test results for DNS servers used by the above domain
         controllers:

            DNS server: 128.8.10.90 (d.root-servers.net.)
               1 test failure on this DNS server
               PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DN
S server 128.8.10.90
            DNS server: 192.5.5.241 (f.root-servers.net.)
               1 test failure on this DNS server
               PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DN
S server 192.5.5.241
            DNS server: 2001:500:1::803f:235 (h.root-servers.net.)
               1 test failure on this DNS server
               PTR record query for the 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.
0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa failed on the DNS server 2001:500:1::803f:235

            DNS server: 2001:500:2d::d (d.root-servers.net.)
               1 test failure on this DNS server
               PTR record query for the 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.
0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa failed on the DNS server 2001:500:2d::d

            DNS server: 2001:500:2f::f (f.root-servers.net.)
               1 test failure on this DNS server
               PTR record query for the 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.
0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa failed on the DNS server 2001:500:2f::f

            DNS server: 2001:500:3::42 (l.root-servers.net.)
               1 test failure on this DNS server
               PTR record query for the 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.
0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa failed on the DNS server 2001:500:3::42

            DNS server: 2001:503:ba3e::2:30 (a.root-servers.net.)
               1 test failure on this DNS server
               PTR record query for the 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.
0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa failed on the DNS server 2001:503:ba3e::2:30

            DNS server: 2001:503:c27::2:30 (j.root-servers.net.)
               1 test failure on this DNS server
               PTR record query for the 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.
0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa failed on the DNS server 2001:503:c27::2:30

            DNS server: 2001:7fd::1 (k.root-servers.net.)
               1 test failure on this DNS server
               PTR record query for the 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.
0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa failed on the DNS server 2001:7fd::1

            DNS server: 2001:7fe::53 (i.root-servers.net.)
               1 test failure on this DNS server
               PTR record query for the 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.
0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa failed on the DNS server 2001:7fe::53

            DNS server: 2001:dc3::35 (m.root-servers.net.)
               1 test failure on this DNS server
               PTR record query for the 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.
0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa failed on the DNS server 2001:dc3::35

            DNS server: 202.12.27.33 (m.root-servers.net.)
               1 test failure on this DNS server
               PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DN
S server 202.12.27.33
               THESTOVE                     PASS WARN PASS PASS WARN PASS n/a
         ......................... MULTUK.INTERNAL passed test DNS


My previous DNS was 192.168.0.4 but its not anymore. I dont know why it still appearing for me as DNS Server (192.168.0.4) ..
Do you know where should I clean it up? DNS or DHCP

Thank you


0
 
Chris DentPowerShell DeveloperCommented:
DHCP, if that's what you use to set servers for your client.

Chris
0
 
rmarcandierAuthor Commented:
Thank you chris,

In my DHCP I have just my NEW DNS... do you how where should I check if still have some reference to 192.168.0.4 ?? Or should I restart my DHCP service... ?
DHCP.jpg
0
 
Chris DentPowerShell DeveloperCommented:
Please run:

ipconfig /all

If that references your old DNS server note the DHCP Server entry as well. Make sure that's the same server as you're looking at above.

And make sure the DNS servers aren't statically configured in your network config.

Chris
0
 
rmarcandierAuthor Commented:
Hey Chris,

Ipconfig /all (on my machine)

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

C:\Users\renatom>ipconfig /all

Windows IP Configuration

   Host Name . . . . . . . . . . . . : renatom
   Primary Dns Suffix  . . . . . . . : MULTUK.INTERNAL
   Node Type . . . . . . . . . . . . : Hybrid
   IP Routing Enabled. . . . . . . . : No
   WINS Proxy Enabled. . . . . . . . : No
   DNS Suffix Search List. . . . . . : MULTUK.INTERNAL

Ethernet adapter Local Area Connection:

   Connection-specific DNS Suffix  . : MULTUK.INTERNAL
   Description . . . . . . . . . . . : Realtek PCIe GBE Family Controller
   Physical Address. . . . . . . . . : 00-21-9B-19-5E-5A
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
   Link-local IPv6 Address . . . . . : fe80::b43c:a600:eba7:eab2%10(Preferred)
   IPv4 Address. . . . . . . . . . . : 192.168.0.37(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Lease Obtained. . . . . . . . . . : 05 January 2012 11:46:31
   Lease Expires . . . . . . . . . . : 13 January 2012 11:46:31
   Default Gateway . . . . . . . . . : 192.168.0.1
   DHCP Server . . . . . . . . . . . : 192.168.0.3
   DHCPv6 IAID . . . . . . . . . . . : 234889627
   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-16-49-62-C9-00-21-9B-19-5E-5A

   DNS Servers . . . . . . . . . . . : 192.168.0.3
   NetBIOS over Tcpip. . . . . . . . : Enabled

Tunnel adapter isatap.MULTUK.INTERNAL:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . : MULTUK.INTERNAL
   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

C:\Users\renatom>


--------------------------------------------------------------------------------------------------------------------------

ipconfig /all (on my DNS Server)

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

C:\Users\Administrator.MULTUK>ipconfig /all

Windows IP Configuration

   Host Name . . . . . . . . . . . . : THESTOVE
   Primary Dns Suffix  . . . . . . . : MULTUK.INTERNAL
   Node Type . . . . . . . . . . . . : Hybrid
   IP Routing Enabled. . . . . . . . : No
   WINS Proxy Enabled. . . . . . . . : No
   DNS Suffix Search List. . . . . . : MULTUK.INTERNAL

Ethernet adapter Local Area Connection 3:

   Connection-specific DNS Suffix  . : MULTUK.INTERNAL
   Description . . . . . . . . . . . : Broadcom BCM5716C NetXtreme II GigE (NDIS
 VBD Client) #2
   Physical Address. . . . . . . . . : 78-2B-CB-68-9D-43
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
   Link-local IPv6 Address . . . . . : fe80::a80a:8718:596e:177d%15(Preferred)
   Default Gateway . . . . . . . . . : 192.168.0.1
   DHCPv6 IAID . . . . . . . . . . . : 376974283
   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-16-86-46-CB-00-1B-21-BD-72-16

   DNS Servers . . . . . . . . . . . : 192.168.0.3
   NetBIOS over Tcpip. . . . . . . . : Enabled

Ethernet adapter Local Area Connection 2:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Broadcom BCM5716C NetXtreme II GigE (NDIS
 VBD Client)
   Physical Address. . . . . . . . . : 78-2B-CB-68-9D-42
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
   Link-local IPv6 Address . . . . . : fe80::3dea:59eb:69f9:8b44%13(Preferred)
   IPv4 Address. . . . . . . . . . . : 192.168.0.3(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . : 192.168.0.1
   DHCPv6 IAID . . . . . . . . . . . : 309865419
   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-16-86-46-CB-00-1B-21-BD-72-16

   DNS Servers . . . . . . . . . . . : ::1
                                       192.168.0.3
                                       127.0.0.1
   NetBIOS over Tcpip. . . . . . . . : Enabled

Ethernet adapter Local Area Connection:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Intel(R) PRO/1000 PT Server Adapter
   Physical Address. . . . . . . . . : 00-1B-21-BD-72-16
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes

Tunnel adapter isatap.{64AE012F-43A5-4EB8-B846-BE342BB90A9B}:

   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 isatap.MULTUK.INTERNAL:

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

Tunnel adapter isatap.{31094AAC-2996-44DB-9F48-ADE14F731DED}:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Microsoft ISATAP Adapter #3
   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

C:\Users\Administrator.MULTUK>
0
 
rmarcandierAuthor Commented:
Do you see something wrong?
0
 
Chris DentPowerShell DeveloperCommented:
Not really. I think we need to start again. I reckon we need to know these:

Web server name or URL:
Web server IP address:
Result of "nslookup Web-Server-Name-Or-URL", e.g. "nslookup www.yoursite.com":

The problem is that your computer cannot access the web-site? And that's returning the 404 error? I assume other web pages are fine?

Chris
0
 
rmarcandierAuthor Commented:
Here is my original problem:

http://www.experts-exchange.com/Networking/Protocols/DNS/Q_27516672.html?cid=239#a37370691

I am with this problem in my network, if you open 5 pages, or 10 pages 1 of these pages will not find the server or if find the HTML don't appear normal you need to reload the page.
Example, if I try one page for the first time (I made a migration during xmas time) www.winamp.com
firt appear server not found, if you reload (f5) it appears normal....

I dont know where should I fix it :(
0
 
Chris DentPowerShell DeveloperCommented:
That sounds like slow DNS resolution rather than broken as such.

On your DNS server, do you have Forwarders configured? If so, who / what do you forward to?

Chris
0
 
rmarcandierAuthor Commented:
Hey Chris-Dent

Thank you for your answer.

I didn't configured forwarders, how should I do it? do you have some sample?

Thank you very much
DNS.jpg
0
 
Chris DentPowerShell DeveloperCommented:
Lets try it then, you don't need them, but if things aren't working so well it may help.

Initially I suggest you use Google's DNS servers, those are:

8.8.8.8
8.8.4.4

To add them, select your Server in the DNS console. Right click and open Properties. Select the Forwarders tab and add the two IP addresses there.

Chris
0
 
rmarcandierAuthor Commented:
Thank you

I did it. Lets make some tests :)
forwarders.jpg
0
 
rmarcandierAuthor Commented:
Chris. do you know some tests that I can run  to see if my DNS is working good?
0
 
Chris DentPowerShell DeveloperCommented:
Run this on your DNS server:

dnscmd /clearcache

Then this on your client:

ipconfig /flushdns

And go surfing :) It sounds like it was pretty intermittent in the first place, if that is the case, time will tell.

Chris
0
 
rmarcandierAuthor Commented:
Hey Chris,

Thank you for all your help, but I am still getting the same problem... when I open a webpage for the first time always is being showed (server is not found)... if I press f5.. f5... the page appears normally...

Do you think I should uninstall DNS service from my windows 2008 server r2, and install it again?!

0
 
Chris DentPowerShell DeveloperCommented:
No, that won't help. I don't think there's anything wrong with DNS itself.

Can you tell me a bit about your network?

Presumably you have something like:

Your Computer -> Some Switches -> Your DNS Server -> Some Firewall -> The Internet

Chris
0
 
rmarcandierAuthor Commented:
Hello Chris

I have, my computer, some switches (netgear), all my computers and server are connected in this switches. one firewall (daytreck - virgo 3300) and 3 links of internet connected in this firewall
I am using windows 2008 server r2 - totally up to date - hardware new (Dell PowerEdge R310 Rack Server)
internet:
1 - virgin - dedicated 20 mb
2 - O2 - dynamic 10 mb
3 - be - dynamic 10 mb

Its my network
0
 
Chris DentPowerShell DeveloperCommented:
Which of those three connections is the DNS server using? And have you tried it on any of the others (if it is possible to do so)?

Chris
0
 
rmarcandierAuthor Commented:
I just configured it to 192.168.0.1 (my gateway /firewall) this device that makes the balance between my 3 links.
0
 
Chris DentPowerShell DeveloperCommented:
Hmm okay. So what happens if one of those connections is the cause of this problem?

Chris
0
 
rmarcandierAuthor Commented:
Chis, I check my logs and I saw some errors

Do you think could be the problem?

Take a look for me pls
pic1.jpg
pic2.jpg
pic3.jpg
pic4.jpg
pic5.jpg
0
 
Chris DentPowerShell DeveloperCommented:
Afraid none of those are related.

The behaviour you describe suggests a network-level problem really.

There's one thing we can try, this one depends on your network hardware (for root cause), but we can attempt a work-around on the DNS server:

dnscmd /config /EnableEDnsProbes 0

This will stop your server advertising support for UDP packets larger than 512b, some network devices like to drop DNS packets over that size which can lead to inconsistent name resolution.

It's worth a try anyway, it won't have any negative impact on your system.

Chris
0
 
rmarcandierAuthor Commented:
Great, let me do it :)
0
 
rmarcandierAuthor Commented:
hmmm I am still with this problem... all web site that I open first time dont find.. second time work perfect..
0
 
Chris DentPowerShell DeveloperCommented:
Still slow resolution then.

What's happening is this:

1. Your computer sends a request for the name to your DNS server
2. Your DNS Server gets that, looks to see if the name is cached
3. If the name is not cached, your DNS server sends a request to the Forwarders we configured yesterday
4. Your DNS server sits waiting for a response
5. The client request times out, then your browser fails to display the page
6. Your DNS server finally gets the reply with an IP address for the name
7. You hit refresh
8. Your DNS Server gets that, looks to see if the name is cached
9. The name is cached now, so it tells you that
10. The page loads

So our problem is step 5 and 6. The response should be fast and it is not, that's what I'd hoped to get around by having you set the Forwarder (your server has to do a lot more work without it).

Do any of your ISPs provide you with DNS server IP addresses we can test as Forwarders? Or did your old DNS server have Forwarders configured? They'll be closer to you (in network terms) than Google's DNS servers, or at least they will when you use their connection.

Chris
0
 
rmarcandierAuthor Commented:
Great Chris,

I think I got a new error now.

I am using virgin media and I tryed to put they DNS address:

Primary address: 194.168.4.100
Secondary address: 194.168.8.100
DNS.jpg
0
 
Chris DentPowerShell DeveloperCommented:
Helpful of them, may as well scratch those off as being useless then :)

It's possible they only work when you're using their connection, and that wouldn't be too helpful given the nature of yours.

Chris
0
 
rmarcandierAuthor Commented:
I come back to google 8888 8844

But some times are ok, sometimes red...

Is it normal?!
Google1.jpg
Google2.jpg
0
 
Chris DentPowerShell DeveloperCommented:
They should be consistently green, the red is just another way of it exhibiting the problem you're having.

Is there any way you can test each of those internet connections on its own?

Chris
0
 
rmarcandierAuthor Commented:
yes, I will take the cables off and leave just 1 and make tes
0
 
Chris DentPowerShell DeveloperCommented:
If you can test them in turn. I'm really hoping we only get the problem on one of them...

Chris
0
 
Chris DentPowerShell DeveloperCommented:
I'm glad you found the problem in the end :)

Chris
0
 
rmarcandierAuthor Commented:
I checked the cables and I saw 2 cables connected in the same server.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.