Question Locked

Outlook 2007 connection to Exchange 2003 via VPN?

0 helpful
9 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

We have recently upgraded some users to Office 2007 and therefore Outlook 2007. This connects fine to Exchange 2003 when they are in the office but says the server is unavailable when they are working remotely via VPN.

When on VPN they can access the network, ping the exchange server and resolve the exchange server name in the exchange outlook profile (fully qualified DNS name). However, when opening Outlook 2007 on a VPN connection it appears to hang and then eventually says the Exchange server is unavailable. Our users still on Outlook 2003 have no remote VPN connection issues.

Does anyone know what the issue is with Outlook 2007 over VPN and how to resolve it?

We have: Windows 2003 Server, Exchange 2003 Server and the VPN software is from Safenet (though I've a feeling if we had a differnet VPN like Cisco we'd still have the same problem) and the client operating systems are Windows XP Professional (not Vista - as I've seen some solutions for this issue on Vista machines).

Regards
Mark

9 replies

by jswentworth

If you have Cached mode disabled, enable it on those laptops. OR vice versa.
The other option is to use RPC over HTTP. If you need info on setting that up let me know.

by Member 27936733

Some info on the RPC over HTTP would be useful! I've tried setting this up but couldn't seem to get it to work. I know what the OWA address is and that works okay but the customer wants to use Outlook 2007.

by robthegeek

I am running into the same issue here and have not found a solution either. At least the OWA works for my users, but they would really rather use Outlook 2007. I have tried adding the port 1723 through the firewall, but that makes no difference to their connection. My users do not even get the information that the system is trying to connect to the server, it just says Unavailable with the error code 0x8004011D

by Member 27936733

Hi Rob,

There may be another way to fix this issue but in the end I found that putting the fully qualified domain name of the exchange server in the hosts file solved the problem (the host file of the computing connecting via VPN).

[Exchange Server IP Address] [tab] [Exchange Server Name].[yourdomainname]

An example would be:

192.168.0.1 exchangeservername.domainname.local

(I'd previously modified the hosts file with this entry but had not put the domainname.local part on the end).

Let me know if that works for you! Hopefully I've explained this clearly.

Regards
Mark

by robthegeek

Thanks Mark, hopefully I will be able to test this out in about 10 days. Right now, the problem laptop is on a west coast tour, and won't be back in the area until late June.

Take care,

Rob

by jazzr

Hi,

We had very similar issues to the ones decribed. Adding the fully qualified domain name worked for us.

Thanks as always to everyone involved.

Jazz

by munk79

This worked for me too...I tried EVERYTHING to get this stupid outlook working and could not figure it out. Finally came across this thread and it worked. Something so simple. We had the hosts file all filled out...but adding the domainname at the end made it connect again finally. THANKS MARK!!

by grave d.

go to
C:\WINDOWS\system32\drivers\etc

edit file hosts

our hosts (server IP 192.168.2.1(in local net):

127.0.0.1 localhost
192.168.2.1 serverYY.XXX.local

This discussion is closed to new replies.