Wingate Dialup Monitor erratic display

[john4565]

For the last few releases I've noticed that the Wingate Dialup Monitor does not always display in the system tray of Wingate clients. This leaves the clients with no obvious means to disconnect. The problem can depend on what software is requiring the internet connection, for instance on one client connecting with Internet Explorer 6 will not activate the Dialup Monitor but checking for new email in Office will.

I've just upgraded to version 5.2.3 hoping it may fix the problem but not so lucky.

Has anyone experienced this and is there a solution?

[adrien]

Hi

IE6 did some wacky things in how it uses WinSock.

If you ever ran the network setup wizard on the XP machine, then we have found that if it finds a default gateway to use, then IE6 will not load windows sockets. We can only figure that it uses some other means to connect (perhaps a TDI client)

The WinGate client is a Winsock2 Layered Service Provider DLL. That means it only works with applications that use windows sockets (winsock). Therefore if IE6 is not loading winsock, our client doesn't load either, and therefore it won't kick off the dialup monitor.

You will find also in these cases that IE6 will be using NAT (through WinGate's ENS) for connections rather than the Winsock Redirector Service (you should be able to verify this by temporarily stopping this service in WinGate). Also the traffic used by IE6 would not show up in the dialup monitor.

The only way we have found to get IE6 to load again is by removing the default route. This is the route with network address and mask of 0.0.0.0

you can delete it from the command line by typing

route delete 0.0.0.0

You would also need to remove any default gateway setting from your TCP/IP properties for your LAN adapters.

This is not a recommended solution however, unless you aren't running any other applications on those machines that require NAT access to the internet.

Adrien

[john4565]

Hi Adrian,

Thank you for the response to which I advise:

1) The entire system (Home network of three PC's) is based on Windows 98SE (I know I could have used Windows ICS but I like WinGate).

2) If I disable the Winsock Redirector Service then a Client PC returns an error "No WinGate Servers are responding...".

3) Traffic from the Client does show up in the Servers Dialup Monitor.

4) I am reluctant to remove the default route as to be honest I do not know what other applications are on the Clients that might require NAT access to the internet.

John