Major Slowdown/Busy

[Hopkinsmailing]

We installed build 995 on an Advanced Server 2000. We have the icon for the internet connection NIC card showing in the desktop tray (lower right corner). Both send and receive are constantly lit and the entire network is complaining about the access time to the internet. We have a T1 and prior to the upgrade we were moving at T1 speeds. If I shutdown the wingate engine the NIC card stops being busy but the network can't get out obviously. If I disable the internal network NIC card to ensure no users can send traffic and then restart the Wingate engine the internet NIC card goes busy again. I've looked at the Task Manager Performance screen and Wingate is maybe 3-4% with system idle being the balance. What would be causing this phantom traffic and slowdown?

Rob H

[Pascal]

Disable the dead gateway detection in ENS.

[Tinchev]

I am running WG on windows XP pro but after few hours the CPU/RAM usage engine on my WG engine goes about 95% When I stop the It everythink goes normal but when I start It the usege goes high again. I can't even login through the GateKeeper. I have two network interfaces - one public and one internal. I connect to the internet through the public via VPN connection. Please help.

[adrien]

Hi

In task manager, is it WinGate.exe that is consuming all this CPU, or another process (i.e. svchost.exe, or kavss.exe)?

Are you using Kaspersky AV for WinGate? If so, do these times coincide with scheduled update times for Kaspersky AV? We have a known issue with KAV updates when the system is busy, we are testing a fixed SDK from Kaspersky Labs for this.

Regards

Adrien

[Hopkinsmailing]

Disabling Monitor Dead Gateway solved the problem. Thanks. I could not find this in the help file. What is a Dead Gateway?

Rob H

[Tinchev]

Thank you for the replay. No I am not using KAV and WG is consuming all this CPU and RAM. When I try login through the GateKeeper the CPU usage splits between the wingate.exe and wgengmon.exe about 50% each. Do you have any idea where the problem is? By the way I am using NOD 32 antivirus system as antivir scanner and not using any other additional firewall.

[Pascal]

A dead gateway is one that has gone down. For example, you connect to the Internet through an ADSL router. Your WinGate machine is not aware of the state of this device beyond it's control. Somebody in your office accidentally flicks a power switch, which turns off the router. Suddenly, your internet connectivity is gone. That then turns the router in a dead gateway. WinGate becomes aware that it is 'dead' and unreachable, and then will not attempt to use it. If you had a secondary gateway in the form of say, a dial-up modem, WinGate would switch to using that (If allowed).