Socket Error 10049 {Thd 2712}

[winvista]

Socket Error 10049 {Thd 2712} [socket #C34, 24.209.23.182:50101 to :0]

only threads i can find in search is about this error has been fixed.

Windows Vista SP1

[genie]

Hi,

What version of Wingate are you using?

[winvista]

free trial of whatever is on the download page. WinGate6.5.1.1203-USE.EXE

[adrien]

This error normally implies a DNS lookup failure.

Have you checked that DNS is working in WinGate? There are several ways to do this, depending on whether you are using the DNS service in WinGate or not.

From a client computer that uses WinGate for DNS, try pinging a site. If ping reports an error such as "hostname lookup failed..." then you've got a DNS issue.

Are you using Active Directory on that network?

Regards

Adrien

[winvista]

my test client is the same pc the server is installed on.


if i tell it to use any connection it works fine.
if i tell it to use connection A i get a socket error.
if i disable connection a and tell it to use any connection it works fine.
if i re-enable connection A,disable connection B then tell it to use any connection it works fine.
but if i tell it to use exclusively connection A or connection B it fails.

if we roll this out at work we will want connection a to be exclusively for non web-surfing. for net applications.
we want connection b to be for web surfing so we will use wingate to force all web surfing onto connection b.


except for the socket errors.

[adrien]

Ah, ok you're using Gateway settings to specify a gateway ("gateway selection").

We'll have to re-check this.

Make sure you're not running the windows firewall as well, this breaks gateway selection.

Regards

Adrien

[winvista2]

im the same guy i just lost my password lol
i got vista firewall turned off here is a screenshot.


well
not quite i need 5 posts

[winvista2]

4 posts

[winvista2]

fuckit.

i have firewall disabled.
i have no firewall installed.

[adrien]

we retested this

We found a problem if a connection is a dialup one - it seems to work fine for LAN cards though... is one of those connections a dialup?

Regards

Adrien

[winvista2]

none of the connections are dialup.

is there any known problems with vista x64 ?

[jasona]

Yes that sounds like it could be the problem. There is currently no version of WinGate that works with 64 bit Vista

http://wingate.com/download/wingate/download.php
6.5.1

Adds support for Windows Vista, and Windows XP64, removes support for Windows 95, 98, ME and NT4. Resolves a number of bugs.

Supported OSes

Windows 2000
Windows XP (32 bit)
Windows XP (64 bit)
Windows 2003 (32 bit)
Windows Vista (32 bit)

[adrien]

we're working on Vista 64 support at the moment - it works, but driver installation is the main problem.

Dialup can also include things like PPPoE DSL modems. Anything that you have to "connect"

Anyway, looks like the good people at MS decided to break routing on Vista.

If you have a dialup connected, and also a LAN connection to the internet, it ignores metric in routing, and always sends traffic out the dialup (directly contravening the basis of metrics in routing). I wonder if MS sees this as a bug (as we do) or a feature. It also now seems to try and verify that the source address of the connection matches the dialup interface. This irretrievably breaks WinGate gateway selection where dialup connections are involved.

[winvista2]

neither of the connections are dialup or ppoe or isdn.
no login required

they are time warner provided t1 lines.

glad to know its x64 and is being worked on.
i have another question.
our vista has IIS ripped out of it.
will that be a problem with wingate at all?

[adrien]

we have the driver installer working now, just going to be validating it next week.

No problem re IIS, we don't use any parts of it.

Cheers

Adrien