Bridging internet access

[square]

Hi,
In relation to http://forums.qbik.com/viewtopic.php?t=1493 the problem is still the same - I have posted in the above thread. I've started a new thread because I don't think erwin or any other wingate staff spotted my reply in the old one!


The problem is still the same. Our server is running Windows 2000 Server and we are trying to bridge a trial network we are running with our main network, so that the trial network can gain access to the internet. The wingate machine has 2 NICS configured with static IP addresses relating to each network as follows.

The main network NIC is the network connection that has the router and internet access on it.
IP: 10.73.32.105
Subnet: 255.255.252.0
Gateway: 10.73.32.1
DNS: 212.219.82.4
and the proxy server in internet explorer is set to proxy.lancsngfl.ac.uk

The NIC for the trial network is
IP: 192.168.1.4
Subnet: 255.255.252.0
I have left the gateway and DNS blank.

Then I have got a WWW Proxy Service set up in wingate to use a cascaded proxy server - proxy.lancsngfl.ac.uk.

All the machines on the main network can access the internet when the gateway, DNS and proxy server is set as 10.73.32.105. But on the trial network when i set the DNS, gateway and proxy server as 192.168.1.4 the requests just appear in gatekeeper as http://
This is even after trying the suggestions listed in the first thread.

Thanks

[n0ticer]

square,

i cuddnt help too much, i'm no expert but i'd like to make a try...

Then I have got a WWW Proxy Service set up in wingate to use a cascaded proxy server - proxy.lancsngfl.ac.uk.

have u tried running additional WWW Proxy service on different ports and cascade it to e.g. proxy.lancsngfl.ac.uk port:85 ?

i am also maintaining two class c subnets, 192.168.0.1 and 192.168.1.1

server :
WWW Proxy 1 is bind to 192.168.0.1
WWW Proxy 2 is bind to 192.168.1.1

nic 1: 192.168.0.1
nic 2: 192.168.1.1
sm: 255.255.255.0

workstations for staff:
browser: 192.168.0.1:80
gateway: 192.168.0.1

workstations for guests:
browser: 192.168.1.1:85
gateway: 192.168.1.1

i know i cud use a single card for this but i dont want to revise the existing setup.

nic 3: connected to isp

tnx

[square]

Nope, this still doesn't work. Requests from the trial network are still only being displayed in gatekeeper as http:// I'm sure it's got something to do with the DNS but I don't know what.

Any more help greatly appreciated.

Thanks

[erwin]

Hi there

Sorry for not reply sooner.

I take it the router has its own internal IP address, (10.73.32.1)
(I see you have it set as the Gateway on the main LAN NIC)

The main network NIC is
IP: 10.73.32.105
Subnet: 255.255.252.0
Gateway: 10.73.32.1
DNS: 212.219.82.4

You have set the DNS to an External IP on this LAN NIC interface (212.219.82.4) but this should also be the Internal IP address of the router. (10.73.32.1) as the Gateway is set to.

This way the DNS requests made by clients to WinGate will be forwarded to the router for resolution. Which will allow it to resolve the Cascaded proxy server domain name "proxy.lancsngfl.ac.uk" to an IP address.

See how you get on, and let us know.

Regards
Erwin

[square]

Hi,
This hasn't fixed it - in fact its made it worse. When I set the DNS on the main network NIC to that of the router nothing can gain access to the internet - not even the wingate machine itself. When the DNS is set to 212.219.82.4 the wingate machine and the main network can gain access to the internet. It's just the trial network that is having problems bridging through the wingate machine to get to the internet. All the requests from the trial network just appear in gatekeeper as http:// wheras the ones from the main network are working fine.

Matthew