Hello I had the same problem as you, change port from UDP 1194 to TCP 1194 for both client and server and it worked. try it. Edward

How would you connect to the pfSense? Does each client install OpenVPN or do you have another firewall solution?

they all had different certificate but the common name was the same in the certificate. I hate myself sometimes! ::)

[image: beztytuugq3.th.jpg] I'm checking settings trying to connect from Net2 to Net1 - of course the only way is to route this through Net0 using both VPNS. Now it should be easier to understand. The main VPN server in Net0 is pfSense

Well that explains it heh - havent messed arround much with VPN at all - Anyway it worked with \ip number – I will also try messing arround with the WINS server. Thanx alot for all the help - /DaK

OK, the plugin started working when I added OpenVPN from package.

Thanks GruensFroeschli ! I will see what I can do.

So you only want to access services FROM the roadwarriors withing your existing network and not TO your roadwarriors. I Think you can just enable advanced outbound NAT and NAT from the roadwarrior-subnet to your existing network. For servers in your existing network it would seem as if the connections come from the IP of the pfSense-machine: http://forum.pfsense.org/index.php/topic,7001.0.html

1: I cannot speak from experience, but a few users reported that if you want to use it in a multiWAN enviroment you should use TCP and not UDP as carrier protocol. 2: The firewall rule is only there to allow your client to access the server itself. The connections you tunnel over this connection will not be firewalled. 3: Create a key/certificate pair for each client.

Can you ping by IP?  For the name resolution you might need to implement WINS.

Thank you very much ! I've been searching into the forum but i've not found the answer. Thanks again, Nahuel

Hi all !! solved the problem myself. all is working now The Wizard

Thanks chazers18 and GruensFroeschli for your replies. I don't see any major differences between your posts and mine. I'm thinking that I might have miss-configured something in the routing or nating on one of the boxes. As a follow up, RDC also 'kinda works'. I can connect to one machine (of the two that I tried so far). That being said the connection is unusable; it drops in and out, doesn't hardly refresh, and is unresponsive to input. I am thinking about merging the functionality of the two machines to see if that fixes this. It should simplify things at least… Oh well, wish me luck.

ouch… noob mistake... left the .txt when doing the config file... Now i see the options... The Wizard

Also could you post the output of the log on pfSense?

Wow, that compression option was the problem. I checked the box on the pfSense interface and now its working.  I had kinda seen that in the logs, but since it was a WARNING I really didn't give it much attention.  I'm used to seeing all kinds of warnings in my open source product logs that should usually just be ignored. Thanks for the help!