Maybe this helps:
Sometimes a VPN is limiting the MTU and the machines at some (both?) ends
have to do fragment/defragment. This does not work in all configurations or
may impact in other ways your model.
Try to specify a lower MTU than the default, either at endpoints or at the
VPN endnodes level.
Unfortunately I cannot explain further and have no reference at hand, but a
quick search on "VPN MTU stale" or something like that may point you to a
more detailed issue description

----- Original Message ----- 
From: <[EMAIL PROTECTED]>
To: <twsocket@elists.org>
Sent: Thursday, July 14, 2005 2:27 PM
Subject: [twsocket] No connection with TCP/IP over VPN


> I'm not very much into networking, so my question might be quite dumb.
>
> I have made a controller for a datalogging application that uses TCP/IP
> to allow the logged data to be transferred to a connected computer. The
> IP address of this controller is 192.168.2.10. To retrieve the data via
> the local network, I have used the TWSocket component (cbuilder 1), set
> the address to 192.168.2.10 (PC address 192.168.2.2), port to 10000
> (which is used to transfer the data) and this appears to work flawless.
>
> Now we try to get the data into a different network (IP 192.168.0.x)
> using VPN, but TWSocket can't connect. The VPN connection is working
> OK, and the controller responds to a PING from this network over the
> VPN as well, but nothing happens with my TWSocket application. Port
> 10000 is open on both ends of the network firewalls. Where should I
> look for to troubleshoot this problem?
>
> Menno
>
>
>
>
> -- 
> To unsubscribe or change your settings for TWSocket mailing list
> please goto http://www.elists.org/mailman/listinfo/twsocket
> Visit our website at http://www.overbyte.be
>
>



-- 
To unsubscribe or change your settings for TWSocket mailing list
please goto http://www.elists.org/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be

Reply via email to