I've had a quick look at a virtual winxp I've got and it does seem to
be the default unfortunately. I'd recommend quickly checking what the
vpn client has selected and at the same time check that the routing
from your web server can actually get back to the ip address that your
vpn client is given. It's also worth checking if there's any firewall
rules the other side has that could be interfering.
Once you've got a vpn tunnel established through your openbsd firewall
the openbsd firewall has no control over what is happening within the
tunnel. The error is then either on your machine or on the thing
you're trying to connect to the other side. It might be worth (and I
will wash my mouth out with soap) trying using Internet Explorer
instead of Firefox just in case it's your firefox browser having the
problem. ( a quick telnet to port 80 on the webserver would also prove
connectivity).
I have assumed that you're doing a pptp tunnel to a windows server and
only going through the firewall - not starting or terminating the
tunnel on the firewall. If you are then the issue is with your openbsd
firewall and you'd need to add routes and rules into that.
Hope some of this helps.
On 30 May 2009, at 21:19, patrick keshishian wrote:
On Sat, May 30, 2009 at 11:09 AM, Nick Ryan <n...@njryan.com> wrote:
There's a tickbox on the windows vpn client to tick.
It's quite well hidden.
To get to it, do properties on your VPN connection, then click the
networking tab. Then do properties on the TCPIP protocol, then click
advanced and select the Use Default Gateway On Remote Network Option.
It's handy to not have this ticked if you want all your non work
traffic to
go out via your normal connection, but in this case you want it
ticked.
do you know if the Windows VPN client sets up a route for the remote
network if this checkbox is not checked? Meaning, if the user does not
select this option, is s/he required to set up the route manually?
--patrick
Cheers - Nick
On 29 May 2009, at 22:08, Juan Miscaro wrote:
Hi, I'm trying to set up a PPTP tunnel for a Windows machine lying
behind my OBSD 4.0 internet gateway. I can establish the tunnel but
I'm missing the last piece in the puzzle. This is the routing of
the
RFC 1918 addresses. Locally I have 10.9.0.0/16 addresses and the
windows machine wants to connect to a web server on the remote side
that is using 192.168.0.0/16.
I'm not familiar enough with Windows to say if there is some
checkbox
to fill in to make this work but the Firefox browser complains:
Connection interrupted.
The connection to the server was reset while the page was loading.
The network link was interrupted while negotiating a connection.
Please try again.
Is there some particular route that needs to be set up for this to
work?
Thank you,
/jm
