Software

Ask something
Discussion Locked

VPN connection can't access Exchange 5.5

0 helpful
5 replies

by mr. fixit 1 view

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

Have an odd problem involving VPN tunneling "talking" to our Exchange server via Outlook 2k. Other aspects of the VPN work in terms of "getting around" the server, but Outlook 2k just wont see the Exchange mail. The Exchange server is the same box as what they log into for the VPN tunnel. At a recent MS TechNet seminar, the MS guy claimed that since we are using a single NIC from the server to the switch, that that was the issue, and that a second NIC to the router/T1 and the setup of a multihoming system would solve that. Seemed like an odd and overly complex solution however. We are running (all on the same server) Back Office 4.5, Exchange 5.5 (SP3), IIS/OWA and on the client side Office/Outlook 2k...
Thoughts?

5 replies

by calves

Well, I have a similar setup, except that I upgraded the RAS server to W2K, but it worked just the same b4.
Because, most of your users connect in using a modem, the speed of the connection is very different from one on the network. To find the Exchange server, the client first use Host then DNS, and so on.
I found that by increasing the timeout settings for Exchange (Client machine, properties of Outlook 2000, on the general tab, towards the bottom) to 90 or 120 resolves the problem.

Give it a shot!

Good luck!

by esrfalco

I'm thinking it may be a DNS problem. As an experiment, try specifying the IP address of the Exchange server rather than the name and see if anything is different.

by mr. fixit

It partially tied into that; we eventually solved the issue by creating a router based "fixed tunnel" between our locations vs. just a VPN dialup approach...

This discussion is closed to new replies.