Internal Error 500!!!

[novice]

Hi!

When I surf the net from Client most of the time I get The message "Internal Sever Error 500" and usually slow...

Anybody could help please?

===============================
My Brief configuration:

- I using NAT to share Internet
- Wingate version: 5.22
- Connection: PPPoE (256kbs DSL)
- NIC: 2 NICs (One connect to DSL modem, Other LAN)
- USER:
+ Internet: internet connection (with usage limit)
+ Mail : Pop3 mail only
+ Priority:Internet connection without any limit
- IP: Using Static IP
- OS: Windows 2000

================================

[Pascal]

Are you using Transparent Redirection (Sessions Tab->Redirect ENS/WGIC sessions) with NAT ?

If you are, can you enable error logging in the WWW Proxy ? That will give you the exact reason for the 500 Internal Server error.

[pheakavoin]

Hi, I'm meeting this same problem also. But with little difference. My clients can access to any web site. But everytime they try to access www.hostingsupport.com the error page appear with "HTTP 500 internal server error".

My configuration is

-broadband wireless internet access
-2 NICs in server machine (one to the internet box, one to LAN Hub)
-NAT without Redirect ENS/WGIC, Wingate firewall disable
-Without any bandlist for each internet user
-gateway/dns point to Wingate server for each client with static IP

Any hole that cause this problem?

All of your comments with be appriciated.

Pheakavoin

[novice]

If you are, can you enable error logging in the WWW Proxy ? That will give you the exact reason for the 500 Internal Server error.

Yes Pascal, I am using it. But where/How could I find the place to see the problem?

Thanks.

[Pascal]

Go to the folder you installed WinGate. (Normally C:\Program Files\WinGate)

From there, there is a folder called "Logging" or "Logs". In that folder will be a series of different folders, named for the different components of WinGate. Look for one titled "WWW Proxy Service". The log files are in there.

You can open the logs with a text editor, such as NotePad.

[yoman]

I am having the same problem.. I had installed the pursite plugin but removed thinking .. that it may caused the error.. AS suggested here. I found this unusual thing in my wwwProxy logs..

Code:

03/08/04 17:49:07   192.168.0.4   Guest   0000000046   Error:   Caught socket exception in CWWWSession::HTTPProcessRequest() Connection to Remote Host timed out - terminating
03/08/04 17:49:07   192.168.0.4   Guest   0000000046   Traffic    215   399   0   0   21s
03/08/04 17:49:09   192.168.0.4   Guest   0000000047   Error:   Caught socket exception in CWWWSession::HTTPProcessRequest() Connection to Remote Host timed out - terminating
03/08/04 17:49:09   192.168.0.4   Guest   0000000047   Traffic    0   238   0   0   

Now can any one tell me wht the reason behing it ?

[Pascal]

We're investigating several areas that might be related to this. One of them seems to be exceptionally high CPU load on the WinGate machine. Would you describe your setup as one which might have high CPU usage (85% or more, roughly) on a regular basis ?

Do you run WinGate with GateKeeper open and showing activity all the time ?

[Pascal]

Are these error messages a regular occurence ? Or is it occasional, as you'd expect from a server that is simply not available or reachable at a given time ?

(Trying to determine if it is a general, Internet glitch which goes away after a while, or a more tangible problem)

[novice]

Sorry for my late reply.

After I look at the log file I found this error message:

03/18/04 17:08:36 192.168.0.37 priority 0000003697 Requested: http://www.ebay.com/
03/18/04 17:08:38 192.168.0.37 priority 0000003690 Error: Caught socket exception in CWWWSession::HTTPProcessRequest() Connection to Remote Host timed out - terminating
03/18/04 17:08:38 192.168.0.37 priority 0000003690 Traffic 215 998 0 0 23s

And the error always occure after I surf the net from client about 10 to 15 min (on any website).

Could you tell me how to solve this problem?

Note: Sulf from the server I found no problem and Send and receive mail at the clien computer also found no problem too.