ICQ disconnecting with 6.1 & Problems with network tab

[JensL]

Hello,

i've used Wingate 5.0.3 and updated to Wingate 6.1

Now ICQ Lite 5.0 is regularly disconnecting. Is there a timeout value?
I'm using a wingate as nat gateway with an isdn connection to AOL.
Connection with irc client to irc network is stable. MSN Messenger is also stable.
DHCP ist not used, Service is disabled, ips are fixed.
OS: Win XP Pro SP2
Configuration: Exteral ISDN Connection to AOL
Internal: Wireless Adhoc Network over USB adapter.

Another problem is that the network tab in gatekeeper is automatically refreshing the connection list control very often. So if there are more dial up connections than can shown you need to scoll down. But you can't scroll down because its automatically refreshing and so the focus is back on the first row.
Workaround is using full screen, but still if i had more dial up entries it wouldn't work.

The refreshing is also a problem if you want to change the the automatic detection of internal or external to internal or external. Each time it is refreshing the radio box is going back to automatic, so you have to be very fast to change it.

Another question, in the details of a connected isdn dial up connection a mtu value of 1400 is shown. Is this correct? Aren't aol connections on a mtu value of 536?
Same on the Wlan connected to the wingate server. I set MTU to 536 because of a black hole problem. But Wingate shows 1400. Other tools show 536.

[adrien]

Hi

couple of things.

1. Minimum MTU that is supposed to be supported by any interface is 576, so WinGate may be ignoring the setting that says it is 536, and using information it got from the miniport driver etc.

2. I believe you can set your MTU for dialup connections to larger values if you like - PPP negotiates that with the dial-in host. Normally it is best to stick with 1500 if you can, since that prevents problems with fragmentation of LAN traffic that is translated.

3. We don't recommend having a lot of dialup connections - if you have any you don't use, we recommend you delete these.

4. Wireless connections can often disappear and reappear. This can be due to local radio path interference etc, people walking around the room. With Win2000, XP or later, if a wireless connection goes out of range, the network interface is torn down, and any open connections on that interface are closed. You may find this is causing your ICQ sessions to disconnect.

Finally a couple of questions - how does ICQ connect? Is this through NAT or SOCKS?

Adrien

[JensL]

2. With Wingate 5.0.3 i've had to adjust the mtu value to avoid a black hole problem. I've determined the value 538 with "ping -f"
see http://support.microsoft.com/default.aspx?scid=kb;en-us;q314825
Believe me, AOL Isdn connections have such a low value.
To avoid this problems i've set the value of 538 on all clients and the server.

3. Shure its a solution. But it is still a bug in UI programming. I know that is easier to write a complete refresh than an update on each value. It isn't a real problem only a bit annoying.

4. Wlan can be torn down. But this isn't the cause for icq disconnecting. IRC and MSN Connecting aren't aborted. A ping -t to an internet server also shows no signs of a interuppted connection when the icq connection is aborted.
Are there changes in the timeout values of the nat-driver from 5.0.3 to 6.1.0?

ICQ is configured to use the "with firewall and without proxy connection".
Netstat shows a connection from icqlite.exe to the aol server.
So it is connecting through nat.