Improve company productivity with a Business Account.Sign Up

  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 449
  • Last Modified:

Site to site VPN DNS Issue

Hello All

I have created a site to site VPN between our main and branch office. It uses the L2TP IPSec protocol between 2 ISA boxes using a pre shared key.

What I Can do:

Ping any machine from our Main to Branch and Vice Versa (IP address only)
Remote desktop to any machine from Main to Branch and Vice Versa (IP address only)
Browse network drives from Main to Branch and Vice Versa (IP address only)

What I can't do:

Ping machines by computer/machine name
Remote desktop to machines by computer/machine name
Join Branch office computers to Main Office Domain (domain controller cannot be located)

Join Branch office computers to Exchange Via Outlook

Scenario for Outlook
User is logged into Branch Domain, start Outlook and Add Exchange account, enter the IP address of the Main Office Exchange server, this then resolves to and underlines user name, wizard completes successfully. Start Outlook, message.

"Unable to open default e-mail folders. you must connect your Miscrosoft Exchange server computer with the current profile before you can syncronize you folders"

I'm pretty certain that it's a DNS problem, as with the other issues I mentioned, I have attached a network configuration diagram, can anyone see what I'm doing wrong?

Thanks in advance all.              
  • 6
  • 5
2 Solutions
use nslookup to see if you can resolve the names/ips at the main site. If you can, then it's not dns. Might be an issue with netbios or with ports blocked on ISA.
brynstarAuthor Commented:
Thanks for the reply, this is what happens with nslookup

nslookup remotecomputername

maindomaincontroller cannot find remotecomputername: Non-existant domain
hmm, clients not appending dns suffix?
What happens if you query by fqdn?
Get 10% Off Your First Squarespace Website

Ready to showcase your work, publish content or promote your business online? With Squarespace’s award-winning templates and 24/7 customer service, getting started is simple. Head to and use offer code ‘EXPERTS’ to get 10% off your first purchase.

brynstarAuthor Commented:
the FQDN for our remote site ends in .local if I nslookup or ping anything using the FQDN it replies from - not our domain. thanks again for your reply.
strange, do the clients have in their dns search suffix list?
Different domains at main and branch? If so, you might want to configure all clients with a dns search suffix list containing both domains, then make sure the zone is replicated to the branch dns server, so lookups don't go over the vpn.
You also want to make sure that all clients are only configured to use interrnal dns. Only the dns server should be able to query external dns.
brynstarAuthor Commented:
Yes the clients at main do have in thier dns search sufix list.

To test I have been working on one workstation manually putting the DNS into the LAN adapter so..

dns servers (main Domain controller) (branch Domain-controller)

dns search suffix

Still has no luck pinging branch by FQDN, only ip. thanks once again for your replies.
brynstarAuthor Commented:
have managed to get the netbios name to ping so ping remotedomaincontroller replies but I added the remote domain controller IP to the WINS server addresses in the local LAN config (and removed above mentioned DNS settings)
brynstarAuthor Commented:
Sorry, disregard the two above posts.

At the main office, I have setup the DNS search suffix within group policy to list and branchoffice.local

Client's at main office now list this within ipconfig/all

only 1 DNS server is configured for clients in main (main office DC)

what do I need to do within the DNS management of our Main DC? Is it a new forward lookup zone to the branch DC?

Also, when you say replicate the zone to the Branch DNS server, do you mean add new DNS search suffix's at the branch end?

Apologies if I sound way off, your help is most appreciated.

thanks again....
No worries. DNS can get confusing. Your setup sounds similar to my environment. I've got an issue I need to take care of this morning, but I will get back to you today on this.
Sounds like you're on the right track.
So at each site, the clients will have a dns search suffix list with both domains. With their local domain first in the list.
The DNS server at main should have a forward lookup zone for branchoffice.local (secondary zone).
The DNS server at branchoffice will have a secondary zone for (secondary zone)
This way, DNS servers at both sites will be able to resolve records for either domain.

You still might run into some strange issues down the road though. For instance, if is registered to another company, or is your company's web site, then vpn clients with split tunneling might resolve to the wrong IP. Also, the DNS client strips subdomains as it searches for a valid record. So, a client searches for, and doesn't get a valid result, eventually it'll look for As you know that's an actual website, so you might have an issue there too.

Microsoft recommends using a subdomain of a valid, registered domain for windows domains. Something like,

.local is used by some vendors for upnp, so this could create some issues there too.

If it's a good fit for your organization, then the best solution would be to get both sites on the same domain, or at least in the same forest. Again, using subdomains of a valid, registered domain.
brynstarAuthor Commented:
thanks so much, that's done it. Added two secondary zones each side and can now ping/browse by netbios, ip or FQDN.

I can't thank you enough for your help!

Superb! A************

Best Regards
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

The 14th Annual Expert Award Winners

The results are in! Meet the top members of our 2017 Expert Awards. Congratulations to all who qualified!

  • 6
  • 5
Tackle projects and never again get stuck behind a technical roadblock.
Join Now