wingate 4.5.2 ADSL socket errors

[asciipixel]

I have wingate 4.5.2 and have it set up as a proxy to handle for there surfing ….

My machines Network config is

NIC 1 = Internal IP – 192.168.76.1
NIC 2 = ADSL IP – 192.168.0.203
NIC 3 = 64k LEASE LINE – 209.212.104.51

When I put connections (Interface) via the 64k Lease Line the proxy is fine no errors and all goes
well slow but ok.. the second I put anyone through (interface) the ADSL ROUTER connections they start getting socket errors
randomly and it starts with one or two and then it get’s to a point where ever second site comes up as a 500 or
socket error even tho the line is up and working 100% …

Do you have any idea what it is ?

[adrien]

WinGate 4.5.2 had a problem with the DNS resolver. This was the first version released with our own in-built DNS resolver, and it ran out after a while.

Your 4.x key will work in the latest version of WinGate however, so you should probably upgrade to 5.0.10

Adrien

[asciipixel]

these connections are proxy connections not NAT ... the connection are set as follows :

Binding Interface
192.168.76.8 192.168.0.203

so they come via a local lan ip to the first NIC and then get told to go out the ADSL Nic to get out to the net :)

[adrien]

Yep, it still uses WinGate's internal DNS resolver for the proxy to look up the server names to connect to.

Adrien

[asciipixel]

So how do I fix this ? ... basically at the moment whenever I set anyone up via the 64k link it all runs 100% fine but the second I set them via the ADSL Router give me randomly tons of these

Socket Error
Connection to Remote Host timed out

[adrien]

fix -> upgrade... Wingate 4.5.2 had DNS issues..

You can use your existing 4.x key, so it won't cost you anything.

[asciipixel]

I have upgraded to wingate 5.0.7 build 826 and I still get the same issues :) ... what do I do now ?

[adrien]

Did you email me about this issue as well? If so how did you get on with your route table?

I am picking that in order to use your DSL, then your default gateway needs to point to the DSL modem, whereas to use the leased line, the default gateway would need to point to the next hop router at the other end of your leased line.

If you have 2 default routes, then windows or WinGate router gets quite confused.

In fact, if you have the WinGate option "support multiple default routes" then probably that will stop WinGate from being able to use the DSL modem as a gateway, since the next hop IP address will be a private address, and therefore WinGate thinks it is not a suitable next hop to access the public Internet.

[asciipixel]

I have emailled you ... check the attachement :) ....

[asciipixel]

Did you get my ENS screen shots ... ? and what must I change ?

[adrien]

OK, what it comes down to, is you need to decide which interface you will use, and then set up your default route accordingly.

This will mean removing the default gateway entry in the TCP/IP properties from either the leased line interface, or the NIC that is connected to the DSL modem.

[asciipixel]

if I take the default gateway out of my lease line tcp/ip ... will it affect how people connect via that interface via Wingate ... basically how I work it is all surfing goes via ADSL and all ftp etc goes via my lease line ...

[asciipixel]

Just tried removing the gateway from my lease line NIC and the ftp I set up on wingate to go via that interface doesn't work .. any ideas?

[adrien]

When you say "set up WinGate to go via that interface" what do you mean? Do you mean set the interfaces tab for the proxies to connect out over a specific interface?

[asciipixel]

Hi there ...


I have sent u an email with screen shots btw if u want to chat to me on msn I have emailed u my MSN address :)