Barew!
I think all this is part of what M$oft calls "different behaviours" of programs installed.
What happened to me was the following:
I have a small home network with 4 PCs, all having Internet access through one of them, let's call it Comm, using Wingate v5.0.10.848 without VPN, and not ICS.
A couple of weeks ago I've installed SP2 on Comm, and besides some little annoyances (about Windose Firewall, and automatic updates, very good for MS, but not for me) which I bypassed easily, everything went smoothly.
So I decided to install SP2 on a second computer (call it Things). Installation successful, bypassed the little problems already known from Comm, and her I go to checking the Internet connection. The Wingate client couldn't find the server. Don't worry! Uninstall and re-install! No chance! Received a message stating that while I had ICS and/or Windose Firewall running (I had disabled the last one and hadn't touched in ICS's configuration when installing SP2). Managed to de-activate ICS in Things, and install Wingate client. Surprise!
Wingate client is unable to see the server, and worst... I've lost the local network connection.
So I go back to SP1 in Things (made an image with Drive Image before "upgrading"), so that things will run normally again... without any "different behaviour"...
I'm waiting for seeing if some newer version of Wingate could behave as Gate$ wants!
Cheers!