Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people, just like you, are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions

Connecting Outlook 2007 to Exchange 2003 over VPN

Posted on 2010-09-21
Last Modified: 2012-06-27
I have an intermittent problem connecting Outlook 2007 to an Exchange 2003 server over my VPN.  I always use a hosts file on the computers and most of the time it works fine.  However, sometimes it does not.  The problem appears when I hit the "check name" button and it fails to resolve the user.  I have this problem about 25% of the time when I try to connect this way.  Outlook 2003 never has a problem synchronizing over the VPN to the Exchange server.

Any Ideas?
Question by:Kirchtoe
  • 2
  • 2
  • 2
  • +1

Expert Comment

ID: 33729209
You must be using split tunneling and the DNS settings for DHCP are not resolving internal name/IP addresses. VPN should assign new DHCP settings w/ an internal DNS server.

If you can, stay away from hosts files.

Expert Comment

ID: 33730035
Are you using the fully qualified domain name?

^^ is right, stay away from host files, they are never a good idea.


Author Comment

ID: 33734218
I have a DNS and DHCP server on each side of the tunnel that handles those duties for each network.  On the LAN where I am trying to connect the Outlook client, where do I specify the FQDN?  Do I add it to my DNS or in DHCP.
Is Your AD Toolbox Looking More Like a Toybox?

Managing Active Directory can get complicated.  Often, the native tools for managing AD are just not up to the task.  The largest Active Directory installations in the world have relied on one tool to manage their day-to-day administration tasks: Hyena. Start your trial today.


Accepted Solution

Richard1985 earned 250 total points
ID: 33734295

Depending on the IP ranges on each network I would specify the exchange server in the host file against local IP - if the network ranges are the same this would cause issues. This will effectively avoid DNS issues and should work.

Do not use multiple exchange entries such as:     Exchaange     Exchange.local

Instead use:
<local IP>       <Exchange name>.local

As duplicate entries can create loopbacks and crash Outlook over VPN - this was the cause of a similar issue I had. Try it and let me know.


Author Comment

ID: 33738808

I entered the complete FQDN of the server in my hosts file and it worked!

thank you

Expert Comment

ID: 33738825
You should still stay away from host files.

When you connect to the server, use the FQDN and it should connect without a host file entry.

Expert Comment

ID: 33742060
Glad that worked for you Kirch,

Personally I have never had issues using the FQDN only in host files as long as network IP ranges are different.

Thanks for the points :o)

Featured Post

Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Marketers need statistics and metrics like everybody else needs oxygen. In this article we explain how to enable marketing campaign statistics for Microsoft Exchange mail.
How to resolve IMCEAEX NDRs in Exchange or Exchange Online related to invalid X500 addresses.
In this Micro Video tutorial you will learn the basics about Database Availability Groups and How to configure one using a live Exchange Server Environment. The video tutorial explains the basics of the Exchange server Database Availability grou…
how to add IIS SMTP to handle application/Scanner relays into office 365.

860 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question