HTTP Error 500 - can't get www proxy working

[munrobasher]

Hi,

We're currently piloting our new AD set-up and I've got around to looking at Wingate. We've currently got Wingate running fine in our old NT 4 domain but I can't get it working in our new AD system. This is the set-up:

o Windows 2003 Server R2
o Server configured as domain controller
o Server also configured as DNS server
o Single network interface connected to LAN and onto the firewall
o DNS forwarding setup on the server
o Server static IP configured through the firewall for basic web activities

You can logon to the console at this server and access the internet, e.g. ping www.bbc.co.uk and load www.bbc.co.uk into the IE7.

It's been ages since I installed Wingate so the configuration is distant memory :-) This is what I've done:

o Installed Wingate with trial license
o Disable ENS as we don't need NAT - our firewall does that
o Linked it to the AD directory of users (can see list of users)
o Disabled the DCHP service as this is handled elsewhere
o Disabled the DNS service as this server is already running DNS as part of Windows 2003
o Changed the WWW proxy port to 81 (as 80 conflicts with IIS)
o Turned on NTLM authentication on WWW proxy
o Added Everyone against policy with user must be authenticated
o The Windows firewall is enabled on this server but I've turned it off just in case

On the client PC, I've changed IE7 connection settings to use VSERVER003 as the proxy on port 81.

On the client, the user can load up our intranet fine. The user shows up in the activity window with their IP address, name and assumed (although it sometimes changes to authentication).

However, when they try to go to an internet site, IE7 reports "HTTP 500 - Internal server error". The log on Wingate shows something like this:

04/21/08 16:17:20 192.168.1.177 Guest 0000000004 Created:
04/21/08 16:17:20 192.168.1.177 rob.nicholson 0000000004 Requested: http://www.bbc.co.uk/
04/21/08 16:17:20 192.168.1.177 rob.nicholson 0000000004 Debug: [www.bbc.co.uk/] Copy to use: SERVER
04/21/08 16:17:20 192.168.1.177 rob.nicholson 0000000004 Debug: WWW Session sending server request in thread 7fc
04/21/08 16:17:20 192.168.1.177 rob.nicholson 0000000004 Error: Caught socket exception in CWWWSession::HTTPProcessRequest() Socket Error 10049 {Thd 2044} [socket #CE4, 0.0.0.0:1601 to :0] - terminating
04/21/08 16:17:20 192.168.1.177 rob.nicholson 0000000004 Traffic 1425 1464 0 0 0s
04/21/08 16:17:20 192.168.1.177 rob.nicholson 0000000004 Terminated exit code 2
04/21/08 16:17:23 192.168.1.177 rob.nicholson 0000000005 Created:
04/21/08 16:17:23 192.168.1.177 rob.nicholson 0000000005 Requested: http://www.bbc.co.uk/
04/21/08 16:17:23 192.168.1.177 rob.nicholson 0000000005 Debug: [www.bbc.co.uk/] Copy to use: SERVER
04/21/08 16:17:23 192.168.1.177 rob.nicholson 0000000005 Debug: WWW Session sending server request in thread fe4
04/21/08 16:17:23 192.168.1.177 rob.nicholson 0000000005 Error: Caught socket exception in CWWWSession::HTTPProcessRequest() Socket Error 10049 {Thd 4068} [socket #C7C, 0.0.0.0:1602 to :0] - terminating
04/21/08 16:17:23 192.168.1.177 rob.nicholson 0000000005 Traffic 342 364 0 0 0s
04/21/08 16:17:23 192.168.1.177 rob.nicholson 0000000005 Terminated exit code 2

NOTE: This server is the R2 flavour of Windows 2003 server which means that many of the normal services may be disabled by the security configuration wizard.

Any ideas?

Thanks, Rob.

[munrobasher]

Just to prove to myself that I can get it working, I've just created a Windows 2000 server in our old domain, drilled it through the firewall, installed WinGate trial and done the same configuration and it works.

There are some posts on here about that socket error.

Cheers, Rob.

[munrobasher]

Such is the power of VMware VMs, I'm going to throw to gether a simple member Windows 2003 R2 server. It'll be the same version etc. but I won't make it a domain controller.

Cheers, Rob.

[adrien]

Hi Rob

10049 is a signature error relating to DNS lookup failures. First thing to do should be to check DNS resolution in WinGate - configuration of the DNS resolver etc.

By default WinGate won't use 127.0.0.1, which is the default DNS server applied to NICs on an AD Domain Controller, so you may need to manually add the actual IP of that machine.

Regards

Adrien

[munrobasher]

Hi Rob

10049 is a signature error relating to DNS lookup failures. First thing to do should be to check DNS resolution in WinGate - configuration of the DNS resolver etc.

By default WinGate won't use 127.0.0.1, which is the default DNS server applied to NICs on an AD Domain Controller, so you may need to manually add the actual IP of that machine.

Regards

Adrien

Hi Adrien,

Where would I add the DNS setting? The current IP config is shown below.

Thanks, Rob.

O:\>ipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : vserver003
Primary Dns Suffix . . . . . . . : testcompany.local
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : testcompany.local

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : VMware Accelerated AMD PCNet Adapter
Physical Address. . . . . . . . . : 00-0C-29-42-87-E6
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.1.42
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.251
DNS Servers . . . . . . . . . . . : 127.0.0.1
Primary WINS Server . . . . . . . : 192.168.1.42

O:\>

[munrobasher]

Where would I add the DNS setting? The current IP config is shown below.

Answering own question - I assumed you meant of the actual NIC itself. The DNS on that was set to 127.0.0.1 (which is what happens when you DCPROMO the first AD in a domain).

I've set it to 192.168.1.42 and nothing happened. So I restarted Wingate engine and that worked.

Cheers, Rob.

[adrien]

Hi Rob

You can also manually enter DNS servers to use in the DNS resolver settings in WinGate itself - save changing NIC settings.

Regards

Adrien

[munrobasher]

You can also manually enter DNS servers to use in the DNS resolver settings in WinGate itself - save changing NIC settings.

Thanks - that worked as well as is more "contained" if you see what I mean.

Cheers, Rob.