Falcor and Christiaens

Thanks for the advice. There ended up being a problem on my home 
ISP's end, which i was able to resolve. And all is working as it 
said it would.

Falcor, a similar howto for ipsec would be great! I'd love to 
take a look and test it out - if you want somebody to test your 
configurations before publishing it i'd be happy to do so. As far 
as i could tell clients weren't built into the windows OS for 
ipsec (though maybe they are), and that's why i figured PPTP 
would be better, but if there are free clients available that 
would also be an option for us.

Matthew

Matthew Geddert wrote:

> Hello,
> 
> I've followed the advice in this guide:
> 
> http://m0n0.ch/wall/guides/pptpvpn.pdf
> 
> And am not able to access pptp from a remote location (i.e. on the WAN 
> side of the firewall). I've done a port scan with nmap on the WAN side 
> and all ports are blocked and it in fact doesn't even respond to a ping 
> - which I’m guessing is the default behavior. On the LAN side port 1723 
> (i.e. the pptp port) is open and I was able to connect to pptp using the 
> standard windows XP built in client. I have the "pptp -> any rule" as 
> described in the pdf. Does anybody have any suggestions for allowing me 
> to remotely access pptp (i.e. through the WAN interface)?
> 
> I have enabled all ports on the wan side with a wan rule of * * * * * 
> and that didn't do anything to allow access to pptp from the WAN side.
> 
> Or, if this is an egregious security error could somebody please suggest 
> a better alternative for remote access to the LAN.
> 
> Thanks for the help
> 
> Matthew
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: m0n0wall dash unsubscribe at lists dot m0n0 dot ch
> For additional commands, e-mail: m0n0wall dash help at lists dot m0n0 dot ch
> 
> 
>