Wingate 5.0.2 sitting behind an ISA Firewall Client

[Skkeletor]

I can not make Wingate to get to the internet through the ISA Firewall Client. I was running Wingate 5.0.2 in order to provide Internet conection to a subnet. After the network admin decided to install the ISA server I couldn't make Wingate to autenticate to the ISA server.
The network admin gave me the ISA Firewall client to mitigate the problem. Although all programs from my machine get to the Ingenet, the subnet that I was providing Internet services to can't get through anymore, even though they reach the Wingate server without problem.
As I see it, it is the Wingate server the one that cannot get through the ISA Firewall Client to the Internet.

I tried but I couldn't find anything to make Wingate aware of the ISA Firewall Client.

Any suggestions?

[ImmediateAction]

To begin with, you are not using the latest verison of WinGate so you should upgrade. And secondly, you need a default gateway.

[Skkeletor]

To begin with, you are not using the latest verison of WinGate so you should upgrade. And secondly, you need a default gateway.

Really? I should agree I need some upgrading. But you should have guessed there was a default gateway defined when I mentioned every other application could get into the Internet but Wingate. Not to mention the ISA Firewall Client I am running.

Here is the (partial) routing table
===============================================
Routes:
Destination..........Mask...........Gateway...........Interface............Metric
0.0.0.0............. 0.0.0.0.......192.168.4.1........192.168.4.27....... 20
0.0.0.0............. 0.0.0.0.......192.168.4.3........192.168.4.27....... 20

Default gateway: 192.168.4.1
===============================================

192.168.4.3 is the ISA server host, 192.168.4.1 is the internet router.

[adrien]

Hi

you've got 2 default gateways there, out the same adapter. That's not normally a good thing, unless there's definitely a router to the internet at each of those IPs.

Does say web browsing from the WinGate machine work through the ISA server?

It may need you to use the WinGate proxies, since those are more likely to be intercepted by the ISA client, than the WinGate NAT traffic.

PS, WinGate runs in a non-interactive account, so if the ISA firewall client was going to pop up a login dialog, you wouldn't see it. You may need to enable the WinGate service to interact with the desktop in your windows services setup.

Regards

Adrien