Not disconnecting after xxx seconds of inactivity

[davedixon]

Just purchased and installed Wingate 5.0.10 - on Windows 98SE using an ISDN modem. UK dealer not interested at all in helping us out to get it operational. So here goes:-

WinGate connects only when required (so there is no spurious dialling) BUT once connected it holds the line open for ever...... until we tell the dialler to stop.

There appears to be no activity on the traffic monitor, and a search through all the logfiles shows nothing except the original request to dial, and some ICMP traffic from some TCP/IP addresses close to our ISP's DNS address.

Could this ICMP traffic (every minute or so) cause WinGate to keep the connection alive?

Or have I overlooked something? All help gratefully received.

Many Thanks

Dave Dixon (going grey by the hour!)

[xtreme69]

I've never worked with the dialer before, so take what I have to say with a grain of salt. But, considering the fact that you can find no other source of activity, I would focus on ways to stop or isolate the ICMP activity and monitor the dialers reaction then.

Also, have you gotten the timeout on the dialer to work properly previously? If not, can you test on another line (non-ISDN)? I wish I could help you out more, but I can only throw out thoughts on this topic :) Good luck and be sure to post your solution when you do figure out what's up.

[Nev]

Just purchased and installed Wingate 5.0.10 - on Windows 98SE using an ISDN modem. UK dealer not interested at all in helping us out to get it operational. So here goes:-

WinGate connects only when required (so there is no spurious dialling) BUT once connected it holds the line open for ever...... until we tell the dialler to stop.

There appears to be no activity on the traffic monitor, and a search through all the logfiles shows nothing except the original request to dial, and some ICMP traffic from some TCP/IP addresses close to our ISP's DNS address.

This is either MSBLASTER / WELCHIA [et al] on infected pc's with your ISP, why memo's can't be issued to user's I don't know to clean their machines is beyond me.

Could this ICMP traffic (every minute or so) cause WinGate to keep the connection alive?

Yes found that to be the case and it was quite a problem with a static IP that has 100 or more ICMP hits like above per hour, it would dial within a minute of loading!

Solution was to set specific rules about who could dial, ie users and that at least be assumed for access, then don't dial for any of the IP's in the local network fixed the problem AOK!

Good luck,
Nev.

[neil]

If you upgrade to 5.1 there is an option you can untick that might solve this problem, as we found that some OS's made broadcasts over the dial up that kept it alive. We were (and still do) by default allow these, but if you wish to disable them (in 5.1) then go in to your ENS properties, and under the Routing tab click the Advanced button and UNtick 'NETBIOS name service' and 'NETBIOS datagram service'.

This will stop these broadcasts from happening, and thus let the dialer die normally, as well as prevent constant dialling.

Regards

Neil