slow vpn traffic...

[maxim2004]

hi there...
i'm using vpn with bundled with wingate 5.2.3...the problem is any vpn access is so slow.. i can't access printer or any file transfer due to too small bandwidth....any extra setting???...vpn traffice utilizes about 2-3kbps, but if i connect to apache to d/l some files from one server to another it utilizes about 100kbps....i use 128kbps adsl to connect to the internet...the problem shall be at some settings in wingate


any idea??
thanks support...

[Pascal]

In the "Guideling to setting up a functional VPN" you will find references on how to test the MTU. I'd recommend that you do that. (http://www.wingate.com/files/VPN_Setup_Guide.pdf)

The VPN has a header that it needs to attach to every packet. If the MTU is too close you could be experiencing a fragmentation problem; where the header added puts it over the MTU, which will result in every packet being fragmented, etc. etc.

If you do the MTU tests as described in that document (Basically consists of pinging with a specified packet size and no fragmentation until the packets cannot be sent through) you can work out what the best sized MTU should be to take care of the VPN headers.

When you are pinging a machine across the network, what time do you get? E.g.

Pinging 192.168.13.1 with 32 bytes of data:
Reply from 192.168.13.1: bytes=32 time<1ms TTL=64
Reply from 192.168.13.1: bytes=32 time<1ms TTL=64
Reply from 192.168.13.1: bytes=32 time<1ms TTL=64
Reply from 192.168.13.1: bytes=32 time<1ms TTL=64

Lastly, 6.0.3 is significantly better than 5.2.3. Especially wrt the driver. You can use your 5.2.3 license key with 6.0.3.

[maxim2004]

i got

C:\WINDOWS\Desktop>ping 192.168.0.1

Pinging 192.168.0.1 with 32 bytes of data:

Reply from 192.168.0.1: bytes=32 time=192ms TTL=128
Reply from 192.168.0.1: bytes=32 time=124ms TTL=128
Reply from 192.168.0.1: bytes=32 time=151ms TTL=128
Reply from 192.168.0.1: bytes=32 time=138ms TTL=128

Ping statistics for 192.168.0.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 124ms, Maximum = 192ms, Average = 151ms

C:\WINDOWS\Desktop>

and this

C:\WINDOWS\Desktop>ping 192.168.0.1 -l 1350

Pinging 192.168.0.1 with 1350 bytes of data:

Reply from 192.168.0.1: bytes=1350 time=467ms TTL=128
Reply from 192.168.0.1: bytes=1350 time=494ms TTL=128
Reply from 192.168.0.1: bytes=1350 time=426ms TTL=128
Reply from 192.168.0.1: bytes=1350 time=439ms TTL=128

Ping statistics for 192.168.0.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 426ms, Maximum = 494ms, Average = 456ms

C:\WINDOWS\Desktop>

can u suggest me exactly how to solve this?
also how to change mtu in adaptor?
i've tried many software but it still doesn't work...

thanks alot

[maxim2004]

hi pascal and other support,
after messing around with mtu changing now i can transfer and print across vpn but only between both 2 servers....i still can't print across network...

well, i'd show my network scenario....

LAN1 -> SERVER1 -> INTERNET <- SERVER2 <- LAN2

now, i can transfer file with full bandwidth from server1 and server2 and printing across vpn...but the problem is computer in lan1 cannot connect to server2 at full bandwidth so it makes file copying process take long time(can utilize about 3kbps) and surely cannot print from computer in lan1 to server2....
i've change mtu value to 576 in all computers...

is it still because mtu value????

thanks alot