[OpenVPN home] [Date Prev] [Date Index] [Date Next]
[OpenVPN mailing lists] [Thread Prev] [Thread Index] [Thread Next]
Google
 
Web openvpn.net

[Openvpn-users] Re: No vnc, etc via connection


  • Subject: [Openvpn-users] Re: No vnc, etc via connection
  • From: Luc Van der Veken <lucvdv@xxxxxxxx>
  • Date: Wed, 15 Oct 2003 11:06:25 +0200

On Mon, 13 Oct 2003 19:19:57 +0200, <hypocrite@xxxxxxxxxxxxx> wrote:

> I can see the connection (openvpn-deamon-messages and ifconfig tap0). I can access a Win-share, but  neither vnc nor the Terminalserver.

Typical symptoms of an MTU problem: terminal server client will open a
connection, but show nothing but a black window until it times out.

Copying from a previous message:

James Yonan wrote:
> [...]  Try:
> 
>   tun-mtu 1500
>   tun-mtu-extra 32
>   mssfix 1300
> 
> or
> 
>   tun-mtu 1500
>   tun-mtu-extra 32
>   fragment 1300
>   mssfix
> 
> The first example fixes MTU problems with TCP only and has a negligable
> performance penalty.  In most cases, this is the best option.
> 
> The second example performs internal fragmentation on non-TCP protocols, but
> adds 4 additional bytes of overhead to every packet.  This is your second
> choice if mssfix by itself doesn't solve the problem.
> 
> As a diagnostic option, you can also use --test-mtu to have OpenVPN
> empirically measure the MTU, so you can pick a more optimal value than 1300.
> 
> James



____________________________________________
Openvpn-users mailing list
Openvpn-users@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/openvpn-users