icoleman.uk
Member
Hi,
I'm having a slightly annoying issue with our web portal/secure gateway setup.
First let me explain what we have.
On our LAN we have a Windows 2003 R2 server which is running pretty much everything for our 2X solution. It has the TS agent, Publishing agent, Secure Gateway as well as IIS6 & the Cloud Portal on it. I do plan to split these up later but we are evaluating the software at the moment.
In our DMZ we have a Windows 2003 R2 server that is not part of the domain and only has the secure gateway running in forwarding mode and is pointing through our firewall to the LAN at the server mentioned above. I have allowed port 80 and 443 through the firewall from the DMZ to the LAN. The same ports are also allowed from the WAN to the DMZ.
On the LAN server, IIS is configured on port 81, the default for the cloud portal, and the secure gateway is configured on port 80 & 443 and is configured to direct HTTP traffic to localhost:81.
The problem I have is that if I browse to the Cloud Portal from outside our network (Via the DMZ etc) I get a blank white page almost every time, but hitting CTRL-F5 will show the page and then I can log in and everything works.
Does anyone know why I get the blank page first time round?
If I browse to it in Google Chrome I get this error:
Error 324 (net::ERR_EMPTY_RESPONSE): The server closed the connection without sending any data.
Firefox (my preferred browser) gives the blank page with "Done" in the status bar.
IE just says it can't display the page, but all of them work after hitting CTRL-F5.
This behavior only happens when connecting through the Secure Gateway that is in forwarding mode. As a test I connected a machine to the DMZ and browsed to the DMZ gateway from there, same thing. Eliminating the Secure Gateway in forwarding mode removes the problem, but I don't want to put the 2X server itself in the DMZ.
Any help would be appreciated.
Thanks
Iain.
I'm having a slightly annoying issue with our web portal/secure gateway setup.
First let me explain what we have.
On our LAN we have a Windows 2003 R2 server which is running pretty much everything for our 2X solution. It has the TS agent, Publishing agent, Secure Gateway as well as IIS6 & the Cloud Portal on it. I do plan to split these up later but we are evaluating the software at the moment.
In our DMZ we have a Windows 2003 R2 server that is not part of the domain and only has the secure gateway running in forwarding mode and is pointing through our firewall to the LAN at the server mentioned above. I have allowed port 80 and 443 through the firewall from the DMZ to the LAN. The same ports are also allowed from the WAN to the DMZ.
On the LAN server, IIS is configured on port 81, the default for the cloud portal, and the secure gateway is configured on port 80 & 443 and is configured to direct HTTP traffic to localhost:81.
The problem I have is that if I browse to the Cloud Portal from outside our network (Via the DMZ etc) I get a blank white page almost every time, but hitting CTRL-F5 will show the page and then I can log in and everything works.
Does anyone know why I get the blank page first time round?
If I browse to it in Google Chrome I get this error:
Error 324 (net::ERR_EMPTY_RESPONSE): The server closed the connection without sending any data.
Firefox (my preferred browser) gives the blank page with "Done" in the status bar.
IE just says it can't display the page, but all of them work after hitting CTRL-F5.
This behavior only happens when connecting through the Secure Gateway that is in forwarding mode. As a test I connected a machine to the DMZ and browsed to the DMZ gateway from there, same thing. Eliminating the Secure Gateway in forwarding mode removes the problem, but I don't want to put the 2X server itself in the DMZ.
Any help would be appreciated.
Thanks
Iain.