It is too slow to open maped drives in VPN connection

Hi folx;
We have Watchguard firebox X700. we use its VPN and the enctyption is set to
40. Connecting VPN is fine however once we connect to the Fibox on VPN we
experience extreme speed problem while accesing to our maped drives in
internal server and Outlook takes forever to connect to the exchange server
if it connects..

Any ideas how to fix this issue?

Mike
NesTECH.net

If it the way VPN is. It is a horrible performer and always has been. You
need *massive* amounts of bandwidth for it to even be usable. You cannot
buy into all the industry "hype" about how great VPN is.

Ours is "usable" but we had to "merge" two T1 lines (which are synchronous)
to accomplish it. Remember that ADSL and Cable Internet are asynchonous and
the VPN will sync and run only at the slower "upload speed".

--
Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com



"Chet Guzel" <(E-Mail Removed)> wrote in message
news:%23ZDQ$(E-Mail Removed)...
> Hi folx;
> We have Watchguard firebox X700. we use its VPN and the enctyption is set
to
> 40. Connecting VPN is fine however once we connect to the Fibox on VPN we
> experience extreme speed problem while accesing to our maped drives in
> internal server and Outlook takes forever to connect to the exchange
server
> if it connects..
>
> Any ideas how to fix this issue?
>
> Mike
> NesTECH.net
>
>

If the problem is that it is slow to connect (rather than slow to
transfer data), it could be a DNS problem. Does the VPN client have the
correct DNS server IP and the correct DNS suffix for the network it connects
to?

Phillip Windell wrote:
> If it the way VPN is. It is a horrible performer and always has
> been. You need *massive* amounts of bandwidth for it to even be
> usable. You cannot buy into all the industry "hype" about how great
> VPN is.
>
> Ours is "usable" but we had to "merge" two T1 lines (which are
> synchronous) to accomplish it. Remember that ADSL and Cable Internet
> are asynchonous and the VPN will sync and run only at the slower
> "upload speed".
>
>
> "Chet Guzel" <(E-Mail Removed)> wrote in message
> news:%23ZDQ$(E-Mail Removed)...
>> Hi folx;
>> We have Watchguard firebox X700. we use its VPN and the enctyption
>> is set to
>> 40. Connecting VPN is fine however once we connect to the Fibox on
>> VPN we experience extreme speed problem while accesing to our maped
>> drives in internal server and Outlook takes forever to connect to
>> the exchange server if it connects..
>>
>> Any ideas how to fix this issue?
>>
>> Mike
>> NesTECH.net

"Bill Grant" <not.available@online> wrote in
news:(E-Mail Removed):

> If the problem is that it is slow to connect (rather than slow to
> transfer data), it could be a DNS problem. Does the VPN client have
> the correct DNS server IP and the correct DNS suffix for the network
> it connects to?
>
> Phillip Windell wrote:
>> If it the way VPN is. It is a horrible performer and always has
>> been. You need *massive* amounts of bandwidth for it to even be
>> usable. You cannot buy into all the industry "hype" about how great
>> VPN is.
>>
>> Ours is "usable" but we had to "merge" two T1 lines (which are
>> synchronous) to accomplish it. Remember that ADSL and Cable Internet
>> are asynchonous and the VPN will sync and run only at the slower
>> "upload speed".
>>
>>
>> "Chet Guzel" <(E-Mail Removed)> wrote in message
>> news:%23ZDQ$(E-Mail Removed)...
>>> Hi folx;
>>> We have Watchguard firebox X700. we use its VPN and the enctyption
>>> is set to
>>> 40. Connecting VPN is fine however once we connect to the Fibox on
>>> VPN we experience extreme speed problem while accesing to our maped
>>> drives in internal server and Outlook takes forever to connect to
>>> the exchange server if it connects..
>>>
>>> Any ideas how to fix this issue?
>>>
>>> Mike
>>> NesTECH.net
>
>
>

We recently had a report of VPN users getting really sucky performance.
It turned out to be the way the VPN client was (or wasn't) setting the
MTU. Cranking it down to 572 bytes fixed the problem, although I suspect
something in the 1000-1200 byte range may have worked. You can set it
via the registry and some VPN clients (Cisco) ship with an MTU setting
utility.

HTH,

Wayne Tilton

VPN's are extremely slow without massive bandwidth. I have several clients
who have this issue. The way i have always worked around this is by creating
another server as a domain controller at the second office and using DFS and
NT FRS (Replication) to update server B constantly with server A, and update
server A constantly with server B. I have found this to be a very cost
effective solution. If you decide to go this route though, i do want to warn
you that DFS and Replication is almost counterintuitive to setup for the
first time.

Micah A. Norman