Windows 2003 Release 2

Nov 24 07 5:13 am

We're currently running Wingate very happily on an NT 4 server but we are currently piloting Wingate on Windows 2003 Server R2. The R2 version of Windows 2003 locks a lot more down by default.

WinGate is installed (without ENS as we don't use that part), DHCP service disabled (we use Windows own DHCP) and I've changed the www service to port 81 otherwise it conflicts with IIS running on port 80.

But it's not working - clients can't access the internet. I suspect it's the firewall. In fact, I know it's the firewall as if I turn it off (the W2K3 firewall that is), the clients can get to the internet.

So the firewall needs tweaking. Should I do this be opening up TCP port 81 or by adding the Wingate executable as a program? When I installed the problem, the firewall "block, unblock or ask later" prompt appeared and I said "Ask later" as I didn't think the install program itself needs firewall access.

Cheers, Rob.

Nov 24 07 10:32 am

If you are planning to use Wingate firewalling facility, then you are better off just switching Win2k3 firewall off altogether. Otherwise, you have to open all the ports Wingate uses for inbound connection and allow Wingate to establish outbound connections in W2K3 firewall config.

Nov 27 07 1:05 am

genie wrote:If you are planning to use Wingate firewalling facility, then you are better off just switching Win2k3 firewall off altogether. Otherwise, you have to open all the ports Wingate uses for inbound connection and allow Wingate to establish outbound connections in W2K3 firewall config.

We won't be using the Wingate firewall - we'll be using the Windows 2003 one as it's now too tightly integrated in with the Windows 2003 Security Configuration Wizard.

Cheers, Rob.