Clients can't access servers bij dns name witouth suffix
Hello, We have some server that are unable to connect to other servers by dns name (server01). However when we try to connect bij server name with dns suffix we are able to connect (server01.domain.lan). This problem occurs ones in a while. When we restart the server the problem is solved. However we can't find out why this is happening. Does anyone have any idea where we have to look to find this problem? The problem occurs from a Terminal Server Windows Server 2008R2 to two print servers, one Windows Server 2003 and one Windows Server 2008R2. We are able to connect to these server from other servers and the terminal server is able to connect to other servers. All the servers are in the same domain. Remco
September 23rd, 2010 8:40am

Make sure the servers are only pointing to internal DNS servers which are usually just Domain Controllers in their TCP\IP properties.
Free Windows Admin Tool Kit Click here and download it now
September 23rd, 2010 8:49am

The DNS servers are two domain controllers. Both servers have the same dns records en replications works fine. So this does not seem to be the problem. Any other ideas?
September 23rd, 2010 8:55am

So, they have the DCs in their TCP\IP properties as primary and secondary DNS server, right? I would update the drivers and firmware for the NIC.
Free Windows Admin Tool Kit Click here and download it now
September 23rd, 2010 9:20am

Read this. http://networkadminkb.com/kb/Knowledge%20Base/DNS/How%20the%20Client%20DNS%20Settings%20work%20to%20resolve%20DNS%20names.aspx Check those settings against the ones on the computer. Basically, the DNS Suffix Search List (as show in ipconfig /all) needs to list domain.ian. If it doesn't then server01.domain.lan won't resolve.
September 23rd, 2010 10:01pm

We've updated the drivers and we are monitoren if the problems still occurs. Because it occurs only ones in a while I can not yet tellf if this solves the problem.
Free Windows Admin Tool Kit Click here and download it now
September 27th, 2010 4:33am

Problem has come back today. Driver updates doesn't solve the problem.
October 4th, 2010 7:33am

Post ipconfig /all
Free Windows Admin Tool Kit Click here and download it now
October 5th, 2010 3:48am

Windows IP-configuratie Hostnaam . . . . . . . . . . . . : OETSA5 Primair DNS-achtervoegsel . . . . : office-extra.lan Knooppunttype . . . . . . . . . . : hybride IP-routering ingeschakeld . . . . : nee WINS-proxy ingeschakeld . . . . . : nee DNS-achtervoegselzoeklijst. . . . : office-extra.lan Ethernet-adapter voor LAN-verbinding 3: Verbindingsspec. DNS-achtervoegsel: Beschrijving. . . . . . . . . . . : Microsoft Virtual Machine Bus Network Ada pter #3 Fysiek adres. . . . . . . . . . . : 00-15-5D-01-32-0E DHCP ingeschakeld . . . . . . . . : nee Autom. configuratie ingeschakeld : ja IPv4-adres. . . . . . . . . . . . : 172.24.1.60(voorkeur) Subnetmasker. . . . . . . . . . . : 255.255.255.240 Standaardgateway. . . . . . . . . : 172.24.1.49 DNS-servers . . . . . . . . . . . : 172.24.1.3 172.24.1.19 NetBIOS via TCPIP . . . . . . . . : ingeschakeld Tunnel-adapter voor isatap.{2D05FA58-73B1-4D11-B39B-D22880613EC2}: Mediumstatus. . . . . . . . . . . : medium ontkoppeld Verbindingsspec. DNS-achtervoegsel: Beschrijving. . . . . . . . . . . : Microsoft ISATAP Adapter Fysiek adres. . . . . . . . . . . : 00-00-00-00-00-00-00-E0 DHCP ingeschakeld . . . . . . . . : nee Autom. configuratie ingeschakeld : ja Tunnel-adapter voor Teredo Tunneling Pseudo-Interface: Mediumstatus. . . . . . . . . . . : medium ontkoppeld Verbindingsspec. DNS-achtervoegsel: Beschrijving. . . . . . . . . . . : Teredo Tunneling Pseudo-Interface Fysiek adres. . . . . . . . . . . : 00-00-00-00-00-00-00-E0 DHCP ingeschakeld . . . . . . . . : nee Autom. configuratie ingeschakeld : ja
October 5th, 2010 5:41am

Is this an IP address from within the host for a virtual machine?
Free Windows Admin Tool Kit Click here and download it now
October 5th, 2010 8:21am

It is the IP adres of the vitual machine itself.
October 5th, 2010 8:42am

Go into Network Binding check to make sure this network card is listed first.
Free Windows Admin Tool Kit Click here and download it now
October 5th, 2010 9:44am

This is also done. We herstarted a lot of services and everything worked again. When the problem reoccures we will restart them one by one. List of services: Netwokr Store Interface Services Network List Service Network Location Awareness Network Conenctions Netlogon Workstation IP Helper DNS Client DHCP-client
October 14th, 2010 7:44am

Problem found, it's the workstation service. Now I just need the solution.
Free Windows Admin Tool Kit Click here and download it now
November 9th, 2010 5:12am

Type nslookup from command line. Does the server respond with 'timeout' before giving you the name and ip? type your computer name in the nslookup window. Does the server return your full name and IP?New York Tech
November 9th, 2010 7:11am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics