Here is my situation. HQ Office I have Windows 2008 Server. About 10 computers in this office and all on active directory. No issues there. Server IP of 192.168.0.250. Remote Office A. 3 computers. They have a persistent VPN connection to the HQ Office (netgear routers). While I can map drives using \\192.168.0.250, first, I'm unable to map drives using \\server (to shared folders). I cannot ping by FQDN, only IP address. Second, I'm unable to join the remote office A computers to the domain by domain_name or domain_name.local (did not try to join the domain via IP address). Computers in the remote office A have DNS directly to the server (192.168.0.250) (and DNS to the local router too). Should I setup WINS on the server to accept netbios names and such for the VPN'ed computers that are remote? How can I get them to join the domain and be able to browse the network via network places, ping by FQDN and such? Thanks in advance, Steve

Hi Steve, Thanks for posting here. > Computers in the remote office A have DNS directly to the server (192.168.0.250) (and DNS to the local router too). So these three hosts at branch are using this Windows server 2008 domain controller for name resolution now. Is that the preferred DNS server at client? please show us the “ipconfig /all” results from one of these three hosts here . Could we also check if the name resolution functionally is working properly by running the command “nslookup <AD domain name>” and will get the address 192.168.0.250? WINS is optional cos DNS has already been deployed in my environment so please first ensure these hosts are properly running with it . Thanks. Tiger LiTiger Li TechNet Community Support

Hi Steve, Thanks for posting here. > Computers in the remote office A have DNS directly to the server (192.168.0.250) (and DNS to the local router too). So these three hosts at branch are using this Windows server 2008 domain controller for name resolution now. Is that the preferred DNS server at client? please show us the “ipconfig /all” results from one of these three hosts here . Could we also check if the name resolution functionally is working properly by running the command “nslookup <AD domain name>” and will get the address 192.168.0.250? WINS is optional cos DNS has already been deployed in my environment so please first ensure these hosts are properly running with it . Thanks. Tiger LiTiger Li TechNet Community Support

Hi Steve, Thanks for posting here. > Computers in the remote office A have DNS directly to the server (192.168.0.250) (and DNS to the local router too). So these three hosts at branch are using this Windows server 2008 domain controller for name resolution now. Is that the preferred DNS server at client? please show us the “ipconfig /all” results from one of these three hosts here . Could we also check if the name resolution functionally is working properly by running the command “nslookup <AD domain name>” and will get the address 192.168.0.250? WINS is optional cos DNS has already been deployed in my environment so please first ensure these hosts are properly running with it . Thanks. Tiger LiTiger Li TechNet Community Support

Hi Tiger, Thank you for your reply. Here is the information you requested: Microsoft Windows XP [Version 5.1.2600] (C) Copyright 1985-2001 Microsoft Corp. C:\Documents and Settings\mpride>ipconfig /all Windows IP Configuration Host Name . . . . . . . . . . . . : hodconference Primary Dns Suffix . . . . . . . : Node Type . . . . . . . . . . . . : Hybrid IP Routing Enabled. . . . . . . . : No WINS Proxy Enabled. . . . . . . . : No Ethernet adapter Local Area Connection: Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Marvell Yukon 88E8001/8003/8010 PCI Gigabit Ethernet Controller Physical Address. . . . . . . . . : 00-18-F3-43-4B-94 Dhcp Enabled. . . . . . . . . . . : Yes Autoconfiguration Enabled . . . . : Yes IP Address. . . . . . . . . . . . : 192.168.2.2 Subnet Mask . . . . . . . . . . . : 255.255.255.0 Default Gateway . . . . . . . . . : 192.168.2.1 DHCP Server . . . . . . . . . . . : 192.168.2.1 DNS Servers . . . . . . . . . . . : 192.168.2.1 192.168.0.250 192.168.0.1 Primary WINS Server . . . . . . . : 192.168.0.250 Lease Obtained. . . . . . . . . . : Tuesday, January 31, 2012 11:44:35 PM Lease Expires . . . . . . . . . . : Wednesday, February 01, 2012 11:44:35 PM The 192.168.2.1 is their local router The 192.168.0.250 is the domain controller/AD Server at the HQ office The 192.168.0.1 is the router at the HQ Office Those DNS actually do work because of the persistent VPN connection - so they have a connection online 24x7 from the remote office to the HQ office (they need that because their "My Documents" is mapped to a Y Drive, which is actually the user's folder on the server). Here is the nslookup: Microsoft Windows XP [Version 5.1.2600] (C) Copyright 1985-2001 Microsoft Corp. C:\Documents and Settings\mpride>nslookup server.dignity.local *** Can't find server name for address 192.168.2.1: Non-existent domain *** Can't find server name for address 192.168.0.250: Non-existent domain DNS request timed out. timeout was 2 seconds. *** Can't find server name for address 192.168.0.1: Timed out *** Default servers are not available Server: UnKnown Address: 192.168.2.1 *** UnKnown can't find server.dignity.local: Non-existent domain The user's host file also includes an entry of 192.168.0.250 Server.dignity.local Thanks, Steve

Hi Tiger, Thank you for your reply. Here is the information you requested: Microsoft Windows XP [Version 5.1.2600] (C) Copyright 1985-2001 Microsoft Corp. C:\Documents and Settings\mpride>ipconfig /all Windows IP Configuration Host Name . . . . . . . . . . . . : hodconference Primary Dns Suffix . . . . . . . : Node Type . . . . . . . . . . . . : Hybrid IP Routing Enabled. . . . . . . . : No WINS Proxy Enabled. . . . . . . . : No Ethernet adapter Local Area Connection: Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Marvell Yukon 88E8001/8003/8010 PCI Gigabit Ethernet Controller Physical Address. . . . . . . . . : 00-18-F3-43-4B-94 Dhcp Enabled. . . . . . . . . . . : Yes Autoconfiguration Enabled . . . . : Yes IP Address. . . . . . . . . . . . : 192.168.2.2 Subnet Mask . . . . . . . . . . . : 255.255.255.0 Default Gateway . . . . . . . . . : 192.168.2.1 DHCP Server . . . . . . . . . . . : 192.168.2.1 DNS Servers . . . . . . . . . . . : 192.168.2.1 192.168.0.250 192.168.0.1 Primary WINS Server . . . . . . . : 192.168.0.250 Lease Obtained. . . . . . . . . . : Tuesday, January 31, 2012 11:44:35 PM Lease Expires . . . . . . . . . . : Wednesday, February 01, 2012 11:44:35 PM The 192.168.2.1 is their local router The 192.168.0.250 is the domain controller/AD Server at the HQ office The 192.168.0.1 is the router at the HQ Office Those DNS actually do work because of the persistent VPN connection - so they have a connection online 24x7 from the remote office to the HQ office (they need that because their "My Documents" is mapped to a Y Drive, which is actually the user's folder on the server). Here is the nslookup: Microsoft Windows XP [Version 5.1.2600] (C) Copyright 1985-2001 Microsoft Corp. C:\Documents and Settings\mpride>nslookup server.dignity.local *** Can't find server name for address 192.168.2.1: Non-existent domain *** Can't find server name for address 192.168.0.250: Non-existent domain DNS request timed out. timeout was 2 seconds. *** Can't find server name for address 192.168.0.1: Timed out *** Default servers are not available Server: UnKnown Address: 192.168.2.1 *** UnKnown can't find server.dignity.local: Non-existent domain The user's host file also includes an entry of 192.168.0.250 Server.dignity.local Thanks, Steve

Hi Tiger, Thank you for your reply. Here is the information you requested: Microsoft Windows XP [Version 5.1.2600] (C) Copyright 1985-2001 Microsoft Corp. C:\Documents and Settings\mpride>ipconfig /all Windows IP Configuration Host Name . . . . . . . . . . . . : hodconference Primary Dns Suffix . . . . . . . : Node Type . . . . . . . . . . . . : Hybrid IP Routing Enabled. . . . . . . . : No WINS Proxy Enabled. . . . . . . . : No Ethernet adapter Local Area Connection: Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Marvell Yukon 88E8001/8003/8010 PCI Gigabit Ethernet Controller Physical Address. . . . . . . . . : 00-18-F3-43-4B-94 Dhcp Enabled. . . . . . . . . . . : Yes Autoconfiguration Enabled . . . . : Yes IP Address. . . . . . . . . . . . : 192.168.2.2 Subnet Mask . . . . . . . . . . . : 255.255.255.0 Default Gateway . . . . . . . . . : 192.168.2.1 DHCP Server . . . . . . . . . . . : 192.168.2.1 DNS Servers . . . . . . . . . . . : 192.168.2.1 192.168.0.250 192.168.0.1 Primary WINS Server . . . . . . . : 192.168.0.250 Lease Obtained. . . . . . . . . . : Tuesday, January 31, 2012 11:44:35 PM Lease Expires . . . . . . . . . . : Wednesday, February 01, 2012 11:44:35 PM The 192.168.2.1 is their local router The 192.168.0.250 is the domain controller/AD Server at the HQ office The 192.168.0.1 is the router at the HQ Office Those DNS actually do work because of the persistent VPN connection - so they have a connection online 24x7 from the remote office to the HQ office (they need that because their "My Documents" is mapped to a Y Drive, which is actually the user's folder on the server). Here is the nslookup: Microsoft Windows XP [Version 5.1.2600] (C) Copyright 1985-2001 Microsoft Corp. C:\Documents and Settings\mpride>nslookup server.dignity.local *** Can't find server name for address 192.168.2.1: Non-existent domain *** Can't find server name for address 192.168.0.250: Non-existent domain DNS request timed out. timeout was 2 seconds. *** Can't find server name for address 192.168.0.1: Timed out *** Default servers are not available Server: UnKnown Address: 192.168.2.1 *** UnKnown can't find server.dignity.local: Non-existent domain The user's host file also includes an entry of 192.168.0.250 Server.dignity.local Thanks, Steve

Hi Steve, Thanks for update. > The user's host file also includes an entry of 192.168.0.250 Server.dignity.local Try to first remote the entry form hosts file on client. >C:\Documents and Settings\mpride>nslookup server.dignity.local >*** Can't find server name for address 192.168.0.250: Non-existent domain Do we really have A record “server” under zone “dignity.local” on host 192.168.0.250? Is there any problem the reach that server form client at remote by going through VPN tunnel ? could you also show us the result of “ping 192.168.0.250” form client ? > DNS Servers . . . . . . . . . . . : 192.168.2.1 192.168.0.250 192.168.0.1 Please change the prioritization to use the remote domain controller as the preferred DNS server on client. Thanks. Tiger LiTiger Li TechNet Community Support

Hi Steve, Thanks for update. > The user's host file also includes an entry of 192.168.0.250 Server.dignity.local Try to first remote the entry form hosts file on client. >C:\Documents and Settings\mpride>nslookup server.dignity.local >*** Can't find server name for address 192.168.0.250: Non-existent domain Do we really have A record “server” under zone “dignity.local” on host 192.168.0.250? Is there any problem the reach that server form client at remote by going through VPN tunnel ? could you also show us the result of “ping 192.168.0.250” form client ? > DNS Servers . . . . . . . . . . . : 192.168.2.1 192.168.0.250 192.168.0.1 Please change the prioritization to use the remote domain controller as the preferred DNS server on client. Thanks. Tiger LiTiger Li TechNet Community Support

Hi Steve, Thanks for update. > The user's host file also includes an entry of 192.168.0.250 Server.dignity.local Try to first remote the entry form hosts file on client. >C:\Documents and Settings\mpride>nslookup server.dignity.local >*** Can't find server name for address 192.168.0.250: Non-existent domain Do we really have A record “server” under zone “dignity.local” on host 192.168.0.250? Is there any problem the reach that server form client at remote by going through VPN tunnel ? could you also show us the result of “ping 192.168.0.250” form client ? > DNS Servers . . . . . . . . . . . : 192.168.2.1 192.168.0.250 192.168.0.1 Please change the prioritization to use the remote domain controller as the preferred DNS server on client. Thanks. Tiger LiTiger Li TechNet Community Support

Hi Tiger, Pinging 192.168.0.250 from the remote computer yields "Request time out" However, if I goto Run and type \\192.168.0.250 - the folder will open showing the shared folders on the server - so I know the connection is available. I didn't understand what you said: "Try to first remote the entry form hosts file on the client" The only two entries are: 127.0.0.1 192.168.0.250 Server.dignity.local There is an A Record in DSN for only 192.168.0.250. NOT Sever (but there is an NS record for server.dignity.local) No problems reaching the server from a remote host - as long as the VPN tunnel is active. I changed the priority of the DNS for the remote host too. Thanks again, Steve

Hi Tiger, Pinging 192.168.0.250 from the remote computer yields "Request time out" However, if I goto Run and type \\192.168.0.250 - the folder will open showing the shared folders on the server - so I know the connection is available. I didn't understand what you said: "Try to first remote the entry form hosts file on the client" The only two entries are: 127.0.0.1 192.168.0.250 Server.dignity.local There is an A Record in DSN for only 192.168.0.250. NOT Sever (but there is an NS record for server.dignity.local) No problems reaching the server from a remote host - as long as the VPN tunnel is active. I changed the priority of the DNS for the remote host too. Thanks again, Steve

Hi Tiger, Pinging 192.168.0.250 from the remote computer yields "Request time out" However, if I goto Run and type \\192.168.0.250 - the folder will open showing the shared folders on the server - so I know the connection is available. I didn't understand what you said: "Try to first remote the entry form hosts file on the client" The only two entries are: 127.0.0.1 192.168.0.250 Server.dignity.local There is an A Record in DSN for only 192.168.0.250. NOT Sever (but there is an NS record for server.dignity.local) No problems reaching the server from a remote host - as long as the VPN tunnel is active. I changed the priority of the DNS for the remote host too. Thanks again, Steve

Hi Steve, Thanks for update. > However, if I goto Run and type \\192.168.0.250 - the folder will open showing the shared folders on the server - so I know the connection is available. Could we please try to first disable the offline file feature on this host “hodconference” and try again ? > I didn't understand what you said: "Try to first remote the entry form hosts file on the client" Sorry for the typo . I meant remove the entry (192.168.0.250 Server.dignity.local) form hosts file so that we can test if the DNS server that we are point to use is working properly now . Otherwise I think we should troubleshoot form the DNS server(192.168.0.250) itself . Thanks Tiger Li Tiger Li TechNet Community Support

Hi Steve, Thanks for update. > However, if I goto Run and type \\192.168.0.250 - the folder will open showing the shared folders on the server - so I know the connection is available. Could we please try to first disable the offline file feature on this host “hodconference” and try again ? > I didn't understand what you said: "Try to first remote the entry form hosts file on the client" Sorry for the typo . I meant remove the entry (192.168.0.250 Server.dignity.local) form hosts file so that we can test if the DNS server that we are point to use is working properly now . Otherwise I think we should troubleshoot form the DNS server(192.168.0.250) itself . Thanks Tiger Li Tiger Li TechNet Community Support

Hi Steve, Thanks for update. > However, if I goto Run and type \\192.168.0.250 - the folder will open showing the shared folders on the server - so I know the connection is available. Could we please try to first disable the offline file feature on this host “hodconference” and try again ? > I didn't understand what you said: "Try to first remote the entry form hosts file on the client" Sorry for the typo . I meant remove the entry (192.168.0.250 Server.dignity.local) form hosts file so that we can test if the DNS server that we are point to use is working properly now . Otherwise I think we should troubleshoot form the DNS server(192.168.0.250) itself . Thanks Tiger Li Tiger Li TechNet Community Support

HI Tiger, Sorry for the delay. Disabled offline file feature and removed the entry from the host file (192.168.0.250 Server.dignity.local). I can still ping the server by name or IP address (but not FQDN). I can still do a \\server and get to the shared folders. Here's something interesting: On the remote computer, I changed the Domain DNS Suffix to dignity.local, rebooted the computer (keep in mind, the computer still in a workgroup). Went to add it to the domain (dignity.local) and it prompted me for the username/password - so I put my administrator credentials in. Praying it would join the domain then...but I got this: The following error occured attempting to join the domain "dignity.local" The Network Path was not found I'm not sure what's next. Still can't get the computer to join the domain. Thanks for your continued help... Steve

HI Tiger, Sorry for the delay. Disabled offline file feature and removed the entry from the host file (192.168.0.250 Server.dignity.local). I can still ping the server by name or IP address (but not FQDN). I can still do a \\server and get to the shared folders. Here's something interesting: On the remote computer, I changed the Domain DNS Suffix to dignity.local, rebooted the computer (keep in mind, the computer still in a workgroup). Went to add it to the domain (dignity.local) and it prompted me for the username/password - so I put my administrator credentials in. Praying it would join the domain then...but I got this: The following error occured attempting to join the domain "dignity.local" The Network Path was not found I'm not sure what's next. Still can't get the computer to join the domain. Thanks for your continued help... Steve I just got the computer to join the domain. Network path was not found triggered something in my head...who knows....but I turned off the firewall on the remote computer - tried to join the domain and it worked now. Looks like I just needed to add domain DNS Suffix and turn off the firewall (probably not the best solution to turn off/disable the firewall, but at this point, I don't want to spend much time tinkering w/the firewall settings...just turn it off....all together).

HI Tiger, Sorry for the delay. Disabled offline file feature and removed the entry from the host file (192.168.0.250 Server.dignity.local). I can still ping the server by name or IP address (but not FQDN). I can still do a \\server and get to the shared folders. Here's something interesting: On the remote computer, I changed the Domain DNS Suffix to dignity.local, rebooted the computer (keep in mind, the computer still in a workgroup). Went to add it to the domain (dignity.local) and it prompted me for the username/password - so I put my administrator credentials in. Praying it would join the domain then...but I got this: The following error occured attempting to join the domain "dignity.local" The Network Path was not found I'm not sure what's next. Still can't get the computer to join the domain. Thanks for your continued help... Steve I just got the computer to join the domain. Network path was not found triggered something in my head...who knows....but I turned off the firewall on the remote computer - tried to join the domain and it worked now. Looks like I just needed to add domain DNS Suffix and turn off the firewall (probably not the best solution to turn off/disable the firewall, but at this point, I don't want to spend much time tinkering w/the firewall settings...just turn it off....all together).