Client Directly Responsible for High Utilization on W2K SVR

Mar 26 04 10:42 am

Evaluating this product for winsock proxy(ing) between a few subnets on my WAN. Installed the client on 2 servers and both developed the EXACT same problems.

High CPU Util. switching betwee several different processes to the point where the server needed to be rebooted. Ran uninstall and the client applet still appears in Control Panel. << ?? Also, the servers boot SLOOOOOOOOOOOOOOW... now.

I suspect some DLL's have been hammered.

Had to reinstall IE6 (all components) just to unbreak whatever the client install broke. Anybody else seen this issues with the client? If so, any suggestions??

Thanks!

Mar 26 04 11:00 am

What version of WinGate were you running ? (Client installation)

We had a similar problem with very early releases, relating to System Services that needed to be added to the override, but I believe that was in the 5.0 or 4.5.3 range.

Mar 26 04 11:04 am

5.2.3

I downloaded the item online today. As far as I know, it is the latest. I used the same executeable for installing the server, just had to select the option for client.

Mar 26 04 11:33 am

When you install the client, add "WinLogon.exe" and "Lsass.exe" to your list of application. Make sure to set them to Local Mode, because they can cause that form of behavior.

Mar 26 04 11:38 am

Now that you mention it, those were definitely 2 of the culprit services. Do I need to set them as applications on the client or server side and where do I perform that task?

Mar 26 04 11:41 am

On the client side. You should not install WGIC on the WinGate Server.

Open the Client Configuration tool (Either from Control Panel or the Start Menu).

In the Applications tab, you can add applications.

Mar 26 04 11:56 am

Got it. I poked around long enough and found the applications tab. I can tell you that this was a windows 2000 pro workstation NOT server and after following your suggestions here, I experienced no problems. What are the chances that I can put it back on my server, add the applications to the local group and won't experience any problems? Thanks for the help, it's appreciated!

Mar 26 04 12:06 pm

If we're talking OS server vs workstation, the same changes should apply. If you are talking WinGate Server vs WinGate Client, you don't need any changes, just don't run the WinGate Client on the WinGate Server (It's not necessary, and will be disabled if found)