by adrien » Aug 08 04 4:56 pm
HI
Have you tried any other internet application to see if they can use the WinGate Client?
With IE6 onwards, MS started doing some really weird things. The WinGate Client is a Winsock 2 Layered Service Provider DLL, which is loaded by Winsock in the context of any winsock application.
If you have ever run the network setup wizard and are using IE6, then we have found that IE6 stops loading our DLL, which I guess means it isn't using winsock (????). We have found in these cases if you remove the default gateway setting from that client machine, then IE6 will then start using the WinGate client again.
Other more obvious things to check are that the WinGate Client is not configured for IEXPLORE.EXE to be local only access, or that if you are using centralised configuration on the Winsock Redirector Service, that the proper settings are in there so that IE will use the WinGate Client.
Adrien