Closed GoogleCodeExporter closed 9 years ago
I should have mentioned (soholistic again) that I am using Remote Desktop to
connect to the server through the
tunnel.
Original comment by soholis...@gmail.com
on 22 Dec 2009 at 8:38
A Google search of "SE_RESET openvpn" yields a thread on the Viscosity forum
(Viscosity is another OpenVPN
GUI): http://www.viscosityvpn.com/forum/viewtopic.php?f=3&t=25
I don't see anything wrong with either your config or the one in the forum, but
the following three lines are
not ones that I use, and appear in both configs, so maybe they have something
to do with it:
nobind
persist-key
persist-tun
or maybe it just has something to do with the file format of the config file or
something -- he/she seemed to
fix his/her config file by replacing it with an OpenVPN sample config file
(edited to match his settings, I
assume).
Original comment by jkbull...@gmail.com
on 25 Dec 2009 at 12:35
Thanks - will try what you suggest. In fact, config was brought over from
windows machine and maybe text
version is the problem. Thanks again!
Original comment by soholis...@gmail.com
on 27 Dec 2009 at 2:55
If you start Tunnelblick with no configuration file present in
~/Library/Application
Support/Tunnelblick/Configurations, Tunnelblick will create a sample config
file for you and open it in TextEdit.
You could then copy/paste from your PC config file.
Please let us know what happens.
Original comment by jkbull...@gmail.com
on 27 Dec 2009 at 3:18
Just found a bug in what I just suggested - after it creates the sample config
file, Tunnelblick opens the wrong
copy TextEdit. Just exit TextEdit and open the file by double-clicking it in
Finder.
Original comment by jkbull...@gmail.com
on 27 Dec 2009 at 3:31
Bug referred to in my comment 5 was fixed in the source in r324.
Original comment by jkbull...@gmail.com
on 17 Jan 2010 at 9:55
Tried contacting the original poster directly to find out if this has been
resolved. No response for three weeks.
Original comment by jkbull...@gmail.com
on 15 Mar 2010 at 2:35
Original issue reported on code.google.com by
soholis...@gmail.com
on 22 Dec 2009 at 3:16