Intermitent Page loading failers

[nuanda]

hello

I'm experiencing a problem where occassionally, clicking a link or submit button instantly returns 1) a blank page with no status message, or 2) a Page cannot be displayed error with a status message of "connection failed server or dns error". Refreshing one or more times fixes the problem.

This is especially likely to occur with dynamic web pages like asp, aspx, jspa, or mxps. Disabling the cache had no affect. I had this same problem with an earlier setup, before upgrading my systems, but now it is worse.

I read some other posts here where a similar problem was caused by licensing issues. This does not seem to be the case here. The problems do not result in errors in the Logs. I suspect there is a DNS problem, could someone take a look at my setup and provide feedback?

My Setup
Cable modem is connected to broadband router.
Broadband router is conected to the external NIC of the server and has dhcp enabled.
The server that runs wingate also runs Window SBS 2003 sp1 with the web server on port 80, DNS and AD running.
Wingate 6.2 has DHCP and DNS services disabled,
The clients use WGIC. NTLM authentication is enabled but at present the Everyone group has access. The clients use the server internal interface for DNS.
The DNS resolver has no DNS specified, initially it had the external adapter but this was causing problems.
W2k3 server DNS service is set up to listen on the internal adapter and forward to the external adapter

Thanks
Mark G

[kgoodknecht]

hello

The DNS resolver has no DNS specified, initially it had the external adapter but this was causing problems.
W2k3 server DNS service is set up to listen on the internal adapter and forward to the external adapter

1. Disable the DNS server service in Wingate.(Critical)

2. In the Wingate DNS resolver, enter the IP of the internal SBS interface.

3. On the Win2k3 DNS, listen only on the internal interface, and set the Forwarder to the ISP DNS or to the Router. That is, forward to the router, if the router supports being a DNS proxy. You can test the router by using this in a cmd prompt:
nslookup -qtype=ns . <IPAddressofRouter>