transport, Exchange and VPN Connection

microsoft.public.exchange2000.transport - Microsoft Exchange Server


transport >> Exchange and VPN Connection

by Mitch » Wed, 21 Jan 2004 13:59:02 GMT

Exchange 2K & VPN

I have a sales office connected to our corporate office via VPN,
Corporate is using a Sonicwall Pro 200 and the sales office is using a
SOHO3.

When users connect to the Exchange Server and try to open e-mail with
attachments of 2MB or more it can take 3-4 minutes to open the
message, but when transferring files from server to server of 2MB or
more from it only takes seconds.

Corporate Office has 2MB Download & 480k Upload.
Sales Office has 512k Download & Upload.

Anyone have any ideas?

Top

transport >> Exchange and VPN Connection

by Lanwench [MVP - Exchange] » Thu, 22 Jan 2004 11:33:32 GMT


Replied in another group - if you need to post to multiple groups, it's best
to do so all at once in a single message (separate the NG names with commas)
so that everyone can follow the thread. Thanks ....

Crossposting = posting once to several newsgroups within a single message.
This is not a Bad Thing (presuming the list of groups posted to is small,
and all the groups are truly relevant to your question)

Multiposting = posting separate, identical posts to several newsgroups. This
is a Bad Thing. :-)

See http://www.blakjak.demon.co.uk/mul_crss.htm
Top
Similar Threads

1. Exchange over VPN connection? - Manage MS Exchange Server

2. Outlook 2007 connection to Exchnage 2007 over VPN looses connection 


If I'm in the Office, I can connect to the Exchange server with no problems.

If I'm in the office outside the firewall and connect to the Exchange server 
via VPN I'm fine too.



Though when I travel and am using Hotel and other Internet Connections My 
VPN to the office is fine, though I seem to have intermittent connectivity 
issues with Outlook 2007 to the Exchange 2007 server.  In the bottom right 
it will say, Connected, Disconnected, Trying to connect, etc...



The VPN is pretty finicky and needs a solid connection. It does not drop at 
all, so the connection to the VPN/Firewall is good.



Is there a Timeout or something I can change to allow it to not see the 
Server for a bit longer period before it disconnects?



Thanks,

  Scott<-

3. Can't establish connection over Satellite connection & VPN

4. Exchange/VPN Connection Slow 

We're running an SBS2K server.  Mutiple XP Pro laptops 
connect via VPN back to the server and synchronize using 
Outlook without problems.  The VPN connection is 
established almost immediately and connection to Exchange 
within 15-20 seconds.

One machine connects through the VPN without problem.  
However, it takes almost two minutes for it to connect to 
Exchange, then syncs without problem.  If the user uses 
another machine, the sync also happens without problem.

I have checked all the VPN settings on the client and 
even created a new connectoid but haven't met with any 
success.  Any help would be appreciated.

Thanks.

Jeff

5. VPN connection to exchange is very slow - Manage MS Exchange Server

6. Exchange 2003, Outlook 2003, VPN Connection Issues 

Hi All,

I've seen a lot of posts regarding Outlook through VPN, but I didn't
see any that address my issue specifically.  My apologies if this has
already been discussed.

My environment:

I have one Exchange 2003 SP3 server in a main office.  It runs on
Windows 2003 Server Standard Edition SP1.  We have 275 users total.
30 of these users are in a remote office 500 miles away.  We have 2
T1's at the main office and 1 T1 at the remote site.  We use Netscreen
208's at the main office and a Netscreen GT at the remote site.  The
two sites are connected via a VPN using the Netscreen Hardware, so
there are no VPN clients being used.  The VPN is open, so there are no
port restrictions involved.  All clients (XP) at the remote site are
members of the domain.   All servers and clients are fully patched to-
date. The users in the remote site have Outlook 2003 installed on
their desktops.  We are not using cached mode for Outlook 2003. There
is a DNS server in the main site.  The clients in the remote site use
this DNS server through the VPN.  There are no DNS issues -- clients
in the remote site can ping all resources including the Exchange
server in the main site by FQDN.  Connectivity for all resources seems
fine from the remote site to the main site through the VPN -- ping,
tracert, DNS, domain authentication, etc.  All T1's have been tested
and are functioning as expected.  The T1 in the remote site
experiences 80% usage -- typically for 1 hour in the morning and 1
hour in the afternoon.  Other than that, usage is @ 15%. I've
confirmed the MTU settings are default on the client, Netscreens and
the routers.

The problem:

Intermittently, the users in the remote office cannot connect to the
Exchange server using Outlook from their desktops.  In some cases,
Outlook "hangs" and cannot connect and there is no error.  Other
times, the users cannot connect and they get a pop-up message in
Outlook, "Exchange server is unavailable."  In each case, a reboot of
the client usually resolves this problem.  The problem is happening
almost every day for one or two users, but different users are
affected each time.  (It's not always the same users).  When the
problems happen, bandwidth usage is at a reasonable level, the clients
can ping the Exchange Server using FQDN, and other traffic is not
affected.  Most often, Outlook works fine in this configuration, so I
know everything is configured properly for basic connectivity.  I have
checked the Exchange server, and there are no problems reported on the
server when the problem occurs.

Also, I have 2 other remote sites connected in the same way -- using
Netscreen GT, T1, DNS at main site, and Outlook from desktop.  One
site is 1000 miles away (10 users).  The other site is 3000 miles away
(15 users).  The two other remote sites do not experience connection
problems to Exchange.

We have given the users the option of using OWA or connecting via
Terminal Server, but they really, really want to use Outlook from
their desktops.  We opted not to use RPC over HTTP because of security
concerns, so that's not an option here.

I've contacted the vendor for the T1 in the remote site several times,
and they assure me that the pipe is working as epxected.

Can anyone give me some ideas on how to troubleshoot this problem with
the one remote location with 30 users?  I'm not looking to change how
the users connect, as we have given them other options.  What I really
need to figure out is how to resolve the problems with Outlook on the
desktop through a VPN not connecting.

Thanks in advance.

7. exchange vpn connection - Manage MS Exchange Server

8. Remote Outlook 2003 VPN Connection to Exchange - WON'T CONNECT 

Hello everyone -

I'm hoping you can help me with an issue we have been having with some
of our remote Outlook clients. First, let me give you a background on
our network.

4 Locations connected via WAN VPN links.

1 Parent Domain, 4 Child Domains

1 Parent & Child Located Same Building - This child directly connects
to Parent PDC DHCP & DNS.

3 Child Domains located in multiple locations connected via WAN VPN
links.
Each of these children is running their own DHCP/DNS with forward
lookup zones of the other domains replicated to eachother.

Now, the problem we're having is that we have multiple Remote Outlook
2003 clients that connect via soft VPN to our primary location (parent
domain). When they login, they are able to access all network
resources, network shares, etc. However, when they try to login to
Exchange via Outlook they cannot connect. Most times, a dialog box
appears asking for a username and password. Even if the users enter
their correct username and password it doesn't work. The dialog box
just pops back up. They have also tried entering their username like
domain/username and still no luck.

I have also tried adding individual LMHOSTS files to these clients, and
still they cannot connect. They just continually get this password
dialog.

How can I get this to work?