|
|
On Wed, 8 Oct 2003 23:06:25 -0000, "James Yonan" <jim@xxxxxxxxx> wrote: > Jordi, > > I'm sorry to hear about your bad experiences trying to uninstall the Tap-Win32 > driver. I've never seen this kind of problem before, Neither have I (Win2000 SP4, using it on server as well as pro). On one machine only, I had frequent problems with the TAP driver seemingly locking up. Strangely, it got solved by installing another firewall at that location (I installed that firewall at home for testing, and now the problem occurs there). When it occurs, restarting the TAP driver and then OpenVPN (in that order only) fixes it. Restarting the firewall or even reconfiguring it so everything is fully open doesn't make any difference. > though my general > impression so far has been that Win2K is not as robust as XP when it comes to > dynamic networking, i.e. loading and unloading drivers without an intervening > reboot, and changing driver properties on the fly. The problem is that the > networking models for both Win2K and XP look the same on paper, but in > practice there are a lot of undocumented differences. For example, on XP you > can install the driver and immediately begin using it. On Win2K a reboot > appears to be required. To make things even more complex, different service > pack levels often show different behavior. I have OpenVPN running on a Win2000 Pro SP4 without a reboot after installing the driver. It's been upgraded from beta 6 to beta 8, also without a reboot. Apart from the downtime for the upgrade, it has kept the tunnel up for about two weeks now. On my other machines I always rebooted just to be safe, especially after I had the freezing TAP driver. ____________________________________________ Openvpn-users mailing list Openvpn-users@xxxxxxxxxxxxxxxxxxxxx https://lists.sourceforge.net/lists/listinfo/openvpn-users |