seagrtj
MIS
- Nov 12, 2002
- 13
- 0
- 0
There is an issue with WebAccess and W2K IIS. We use a 2 sever configuration. The IIS webserver is in our DMZ and the Novell Agent server is on the network. Our DMZ doesn't use real IP address', so the firewall has to NAT and PROXY from real IP's to our DMZ IP's.
Compose a message, if you try to attach a larger file to that message and while it is uploading, just click the X to close the compose window. It causes the W2K server to go 100% utilization and stay there until you restart the We worked with Novell Support extensively and were able to find that the Novell Servlet Gateway (NSGISAPI.DLL) is the problem. They have given us new code to test, haven't had the problem since. This problem has been around for a year.
What happens is the web browser sends a RST command to the web server, the firewall will not pass that through using NAT and PROXY. The browser never really talks to the webserver. The webserver just sits there and waits for a response that it is never going to get.
It is working like a champ now. I was told it will probably be a FTF soon and possibly incorporated into GW6 sp3.
Compose a message, if you try to attach a larger file to that message and while it is uploading, just click the X to close the compose window. It causes the W2K server to go 100% utilization and stay there until you restart the We worked with Novell Support extensively and were able to find that the Novell Servlet Gateway (NSGISAPI.DLL) is the problem. They have given us new code to test, haven't had the problem since. This problem has been around for a year.
What happens is the web browser sends a RST command to the web server, the firewall will not pass that through using NAT and PROXY. The browser never really talks to the webserver. The webserver just sits there and waits for a response that it is never going to get.
It is working like a champ now. I was told it will probably be a FTF soon and possibly incorporated into GW6 sp3.
