Wingate post 5.1.0 reboots machine

[entropy]

I had a problem where Wingate 5.1.0 and earlier worked fine on the machine, but those after rebooted the machine shortly after startup (basically when the engine monitor icon should have turned normal - a little after going yellow).
I discovered that newer versions do work, but only if I remove one NIC (whichever, I think). At the moment there are 3 of them (physical NICs: nVidia, 2xRealtek 8139), 1 firewire conn (seldomly used) and 2 backup dialup conns. VMWare w/network support is installed (2 more conns). Two of the real NICs are joined in a bridge (WinXP Pro).

Has anybody seen this before and/or have any tips on how to fix it (except renouncing the physical NICs?)?

[entropy]

to all you 14 (and subsequent) viewers:

It's ok, you can post.. really! <g>
It's just a keyboard.. it doesn't bite... ;>

[genie]

It can be VMWare that gives this behavior - try disabling/uninstalling it if you can.

[entropy]

done that with two or three versions that came after it - no dice (then given up...). the strange thing for wingate might be the bridge...

[genie]

Aye, I actually thought that VMWare created a bridge for its internal pleasure...

[entropy]

hmm, might be - although it doesn't show up as the win xp one (two of the real cards are linked in a bridge - maybe the fact that they're different contributes to all the fun...). i tried with the 2 VMWare thingies disabled and same prob...