<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"></head><body><div><br></div><div>Hi Leigh,</div><div><br></div><div>Not sure if this is exactly relevant but i had an issue recently with an ubuntu/zentyal config not allowing traffic for ptpp vpn user past the local network range.</div><div><br></div><div>I found it was a dns/proxy issue, fixed it buy editing a dns stub zone to allow local subnets access.</div><div><br></div><div>Prob need a bit more info from you.</div><div><br></div><div>Let me dig out the script in the morning and i will fire over to you.</div><div><br></div><div>Will send you my skype address if you wanna try and work through this.</div><div><br></div><div>Cheers</div><div><br></div><div>Rob</div><div><br></div><div><br></div><div><div style="font-size:100%">Sent from Samsung tablet</div></div> <br>Leigh Porter <leigh.porter@ukbroadband.com> wrote:<br><meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<style type="text/css" id="owaParaStyle"></style>
<div style="direction: ltr;font-family: Tahoma;color: #000000;font-size: 10pt;">Hiya All,
<div><br>
</div>
<div>I have a thinlinc server on three subnets, one local for local thinlinc clients, one subnet for remote VPN access and another that connects to an MPLS VPN across various other networks.</div>
<div><br>
</div>
<div>When clients on the local LAN connect all works fine. But when clients connect over the remote VPN subnet or the MPLS VPN, the IP address I connect to on the client is correct but then is seems to change to trying to connect to the LAN subnet instead.</div>
<div><br>
</div>
<div>Why does it not just connect to the IP address I specify in the client?</div>
<div><br>
</div>
<div>This behaviour seems odd and is really annoying. If I tell it what address to connect to, it really should just connect to that and not some other IP address on the same host.</div>
<div><br>
</div>
<div><br>
</div>
<div>--</div>
<div>Leigh Porter</div>
<div><br>
</div>
</div>
<br clear="both">
______________________________________________________________________<br>
This email has been scanned by the Symantec Email Security.cloud service.<br>
For more information please visit http://www.symanteccloud.com<br>
______________________________________________________________________<br> </body>