DNS request times out on client PC's but not on server(s)

One server with two hyper-v's.

DNS requests gets handled without problems on the server.

Client PC's I get this:

C:\Users\User>nslookup google.com
DNS request timed out.
    timeout was 2 seconds.
Server:  UnKnown
Address:  192.168.1.x

DNS request timed out.
    timeout was 2 seconds.
DNS request timed out.
    timeout was 2 seconds.
DNS request timed out.
    timeout was 2 seconds.
DNS request timed out.
    timeout was 2 seconds.

Open in new window


I've checked that the forwarders are indeed working - and seeing as it works on the servers this indicate some sort of other problem.

dcdiag /test:dns gives:

Directory Server Diagnosis

Performing initial setup:

   Trying to find home server...

   Home Server = SERVER01

   * Identified AD Forest. 
   Done gathering initial info.

Doing initial required tests
   
   Testing server: Default-First-Site-Name\SERVER01

      Starting test: Connectivity

         ......................... SERVER01 passed test Connectivity

Doing primary tests
   
   Testing server: Default-First-Site-Name\SERVER01
   
      Starting test: DNS

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

         ......................... SERVER01 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 : int
   
   Running enterprise tests on : int.DOMAIN.COM

      Starting test: DNS

         ......................... int.DOMAIN.COM passed test DNS

Open in new window


("DOMAIN.COM" is changed by me to anonymize the client.)

Full dcdiag is all ok except:

      Starting test: KccEvent

         A warning event occurred.  EventID: 0x800004C0

            Time Generated: 10/01/2013   10:41:52

            Event String:

            Internal event: An LDAP client connection was closed because of an error. 

         A warning event occurred.  EventID: 0x800004C0

            Time Generated: 10/01/2013   10:41:52

            Event String:

            Internal event: An LDAP client connection was closed because of an error. 

         A warning event occurred.  EventID: 0x800004C0

            Time Generated: 10/01/2013   10:42:22

            Event String:

            Internal event: An LDAP client connection was closed because of an error. 

         A warning event occurred.  EventID: 0x800004C0

            Time Generated: 10/01/2013   10:44:52

            Event String:

            Internal event: An LDAP client connection was closed because of an error. 

         ......................... SERVER01 passed test KccEvent

Open in new window


Not sure if that is related.
LVL 3
tsnironeAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

MAS (MVE)EE Solution Guide - Technical Dept HeadCommented:
type "nslookup" then
type "microsoft.com"

and  post the result here
0
tsnironeAuthor Commented:
hey abbasiftt,

Now for some reason it can resolve normally. I really do not like problems like this that comes and goes.

Here's the result from what you wanted me to do:

C:\Users\User>nslookup
Default Server:  UnKnown
Address:  192.168.1.9

> microsoft.com
Server:  UnKnown
Address:  192.168.1.9

Non-authoritative answer:
Name:    microsoft.com
Addresses:  65.55.58.201
          64.4.11.37

>

Open in new window



And here is the result that would previously time out:

C:\Users\User>nslookup google.com
Server:  UnKnown
Address:  192.168.1.9

Non-authoritative answer:
Name:    google.com
Addresses:  2a00:1450:400f:802::100e
          217.168.95.35
          217.168.95.26
          217.168.95.31
          217.168.95.27
          217.168.95.20
          217.168.95.16
          217.168.95.38
          217.168.95.46
          217.168.95.57
          217.168.95.49
          217.168.95.37
          217.168.95.24
          217.168.95.42
          217.168.95.59
          217.168.95.48
          217.168.95.53

Open in new window

0
MAS (MVE)EE Solution Guide - Technical Dept HeadCommented:
Did you try pinging to one of the IP?
If not pinging try to tracethe same IP
0
Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

tsnironeAuthor Commented:
What IP adress do you want me to try and ping?

Are we sure they reply on ping? (seems that the microsoft ones does not!)
0
MAS (MVE)EE Solution Guide - Technical Dept HeadCommented:
Any of the IP let say 64.4.11.37
You are right it cannot be pinged

Try telneting port 80/443. command below
telnet 64.4.11.37 80
telnet 64.4.11.37 443
0
tsnironeAuthor Commented:
I tried from my home-network and it blackens out the cmd windows and I get the blinking cursor in the top left corner. The same happens for both port 80 and 443.

The same thing happens on my client PCs.
0
tsnironeAuthor Commented:
Further information.

Allthough the client pc's now seem to resolve we still are having problems with all the mfp scanners at this client. They are all unable to send scans using email. Seems they have problems resolving the smtp adress.
0
tsnironeAuthor Commented:
Further information.

Server03 has Exchange installed. The "Queue Viewer" is filled with outgoing emails with error:

451.4.4.0 Primary target IP address responded with: "421.4.2.1 Unable to connect." Attempted failover to alternate host, but that did not succeed. Either there are no alternate hosts, or delivery failed to all alternate hosts.

Please help!!!
0
MAS (MVE)EE Solution Guide - Technical Dept HeadCommented:
Try telneting port 80/4telnet these also please from the client PCs. command below
telnet microsoft.com 80
telnet microsoft.com 443


Did you check your antivirus?

Please tick "Use the external DNS lookup settings on the transport server"
and add your external DNS address in
Serverconfig->HubTransport->right servername->properties-->External DNS Lookups
-->Use- these DNS servers
Add external DNS addresses here
0
tsnironeAuthor Commented:
Yes I did try telnet:

I tried from my home-network and it blackens out the cmd windows and I get the blinking cursor in the top left corner. The same happens for both port 80 and 443.

The same thing happens on my client PCs.

What should I check on the antivirus????

There is no antivirus on the servers nor on the mfc printer/scanners I mentioned.

On the client its Microsoft Security Essentials....but as I said nslookup now works on them.

Seems to me that there is a problem with the dns on the server01 even though it is not clearly reporting any error. I tried to restart DNS service on server01 and it restarted just fine without any entries in the logs.
0
tsnironeAuthor Commented:
I added the external dns-servers, but the queue does not get any shorter!! ://

Added external dns
I also rebooted server03 (exchange) but didnt help.
0
MAS (MVE)EE Solution Guide - Technical Dept HeadCommented:
Can you give remote access to a PC in your network?
if yes
Please install Teamviewer and send me the TV id and password to my personal email
you can see my email in my profile
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
tsnironeAuthor Commented:
This is a production environment and I would rather not give access unless its REALLY needed, (I hope you understand) could you tell me what you would be doing and let me do it instead?

Further information; here is the lan/virtual adapter setup on the three servers:


server01 - iron/dc/dns/dhcp etc
server02 - virtual - remote desktop
server03 - virtual - exchange and sql
screenshot-server01.png
screenshot-server02.png
screenshot-server03.png
0
tsnironeAuthor Commented:
This is one of these situations where one problem leads to another to another etc.

Using tv abbasiftt figured out that an old fw rule on our fw had been activated as a result of rebooting the fw yesterday and the reboot was due to the timeouts for dns.

Now, the exchange queue is emptied out and the dns timouts seems to have vanished so I'm closing this one rewarding the points to abbasiftt.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2008

From novice to tech pro — start learning today.