If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Display Modes |
#1
|
|||
|
|||
What's different about WinXP versus Win10 ovpn doubleclicking?
What's different about WinXP versus Win10 ovpn doubleclicking?
What do I need to change on Win10 to get the connection to just start when I doubleclick on the *.ovpn text file like it has been doing for years on WinXP? WINXP: I doubleclick on a text *.ovpn file & it connects to VPN. I close the opened text file & it disconnects from VPN. OpenVPN v2.3.11-I001 WIN10: I doubleclick on a text *.ovpn file & doesn't connect that way. I have to go to the task tray and connect from there. Yuck. OpenVPN v2.3.9-I601 What happens on Win10 is the following: 1. I doubleclick on the *.ovpn text file 2. Up pops an obnoxious form: User Account Control: Do you want to alter this app to make changes to your PC? [Yes][No] 3. Then up pops an error form: OpenVPN GUI I'm trying to parse "C:\Users\user\Desktop\file.ovpn" as an --option parameter but I don't see a leading '--' [OK] What do I need to change on Win10 to get the connection to just start when I doubleclick on the *.ovpn text file like it has been doing for years on WinXP? |
Ads |
#2
|
|||
|
|||
What's different about WinXP versus Win10 ovpn doubleclicking?
Roy Tremblay wrote:
What's different about WinXP versus Win10 ovpn doubleclicking? What do I need to change on Win10 to get the connection to just start when I doubleclick on the *.ovpn text file like it has been doing for years on WinXP? WINXP: I doubleclick on a text *.ovpn file & it connects to VPN. I close the opened text file & it disconnects from VPN. OpenVPN v2.3.11-I001 WIN10: I doubleclick on a text *.ovpn file & doesn't connect that way. I have to go to the task tray and connect from there. Yuck. OpenVPN v2.3.9-I601 What happens on Win10 is the following: 1. I doubleclick on the *.ovpn text file 2. Up pops an obnoxious form: User Account Control: Do you want to alter this app to make changes to your PC? [Yes][No] 3. Then up pops an error form: OpenVPN GUI I'm trying to parse "C:\Users\user\Desktop\file.ovpn" as an --option parameter but I don't see a leading '--' [OK] What do I need to change on Win10 to get the connection to just start when I doubleclick on the *.ovpn text file like it has been doing for years on WinXP? Using this as a rough (cross-platform) approximation: https://linux.die.net/man/8/openvpn openvpn --config C:\Users\user\Desktop\file.ovpn Maybe something in here will work. There is a Nirsoft application to make it easier. https://superuser.com/questions/3618...dows-open-with http://www.nirsoft.net/utils/file_types_manager.html Paul |
#3
|
|||
|
|||
What's different about WinXP versus Win10 ovpn doubleclicking?
On Wed, 24 May 2017 10:51:18 -0400,
Paul actually wrote: What do I need to change on Win10 to get the connection to just start when I doubleclick on the *.ovpn text file like it has been doing for years on WinXP? Using this as a rough (cross-platform) approximation: https://linux.die.net/man/8/openvpn openvpn --config C:\Users\user\Desktop\file.ovpn Maybe something in here will work. There is a Nirsoft application to make it easier. https://superuser.com/questions/3618...dows-open-with http://www.nirsoft.net/utils/file_types_manager.html Paul Thanks Paul. Your response pointed me in the right direction! 1. I looked at the file associations for ovpn files on WinXP: https://s29.postimg.org/estakppgn/openvpn.gif 2. On Win10, I needed to change the association for ovpn files FROM: OpenVPN GUI for Windows TO: OpenVPN Daemon https://s16.postimg.org/mcs4crgsl/Clipboardq02.jpg 3. Now, just clicking on the ovpn file connects to VPN on Win10! https://s28.postimg.org/rg7ux9b8t/Clipboard0q1.jpg Now on both WinXP and Win10, when I click on any ovpn file, I'm connected to VPN, and when I close that window, I'm disconnected from VPN. Works like a charm! Thanks. |
#4
|
|||
|
|||
What's different about WinXP versus Win10 ovpn doubleclicking?
On Thu, 25 May 2017 02:25:38 +0000 (UTC),
Roy Tremblay actually wrote: 1. I looked at the file associations for ovpn files on WinXP: https://s29.postimg.org/estakppgn/openvpn.gif 2. On Win10, I needed to change the association for ovpn files FROM: OpenVPN GUI for Windows TO: OpenVPN Daemon https://s16.postimg.org/mcs4crgsl/Clipboardq02.jpg 3. Now, just clicking on the ovpn file connects to VPN on Win10! https://s28.postimg.org/rg7ux9b8t/Clipboard0q1.jpg Now on both WinXP and Win10, when I click on any ovpn file, I'm connected to VPN, and when I close that window, I'm disconnected from VPN. Works like a charm! I *thought* VPN worked on Windows 10 but I am having huge permission problems which don't exist on Windows XP so I will ask separately about this log file in a separate thread of its own. Obviously though, I'm missing a *new* step that Windows 10 requires to do the things that VPN needs. FlushIpNetTable failed on interface [17] {78A54AAA-5893-4E9A-9FAB-429FF3FB3C87} (status=5) : Access is denied. ROUTE: route addition failed using CreateIpForwardEntry: Access is denied. [status=5 if_index=8] Route addition via IPAPI failed [adaptive] Route addition fallback to route.exe env_block: add PATH=C:\WINDOWS\System32;C:\WINDOWS;C:\WINDOWS\Sys tem32\Wbem ERROR: Windows route add command failed [adaptive]: returned error code 1 C:\WINDOWS\system32\route.exe ADD 0.0.0.0 MASK 128.0.0.0 10.211.1.46 ROUTE: route addition failed using CreateIpForwardEntry: Access is denied. [status=5 if_index=17] Route addition via IPAPI failed [adaptive] Route addition fallback to route.exe env_block: add PATH=C:\WINDOWS\System32;C:\WINDOWS;C:\WINDOWS\Sys tem32\Wbem ERROR: Windows route add command failed [adaptive]: returned error code 1 C:\WINDOWS\system32\route.exe ADD 128.0.0.0 MASK 128.0.0.0 10.211.1.46 ROUTE: route addition failed using CreateIpForwardEntry: Access is denied. [status=5 if_index=17] Route addition via IPAPI failed [adaptive] Route addition fallback to route.exe env_block: add PATH=C:\WINDOWS\System32;C:\WINDOWS;C:\WINDOWS\Sys tem32\Wbem ERROR: Windows route add command failed [adaptive]: returned error code 1 Initialization Sequence Completed |
Thread Tools | |
Display Modes | |
|
|