Inserting Wingate without changing Cisco router

[mark_f1man]

Haven't used Wingate for a while but am looking at the possibility of inserting it into our existing system. Want to find out if it is possible without changing the configuration of the router (so I don't have to get our IT company involved). Basically want to find out what is happening with our Internet connection using Wingate. Got IT company to turn on IP accounting in Cisco router but wasn't particularly useful in terms of the data it provided.

We have Server 2003 SBS and a Cisco 800 router. They are on the same network at addresses 192.168.1.10 (server) and 192.168.1.253 (router). In terms of incoming traffic there is SMTP, Outlook Web Access and Outlook over RPC/HTTP to the server. There is also a VPN connection to the Cisco router which I think does RADIUS authentication to the server. It allows file access to the server, and remote desktop access to a terminal server pc (192.168.1.4)

So I guess the main question is - would it be possible to insert a Wingate PC with 2 NICs inbetween the network and the router, do some setup in Wingate and not have to change the configuration in the Cisco router? Note: I should be able to manage any changes in the server, such as default gateway, DHCP settings etc

[adrien]

Hi

sounds like it should be possible.

You currently have

Internet -> Cisco -> SBS -> internal

and you want

Internet -> Cisco -> WinGate -> SBS -> Internal.

if you don't want to change the cisco, it will be already configured to forward incoming connections on the ports you mentioned through to the SBS server, but this is 99.9% likely done by IP address, in which case you'll need to give the cisco-side interface of the WinGate machine the IP address that the SBS server had, allocate the SBS server a new IP (in a new subnet range), and give WinGate's SBS server an ip in that range. Then you'll need to do the port forwarding for inbound connections through WinGate to the SBS server.

default gateway for the SBS server will then be WinGate's IP.

Adrien

[mark_f1man]

Thanks. It may be a little trickier than you suggested. Our network is actually:

Internet -> Cisco -> Internal

and we want

Internet -> Cisco -> WinGate -> Internal.

The SBS is just one computer on the internal network. We have a group policy to setup the proxy settings on the client PCs to be the SBS server, but if you manually turn the proxy off (or use Firefox etc) then the internet connection goes direct out through the router.

I can't really think of an easy way of doing this without changing the Cisco router. Maybe insert an additional Ethernet/Ethernet router but it all starts to get quite messy.

[adrien]

I still think it should be possible. Just give the cisco-side interface in Wingate the IP that the old SBS server had.

then the port mappings for the cisco will still work - pointing through to WinGate which you can map through to the SBS server.

[mark_f1man]

If I allocated the SBS server IP (192.168.1.10) to the cisco-side interface in Wingate wouldn't I then have to change the Subnet of the main LAN? Currently this is 192.168.1.x. If I didn't then both interfaces in the Wingate box would have 192.168.1.x addresses.

ie. I would have:
SBS Server 192.168.1.10 -> Wingate LAN-side (say 192.168.1.250) -> Wingate cisco-side (192.168.1.10) -> Cisco (192.168.1.253).

I wouldn't think that would work. Which leaves me with the option of either changing the Cisco router, or changing all the LAN side IP addressing including printers, and we also have a TelstraClear Private IP router. They have fixed 192.168.1.x addresses.