I have a Windows 7 PC (not a member of any AD domain) at home and then I opened a VPN to the company server (Windows SBS 2011). The VPN is set to not Use default gateway on remote network. The VPN has IP 192.168.1.12, gateway of blank in IPCONFIG but 192.168.1.16 in ROUTE PRINT, and DNS 192.168.1.8 (the SBS server). The network destination 192.168.1.0 has a metric of 26 whereas my primary connection has a metric of 25. My problem is, on this PC, sometimes I can resolve corporate intranet machine names and sometimes I can't. When it's not working, I ran DIG @192.168.1.8 (192.168.1.8 is the SBS server), I can resolve all intranet names. When a PC has more than one network connection, what is/are the DNS server(s) being queried and in what order? Thanks.

Hi, For a multihomed computer, the resolver queries the DNS servers in the following order: The resolver sends the query to the first server on the preferred adapter's list of DNS servers and waits for one second for a response. If the resolver does not receive a response from the first server within one second, it sends the query to the first DNS servers on all adapters that are still under consideration and waits two seconds for a response. If the resolver does not receive a response from any server within two seconds, the resolver sends the query to all DNS servers on all adapters that are still under consideration and waits another two seconds for a response. If the resolver still does not receive a response from any server, it sends the query to all DNS servers on all adapters that are still under consideration and waits four seconds for a response. If it still does not receive a response from any server, the resolver sends the query to all DNS servers on all adapters that are still under consideration and waits eight seconds for a response. Name Resolution http://technet.microsoft.com/en-us/library/cc961411.aspx Brent Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. ”

Thanks. That was an informative article. According to it, I shouldn't be facing my problem. But I still do. D:\>ping rossini.mydomain.local Ping request could not find host rossini.mydomain.local. Please check the name and try again. D:\>ping rossini.mydomain.local. Ping request could not find host rossini.mydomain.local.. Please check the name and try again. D:\>dig rossini.mydomain.local @192.168.1.8 ; <<>> DiG 9.3.2 <<>> rossini.mydomain.local @192.168.1.8 ; (1 server found) ;; global options: printcmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 1251 ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0 ;; QUESTION SECTION: ;rossini.mydomain.local. IN A ;; ANSWER SECTION: rossini.mydomain.local. 3600 IN A 192.168.1.8 ;; Query time: 457 msec ;; SERVER: 192.168.1.8#53(192.168.1.8) ;; WHEN: Wed May 25 20:07:07 2011 ;; MSG SIZE rcvd: 54 D:\>ipconfig /all Windows IP Configuration Host Name . . . . . . . . . . . . : BEETHOVEN Primary Dns Suffix . . . . . . . : Node Type . . . . . . . . . . . . : Broadcast IP Routing Enabled. . . . . . . . : No WINS Proxy Enabled. . . . . . . . : No DNS Suffix Search List. . . . . . : gateway.2wire.net PPP adapter VPN bach.mydomain.net: Connection-specific DNS Suffix . : Description . . . . . . . . . . . : VPN bach.mydomain.net Physical Address. . . . . . . . . : DHCP Enabled. . . . . . . . . . . : No Autoconfiguration Enabled . . . . : Yes IPv4 Address. . . . . . . . . . . : 192.168.1.14(Preferred) Subnet Mask . . . . . . . . . . . : 255.255.255.255 Default Gateway . . . . . . . . . : DNS Servers . . . . . . . . . . . : 192.168.1.8 NetBIOS over Tcpip. . . . . . . . : Enabled Wireless LAN adapter Wireless Network Connection: Connection-specific DNS Suffix . : gateway.2wire.net Description . . . . . . . . . . . : Atheros AR9285 802.11b/g/n WiFi Adapter Physical Address. . . . . . . . . : 70-F1-A1-3F-9C-E7 DHCP Enabled. . . . . . . . . . . : Yes Autoconfiguration Enabled . . . . : Yes Link-local IPv6 Address . . . . . : fe80::b5d9:9b2c:c5d0:ee07%12(Preferred) IPv4 Address. . . . . . . . . . . : 192.168.88.64(Preferred) Subnet Mask . . . . . . . . . . . : 255.255.255.0 Lease Obtained. . . . . . . . . . : Wednesday, May 25, 2011 17:42:02 Lease Expires . . . . . . . . . . : Thursday, May 26, 2011 17:42:03 Default Gateway . . . . . . . . . : 192.168.88.1 DHCP Server . . . . . . . . . . . : 192.168.88.1 DHCPv6 IAID . . . . . . . . . . . : 225505697 DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-13-64-17-30-D8-D3-85-E9-58-0D DNS Servers . . . . . . . . . . . : 192.168.88.1 NetBIOS over Tcpip. . . . . . . . : Enabled

Hi, Do you enable the user default Gateway on Remote Network setting? Please post an output of "route print" from the affected computer. To enable the Use Default Gateway on Remote Network setting in the VPN dial-up connection item on the client computer: Double-click My Computer, and then click the Network and Dial-up Connections link. Right-click the VPN connection that you want to change, and then click Properties. Click the Networking tab, click Internet Protocol (TCP/IP) in the Components checked are used by this connection list, and then click Properties. Click Advanced, and then click to clear the Use default gateway on remote network check box. Click OK, click OK, and then click OK BrentPlease remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Thanks. No, I do not Use Default Gateway on Remote Network on the VPN as I don't want all my Internet traffic to go via the VPN unnecessarily. The problem is that this phenomenon is intermittent. Today it is working ok. Anyway: IPv4 Route Table =========================================================================== Active Routes: Network Destination Netmask Gateway Interface Metric 0.0.0.0 0.0.0.0 192.168.88.1 192.168.88.64 25 119.234.10.49 255.255.255.255 192.168.88.1 192.168.88.64 26 127.0.0.0 255.0.0.0 On-link 127.0.0.1 306 127.0.0.1 255.255.255.255 On-link 127.0.0.1 306 127.255.255.255 255.255.255.255 On-link 127.0.0.1 306 192.168.1.0 255.255.255.0 192.168.1.16 192.168.1.15 26 192.168.1.15 255.255.255.255 On-link 192.168.1.15 281 192.168.88.0 255.255.255.0 On-link 192.168.88.64 281 192.168.88.64 255.255.255.255 On-link 192.168.88.64 281 192.168.88.255 255.255.255.255 On-link 192.168.88.64 281 224.0.0.0 240.0.0.0 On-link 127.0.0.1 306 224.0.0.0 240.0.0.0 On-link 192.168.88.64 281 255.255.255.255 255.255.255.255 On-link 127.0.0.1 306 255.255.255.255 255.255.255.255 On-link 192.168.88.64 281 255.255.255.255 255.255.255.255 On-link 192.168.1.15 281 ===========================================================================