Unbinding Services Problem

[GSC]

Sorry for the long introduction...

We have had instances where Wingate unbinds its own services. An example of which would be where the user moves their PC, then turns it on with the network cable unplugged. This causes Wingate to unbind, and even though they later re-connect the cable, the damage is done and no one other than the Wingate user can use the internet etc.

I think the reason for this is Media Sensing. This is a new feature in W2K/XP that allows the workstation to automatically detect whether it is connected to a network or not. If not, then is disables the IP stack. This allows you to move from one network point to another without requiring a reboot/release/renew type cycle. If that sort of thing really floats your boat, more info can be found here : http://support.microsoft.com/?id=kb;en-us;Q239924

Firstly, does this sound pausible?
Secondly, I'd like to be able to stop this unbinding by somehow locking down the Wingate settings (want to keep Media Sensing active). Sort of like making them read only. Can this be done?

Any advice would be appreciated.

[adrien]

Yes, this is indeed what happens.

When WinGate starts up, it checks all its bindings, if one is non-existent, it removes it.

We are working on a dynamic binding system to get around this issue, in the meantime, the best way around it is to set WinGate to start manually, then only start it when the network interfaces are available.

Adrien