setup wingate 6.0.3

[sahon]

we have WinGate 6.0.3 Windows Server 2003
server has 2 network cards
local adapter has adress 192.168.110.4 mask 255.255.255.0 without gateway
external 10.24.99.211 mask 255.255.255.240 gateway 10.24.99.209
we connect to internet through VPN connection
server has route:
route add -p 81.25.32.15 mask 255.255.255.255 10.24.99.209 metric 1
81.25.32.15 is provider's internal adreess and we need to connect it without VPN connection
each LAN client has static IP adress 192.168.110.* with gateway 192.168.110.4

how can I setup wingate server/configuration so each client can access Internet through VPN and provider's resource 81.25.32.15 without Wingate Internet Client program?

[genie]

What seems to be a problem then? NAT should pick up tihs configuration if Wingate adapters are set properly (external/internal). If you try connecting to an external machine through Wingate from one of the client machines, can you see any NAT traffic reported in Gatekeeper?

[sahon]

What seems to be a problem then? NAT should pick up tihs configuration if Wingate adapters are set properly (external/internal). If you try connecting to an external machine through Wingate from one of the client machines, can you see any NAT traffic reported in Gatekeeper?

actually I have 3 adapters in Wingate
1. LAN with adress 192.168.110.4 - wingate shows it as internal
2. adapter with adress 10.24.99.211, it provides connection to provider - wingate shows it as internal
3. VPN connection - connection to internet - wingate shows it as external

with Wingate Internet Client program everything works, but I do not want to use it, is it possible to get rid of it?

[genie]

Sure - have you tried using NAT from a client?

[sahon]

what I should I do? I tryed to add route on a client to 81.25.32.15 through gateway 192.168.110.4 - it didn't help, because I already have this gateway as default. I forgot to say that I have access to internat resources (without Wingate Internet Client program) but I do not have access to 81.25.32.15

[genie]

You don't have to add any routes on the client - the default route should go through Wingate. Wingate router itself will take care of this 81.xxx route if there are any packets to this IP address. When you connect from a client machine, can you see any NAT connections reported by Wingate in gatekeeper activity monitor?

[sahon]

You don't have to add any routes on the client - the default route should go through Wingate. Wingate router itself will take care of this 81.xxx route if there are any packets to this IP address. When you connect from a client machine, can you see any NAT connections reported by Wingate in gatekeeper activity monitor?

I can see:
NAT: TCP Connection to 64.12.28.140:5190 - seems ICQ
NAT: TCP Connection to *.*.*.*:80 - Web
but cannot see anything to 81.25.32.15

[sahon]

do I need to setup adapter with adress 10.24.99.211 as external?

[genie]

It depends - if you want to use it as an outbound adapter, then yes, you have to.

Now, back to this 81.xxx address - why do you expect to see it? Is there anyone on the client machine establishing a connection to this IP address?

[sahon]

It depends - if you want to use it as an outbound adapter, then yes, you have to.

Now, back to this 81.xxx address - why do you expect to see it? Is there anyone on the client machine establishing a connection to this IP address?

I'm trying to open web page with this IP adress DNS resolves it correctly, I can see this IP in ping, but ping cannot be established

On the server ping can be established

[genie]

Say, your initial post says that this route went through 10.24 adapter - have you tried marking it as external then?

[sahon]

Say, your initial post says that this route went through 10.24 adapter - have you tried marking it as external then?

yes with external it works, and with DMZ!!!!!!!!!!
maybe DMZ is more correct?

[genie]

Judging by your setup I'd say it is - since your primary internet connection goes through VPN.

[sahon]

Judging by your setup I'd say it is - since your primary internet connection goes through VPN.

it was very confusing that with Wingate Client program it worked
thank you for your help