Opened 2 years ago

Closed 20 months ago

#185 closed Bug / Defect (notabug)

OpenVPN did not detect windows system path WINDIR SYSTEMROOT SYSTEMDRIVE

Reported by: cavila Owned by:
Priority: minor Milestone:
Component: Configuration Version: 2.2.1
Severity: Not set (if unsure, select this one) Keywords: systemroot windows route route.exe
Cc:

Description

I installed the windows package on a windows XP Professional.
But on openvpn log I got route.exe errors below:

Fri Dec 16 09:22:37 2011 Notified TAP-Win32 driver to set a DHCP IP/netmask of 10.8.0.6/255.255.255.252 on interface {62BF0E58-C57C-4E8A-8888-6ADD532B96D7} [DHCP-serv: 10.8.0.5, lease-time: 31536000]
Fri Dec 16 09:22:37 2011 Successful ARP Flush on interface [65543] {62BF0E58-C57C-4E8A-8888-6ADD532B96D7}
Fri Dec 16 09:22:42 2011 openvpn_execve: CreateProcess C:\WINDOWS\system32\route.exe failed: O sistema não pode encontrar o caminho especificado.   (errno=3)
Fri Dec 16 09:22:42 2011 ERROR: Windows route add command failed: external program did not execute -- returned error code -1
Fri Dec 16 09:22:42 2011 WARNING: potential route subnet conflict between local LAN [143.54.190.0/255.255.254.0] and remote VPN [143.54.0.0/255.255.0.0]
Fri Dec 16 09:22:42 2011 openvpn_execve: CreateProcess C:\WINDOWS\system32\route.exe failed: O sistema não pode encontrar o caminho especificado.   (errno=3)
Fri Dec 16 09:22:42 2011 ERROR: Windows route add command failed: external program did not execute -- returned error code -1
Fri Dec 16 09:22:42 2011 openvpn_execve: CreateProcess C:\WINDOWS\system32\route.exe failed: O sistema não pode encontrar o caminho especificado.   (errno=3)
Fri Dec 16 09:22:42 2011 ERROR: Windows route add command failed: external program did not execute -- returned error code -1

The system could not found the route.exe command.
This windows copy is installed on a different path other than c:\windows .
Looks like the openVPN is not checking windows directory environment variable.

Change History (2)

comment:1 Changed 2 years ago by dazo

Try adding --win-sys env to your configuration. This will become the default in v2.3. See ticket #66 for more info.

Please let us know if this solves your issues.

comment:2 Changed 20 months ago by dazo

  • Resolution set to notabug
  • Status changed from new to closed

Closing as there has been no response from the reporter.

Note: See TracTickets for help on using tickets.