Any assistance would be greatly appreciated on this...it's a critical issue! Hub and spoke topology, one of my locations (spoke) has recently broken into multiple subnets (VLANs - WIFI, Servers, etc...). DNS for the laptops does not resolve the local domain name correctly. This is an issue because we're using the domain name to map DFS shares. Originally, the DNS went round robin (would give a new IP every time we did a ipconfig /flushdns and tried to ping again). I disabled round robin, enabled netmask ordering (was on by default). The laptop subnet is 10.224.3.0/24, server subnet is 10.224.1.0/24. Other sites use 10.223.0.0 addresses. Shouldn't the server always prefer itself due to subnet mask specificity? In the DNS MMC, there are two servers listed before the local server for the (same as parent folder) listing (domain name) - the DNS server always returns one of these addresses to the clients which is unreachable from this site. Forgive the sketchy details...but I've been banging my head on this one for hours and would REALLY appreciate some assistance - thanks!

If your clients are assigned the DNS servers, which are not reachable, so that is your problem. You have to modify DHCP server at that location to provide DNS servers (option 006 in dhcp) which is reachable from clients.With kind regards Krystian Zieja http://www.projectnenvision.com Follow me on twitter My Blog

Krystian - The clients are assigned to the correct DNS server. The problem is that when we ping the domain name (ssbc.local) the DNS server returns every single domain controller in the domain, most of which are not at the site of the client. The local domain controller is third in the list and never gets reached. I hope I'm making sense here...

Krystian - The clients are assigned to the correct DNS server. The problem is that when we ping the domain name (ssbc.local) the DNS server returns every single domain controller in the domain, most of which are not at the site of the client. The local domain controller is third in the list and never gets reached. I hope I'm making sense here... Hello, what you see is expected and nothing to worry about. Ping command is not site aware and just choose an available DC. Best regards Meinolf Weber Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

Unfortunately, the issues bleed into DFS access as well. If the domain resolves to the incorrect DC, I am not able to connect to any DFS shares using \\ssbc.local paths. I've also tested by creating a local hosts file mapping ssbc.local to the correct IP and everything works perfectly (but obviously I don't want to put a static host file on 100 laptops).

Hello, DFS is site aware and therefore AD sites and services must be configured correct, so please check with the following articles: http://technet.microsoft.com/en-us/library/cc730868.aspx http://technet.microsoft.com/en-us/library/cc755768(WS.10).aspxBest regards Meinolf Weber Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

AD Sites and Services is configured correctly. Do you know of anything else it could be?

Hello, please post an unedited ipconfig /all from a problem client the DC/DNS server and the DFS server that should be used.Best regards Meinolf Weber Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

Here's the output from the client laptop: C:\Windows\system32>ipconfig /all Windows IP Configuration Host Name . . . . . . . . . . . . : US2002LP003 Primary Dns Suffix . . . . . . . : SSBCUSA.local Node Type . . . . . . . . . . . . : Hybrid IP Routing Enabled. . . . . . . . : No WINS Proxy Enabled. . . . . . . . : No DNS Suffix Search List. . . . . . : SSBCUSA.local Wireless LAN adapter Wireless Network Connection: Connection-specific DNS Suffix . : SSBCUSA.local Description . . . . . . . . . . . : DW1501 Wireless-N WLAN Half-Mini Card Physical Address. . . . . . . . . : 1C-65-9D-58-95-66 DHCP Enabled. . . . . . . . . . . : Yes Autoconfiguration Enabled . . . . : Yes Link-local IPv6 Address . . . . . : fe80::11a6:4c28:1b15:ee4f%14(Preferred) IPv4 Address. . . . . . . . . . . : 10.224.4.17(Preferred) Subnet Mask . . . . . . . . . . . : 255.255.255.0 Lease Obtained. . . . . . . . . . : Thursday, February 03, 2011 9:26:50 AM Lease Expires . . . . . . . . . . : Friday, February 04, 2011 9:36:21 PM Default Gateway . . . . . . . . . : 10.224.4.254 DHCP Server . . . . . . . . . . . : 10.224.1.250 DHCPv6 IAID . . . . . . . . . . . : 359723425 DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-14-1A-F1-71-F0-4D-A2-87-47-58 DNS Servers . . . . . . . . . . . : 10.224.1.250 10.223.0.10 NetBIOS over Tcpip. . . . . . . . : Enabled Ethernet adapter Bluetooth Network Connection: Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Bluetooth Device (Personal Area Network) Physical Address. . . . . . . . . : 5C-AC-4C-E6-82-BE DHCP Enabled. . . . . . . . . . . : Yes Autoconfiguration Enabled . . . . : Yes Tunnel adapter isatap.SSBCUSA.local: Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : SSBCUSA.local 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 Tunnel adapter isatap.{7B1BC4E9-4E43-47D8-92B5-C5F23CBFDE09}: 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 The DC/DFS server is one and the same: C:\Users\Jeremy>ipconfig /all Windows IP Configuration Host Name . . . . . . . . . . . . : BBUS2002-01 Primary Dns Suffix . . . . . . . : SSBCUSA.local Node Type . . . . . . . . . . . . : Hybrid IP Routing Enabled. . . . . . . . : No WINS Proxy Enabled. . . . . . . . : No DNS Suffix Search List. . . . . . : SSBCUSA.local Ethernet adapter SD LAN: Connection-specific DNS Suffix . : Description . . . . . . . . . . . : BASP Virtual Adapter Physical Address. . . . . . . . . : 84-2B-2B-5D-83-29 DHCP Enabled. . . . . . . . . . . : No Autoconfiguration Enabled . . . . : Yes Link-local IPv6 Address . . . . . : fe80::452e:9e2c:9fd0:d9f3%16(Preferred) IPv4 Address. . . . . . . . . . . : 10.224.1.250(Preferred) Subnet Mask . . . . . . . . . . . : 255.255.254.0 Default Gateway . . . . . . . . . : 10.224.1.254 DHCPv6 IAID . . . . . . . . . . . : 394537771 DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-14-53-CF-20-84-2B-2B-5D-83-2A DNS Servers . . . . . . . . . . . : 10.224.1.250 10.223.0.10 NetBIOS over Tcpip. . . . . . . . : Enabled 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\Jeremy>

Hello, if you run "echo %logonserver%" on the client does it show the site DNS server? If not try removing the secondary DNS and run nltest /sc_reset:dcname and check if this helps.Best regards Meinolf Weber Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

I'm guessing that variable is not processed by W7 correctly? Output: C:\Windows\system32>echo %logonserver% %logonserver% C:\Windows\system32>

I'm guessing that variable is not processed by W7 correctly? Output: C:\Windows\system32>echo %logonserver% %logonserver% C:\Windows\system32> Hello, have no problem on Windows 7 with the command for the computer "Win7": C:\Users\username>echo %logonserver% \\WIN7Best regards Meinolf Weber Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

First of all before name resolution can happen the client computer must be able to reach the dns servers by ip address pinging. Then you can configure the clients to become dns clients by adding the ip address of the dsn server to the tcp/ip properties. If the tcp/ip configuration are issued by a dhcp server to need to specify the correct dns addresses. 1. Try to ping the dns server by ip address. 2. If is not reachable, check you routing table setting.mgassama

As with all things Microsoft, this problem has magically disappeared (I'm sure to reappear in a few weeks) after a slurry of reboots. Meinolf - thanks for your efforts on this!

Malamin...I appreciate your effort in assisting me to ping my DNS server.

Hi, Glad to hear your problem has been solved, thank you for your feedback.Technology changes life