Outlook over VPN

W

wrigley.jenson

Anyone get anywhere with this? I have the same problem. We just did a
huge network move yesterday in which Company A migrated from an office-
based network to a "work-at-home" solution. Their Exchange server is
in our data center and they connect into it via Cisco vpn client. They
can map shared drives (using IP address), they can access their C&P
Accounting program that's on the server, and they can ping the
ExchSrv. (OWA also works just fine and we tested 2-way email flow).
But when they open up Outlook, it times out and says it can't connect
to the exchange server.

I'm out of town this weekend but one thing I thought of was that maybe
I have to manually add the IP address of Exchange Server in the
lmhosts and/or hosts file. Has anyone else tried this? I have verified
that the FQDN is listed in the email settings, so I'm wondering if it
just can't resolve the name of it because of some DNS discrepancies.
Especially because their old shortcuts to shared folders stopped
working after the move and we had to re-create them using \\172.16.x.x
\shared instead of \\server\share

Anyone? :)

Cheers
 
N

neo [mvp outlook]

You are definitely on the right track in regards that adding entries to the
hosts/lmhosts file will resolve whatever DNS/WINS name resolutions exist in
the environment. However you must remember to add all domain
controller/global catalog servers as well.

Other than that, the only other thing that might go funky across a Cisco VPN
connection is that you have to change the authentication in the Outlook
settings from Negotiate/Kerberos authentication to NTLM. The reason why is
that Kerberos authentication tends to happen over UDP and the Cisco client
might be dropping them.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top