Problem with multiple connections in rotation

[dimit16]

Hi all,

I am currently having problems with the multi-connections Wingate feature and I would love to hear suggestions on how to diagnose this issue.

I am trying to use two mobile dial-up connections in rotation. Unfortunately only one connection is used when I browse the internet or download files with multi-part technique. The data-counter on mobile 1 displays constant activity and the data-counter on mobile 2 remains inactive.

I configured the web proxy exactly as explained in this guide: www.asadahmad.com/tutorials/tut_multipl ... ctions.htm .
To summarize these settings, the web-proxy "Binds only to 127.0.0.1 on MS TCP Loopback interface", all two dial-up-connections are added as gateway and "all specified connections are used in rotation". Each connection has "Any gateway" and "Any IP address" checked.

Yet only one connection is used when I browse the web and open webpages with multiple images (this should trigger multiple requests and should use the connections in rotation). Also a multi-part download of a file with a download acceleration only uses one connection (this also should trigger multiple requests and rotation). The data-counter on both mobiles and the data-counter of "windows network status" confirm this strange behavior.
The two mobile connections do work when I use them individually.

Can anyone post some tips to try? I am using windows 7 with latest wingate trial and also disabled my antivirus and the ALG service.
Thanks!

[adrien]

hi

which OS is this on?

Regards

Adrien

[dimit16]

Hi adrien,

I am using windows 7 with latest wingate trial and also disabled my antivirus and the ALG service.
Do you have any suggestions for me to diagnose the problem? Thanks

[adrien]

Hi

Unfortunately due to changes in networking behaviour in Vista and Windows 7 / 2008 server, the gateway selection feature doesn't work properly for dialup connections - this is because the OS refuses to attempt to send packets on what it considers to be the wrong interface, so what you will get is a bunch of errors about network unreachable.

We don't yet have a fix for this problem, in fact unless MS changes this behaviour (we asked) we may not be able to fix it sorry.

[Nev]

in fact unless MS changes this behaviour (we asked) we may not be able to fix it sorry.

Is MS trying to get rid of dial up? // or worse?

[dimit16]

Hi

Unfortunately due to changes in networking behaviour in Vista and Windows 7 / 2008 server, the gateway selection feature doesn't work properly for dialup connections - this is because the OS refuses to attempt to send packets on what it considers to be the wrong interface, so what you will get is a bunch of errors about network unreachable.

We don't yet have a fix for this problem, in fact unless MS changes this behaviour (we asked) we may not be able to fix it sorry.

Thanks for the reply Adrien.
I was suspecting that the issue could be OS-related.
This diagnose does sound logical. One thing though that I don't recognize is "you will get is a bunch of errors about network unreachable".
I didn't see any error of this kind. The second dialup connection is connected fine and is giving no errors, but it is simply not used.

I might try this in WIndows XP then (using vmware or using a dualboot).