Problem with wingate&lan accessing internet

[Kedryn]

Scenario:

I have a wingate machine (+ mdaemon) set up as a gateway for LAN user to internet.
I've several port forwarding from internet->lan machines for some services
the Wingate machine has 1 lan ip (that is the default gateway for lan computers) and 3 public ip (same netmask) over another ethernet card.
My setup is in a AD domain, and i've set up the AD controller to forward dns queries directly to ISP dns servers, and wingate machine > AD controller.
I've open port 25 in wingate firewall to let MDaemon receive smtp from internet and forward them to the internal Exchange server.
I also use the wingate WWW proxy with "intercept calls"

I've tried this configuration both on a win 2003 machine some years ago (don't remember,but i think it was the 6.2 of wingate)
and now i'm retesting it on a WinXP sp3 (with patched max half-open connections and without) on different machine with different network cards

but the problem is always the same

This setup works like a charm... till it stops forwarding packets. either after few minutes from a boot, or several hours, or near a day, or even after few days when i'm lucky.
Wingate services seems to not have problems itself, but doing some trace from the wingate machine seems to have a lot of timeouts. AD controller opens hundred of DNS queries (visible from gatekeepr) that go timeouts, and even browsers timeouts.
The strange thing is that if do a trace at the same time in another machine with another public ip of the same subnet, i get no timeouts.

And this happened in the past on the win 2003 machine same as it is happening now on the win Xp machine.
Even the Mdaemon sto receiving mails. Only way to get all back to work is reboot the wingate machine.

Marco
(sorry for my english)

[Kedryn]

A thing i need to add is this:
from the wingate machine, when the problem arises, i can still ping machines on the lan
but i can't ping the router via external interface.
The router is still alive and working, ebviously

[sysneticlabs]

hi,

Does your problem same as this one, related in this post ? It talks about "timeout" and requires V6.5.3 to fix it...


=> viewtopic.php?f=12&t=39633


I m currently testing a plateform on MS Windows 2008 server, and i experiment BOSD until I install latest and "hidden" V6.5.3...

Since that time, no problem at all...

Wich version of Wingate do you used, it is not written in your post ? WinGate 6.5.2 (Build 1217), , "latest" written here ?

Let us know....

Pascal

[Kedryn]

On the win 2003 i tested the 6.2.1 1133
on the xp i'm testing the "hidden" 6.5.3 that i found earlier in the post you mentioned
my problem is similar to that one, so i removed the www proxy and used nat (dns was already using nat), but nothing changed
now i have a ping -t on a internet address
i saw timeouts (and no more Lan > internet) 3 times during last hours... i did a "repair" on the external network card, and immediately the timeouts stopped and lan clients were able to navigate again

i think i'll install the 6.5.3 on the win2003 to check if it is a faulty network card problem.. but if it is, i have another problem on the xp machine then

[Kedryn]

I've some news regarding my problem
i reinstalled the win2003 with wingate trial...
for simplicity i omitted the fact that both xp and 2003 machines had 4 network card, one for the lan, and 3 for 3 different connections (2 hdsl and one adsl) where i was trying to distribute the internet trafic.

Now.. the 2003 machine had the same problems of the xp machine, till i disabled 2 of the 3 internet connection, leaving only the 6mb hdsl up.
since then ( a week) the connection never went down again.

Maybe there is some problem using multiple external network card, that sometimes go with wrong gateways, or something similar?

[Kedryn]

So? no help? no requests for more info? nothing at all?

[logan]

Can you check if the Application Layer Gateway service is enabled in your operating systems? This Windows service can mess with WinGate's gateway selection where multiple default gateways are involved.

Also, does the WinGate computer have multiple Internal IP addresses? I.e. IP's on the same local subnet where the clients are located?