wingate/WGIC performance issues

[midnightbomber]

I am currently running wingate 6.1.4 on a P4 2Ghz w/512 MB DDR and have been experiencing performance problems using the WGIC since I first began using it almost 2 years ago. Multiple wingate upgrades later the performance is still an issue. Using NAT is relatively quick but using WGIC slows internet performance on client machines to a crawl.
In addition, the WGIC interferes with some applications which require local network access even after we have removed them from WGIC using the exception list (set for local network access for the affected application). In most cases we have to disable the WGIC when we need to use those affected applications.
I need to improve the performance and resolve the WGIC issues (or get an acceptable replacement which provides transparent authentication) or I will be forced to change my internet sharing application.

[adrien]

Hi

thanks for your comments. We have seen a number of problems with the WGIC over the years but I wasn't aware of a performance issue.

the only overhead for normal TCP-based protocols should be the initial connection, since all the WGIC does from that point is redirect the connection to the WinGate server which then pipes it through to the desired end server.

We have plans for a different type of hooking software as well which should relieve some of the issues of Winsock2 layered service providers (old and clunky MS interface that the WGIC uses).

I'm wondering what the performance hit that you are taking is though. For instance is the performance noticeably different for a WGIC client for web surfing than for going via the WWW proxy with WGIC diasbled?

Or is it an initial hit to connect then it's fine. In which case there could be some DNS issue that's slowing things down - WGIC requires working DNS on the client, a bad DNS settup can add a delay to all lookups and will show as a connection delay.

Adrien