|
|
Pascal Deliot <pascal@xxxxxxxxxx> said: > I've had similar problem. > Try to run the command "ntsh.exe" on a command line. Then if you have an error or a crash, try to find the dll involved in the crash (for me it was the "winsmon.dll" Dll). Then got into the registry at HKLM\Software\Microsoft\NetSh and remove the coresponding value (in my case "winmon=winsmon.dll"). > > Then try "netsh.exe" on the command line again, the will no longer occur. Then try OpenVpn again. This have sold the problem for me. It does seem that the netsh command (which is part of Windows 2K and up) has some problems. Though I've never had a problem with it on XP SP 1, it doesn't work as well on Win2K and I haven't tried it on 2003 yet. The next beta will provide alternative, non-netsh methods of automatically setting the TCP/IP properties on the TAP-Win32 adapter. As a workaround, in 1.5b9 you can specify --ifconfig-noexec in addition to --ifconfig, then set the TCP/IP network address and netmask manually. James ____________________________________________ Openvpn-users mailing list Openvpn-users@xxxxxxxxxxxxxxxxxxxxx https://lists.sourceforge.net/lists/listinfo/openvpn-users |