Many network problems that affect your access to the Internet, such as the currently obnoxious "Server Error 1-500", can be better understood, if we can understand how you are connecting to the servers in question. A pathping log, similar to a traceroute log, but easier to read, is very useful in this case.
C:\>pathping www.google.com Tracing route to www.l.google.com [74.125.19.103] over a maximum of 30 hops: 0 Dell1600.martinez.cacroll.net [192.168.203.101] 1 209-204-141-1.dsl.static.sonic.net [209.204.141.1] 2 111.at-4-0-0.gw4.200p-sf.sonic.net [208.106.28.177] 3 0.as0.gw3.200p-sf.sonic.net [64.142.0.225] 4 200.ge-1-2-0.gw2.equinix-sj.sonic.net [64.142.0.210] 5 eqixsj-google-gige.google.com [206.223.116.21] 6 209.85.252.2 7 209.85.251.94 8 74.125.19.103 Computing statistics for 200 seconds... Source to Here This Node/Link Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address 0 Dell1600.martinez.cacroll.net [192.168.203.101] 3/ 100 = 3% | 1 37ms 3/ 100 = 3% 0/ 100 = 0% 209-204-141-1.dsl.static.sonic.net [209.204.141.1] 0/ 100 = 0% | 2 33ms 3/ 100 = 3% 0/ 100 = 0% 111.at-4-0-0.gw4.200p-sf.sonic.net [208.106.28.177] 0/ 100 = 0% | 3 40ms 3/ 100 = 3% 0/ 100 = 0% 0.as0.gw3.200p-sf.sonic.net [64.142.0.225] 0/ 100 = 0% | 4 42ms 5/ 100 = 5% 2/ 100 = 2% 200.ge-1-2-0.gw2.equinix-sj.sonic.net [64.142.0.210] 0/ 100 = 0% | 5 35ms 4/ 100 = 4% 1/ 100 = 1% eqixsj-google-gige.google.com [206.223.116.21] 0/ 100 = 0% | 6 41ms 3/ 100 = 3% 0/ 100 = 0% 209.85.252.2 3/ 100 = 3% | 7 42ms 7/ 100 = 7% 1/ 100 = 1% 209.85.251.94 0/ 100 = 0% | 8 45ms 6/ 100 = 6% 0/ 100 = 0% 74.125.19.103 Trace complete.