After a few months now I am still getting the

17/08/2005 9:26:05 PM|SETI@home|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed with a return value of 500
17/08/2005 9:26:05 PM|SETI@home|No schedulers responded

I do get to connect on occasion and return results, but most of the time I get the 500 error message. A tracert shows the following...

tracert setiboinc.ssl.berkeley.edu

Tracing route to galileo.ssl.berkeley.edu [128.32.18.173] over a maximum of 30 hops:

1 41 ms 39 ms 39 ms rns02-dryb-mel.comindico.com.au [203.220.79.66]
2 36 ms 39 ms 39 ms slb01-dryb-mel.comindico.com.au [203.194.19.161]
3 35 ms 40 ms 39 ms ge5-0.cor01-dryb-mel.comindico.com.au [203.194.19.233]
4 55 ms 49 ms 59 ms pos2-2.cor02-kent-syd.comindico.com.au [203.194.1.1]
5 46 ms 49 ms 49 ms ge3-1.bdr02-kent-syd.comindico.com.au [203.194.25.41]
6 46 ms 49 ms 49 ms 134.159.123.245
7 46 ms 49 ms 49 ms i-5-0.syd-core02.net.reach.com [202.84.144.249]
8 196 ms 199 ms 199 ms i-0-0.wil-core02.net.reach.com [202.84.144.101]
9 195 ms 199 ms 199 ms i-6-2.wil04.net.reach.com [202.84.251.186]
10 * * * Request timed out.
11 208 ms 199 ms 209 ms dc-slo-dc2--lax-dc1-pos.cenic.net [137.164.22.25]
12 207 ms 199 ms 199 ms dc-slo-dc1--dc2-df-iconn-2.cenic.net [137.164.22.124]
13 205 ms 209 ms 209 ms dc-sol-dc2--slo-dc1-pos.cenic.net [137.164.22.27]
14 206 ms 209 ms 209 ms dc-sol-dc1--sol-dc2-df-iconn-2.cenic.net [137.164.22.212]
15 206 ms 209 ms 209 ms dc-svl-dc1--sol-dc1-pos.cenic.net [137.164.22.29]
16 206 ms 209 ms 199 ms dc-svl-dc1--svl-dc2-df-iconn-2.cenic.net [137.164.22.208]
17 206 ms 209 ms 209 ms ucb--svl-dc1-egm.cenic.net [137.164.23.66]
18 207 ms 209 ms 209 ms vlan187.inr-201-eva.Berkeley.EDU [128.32.0.33]
19 207 ms 209 ms 209 ms g6-1.inr-230-spr.Berkeley.EDU [128.32.255.110]
20 217 ms 209 ms 209 ms solen.SSL.Berkeley.EDU [128.32.18.209]
21 * 206 ms 209 ms galileo.ssl.berkeley.edu [128.32.18.173]

Trace complete.

Not all is good out there. I have tried proxy servers and they get through once or twice then they stop working and I need to find a new one and try until I find one that works.

All up it's getting frustrating and it's fairly obvious I am not the only one this is happening to. What else can I do (I have looked at the Wiki)?

Live long and crunch.

---

Paul
(S@H1 8888)
And proud of it!

Hi
Have you traced the packets to see what you send and get back from the server?
Regards
Ian

---

Have you tried rotating through all the proxy servers located at http://www.iantighe.com/boincers.htm ?

---

Stewie: So, is there any tread left on the tires? Or at this point would it be like throwing a hot dog down a hallway?

Fox Sunday (US) at 9PM ET/PT

Have you tried rotating through all the proxy servers located at http://www.iantighe.com/boincers.htm ?

Oh yes, many times.

After a few months now I am still getting the
17/08/2005 9:26:05 PM|SETI@home|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed with a return value of 500
17/08/2005 9:26:05 PM|SETI@home|No schedulers responded

I've come across several posts that indicate the 500 error is the same error 500 a server generates then there is a cgi problem. This would mean you're connecting alright, but some sort of error is happening once you do connect. A cgi 500 commonly means that permissions aren't set correctly on the server side, there's a problem with Perl, the http header the script sends is invalid, that sort of thing. But all those are problems server side and not something that the remote user as any control over. Have you tried accessing the url (galileo.ssl.berkeley.edu) from a web browser? If you are in fact connecting successfully, you should get a page that shows a "403 Forbidden - you don't have permission to access this server". Or, using the url http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi in a browser should display:

scheduler_reply
scheduler_version>468 /scheduler_version
message priority="low"Incomplete request received. /message
/scheduler_reply
HTML HEAD META HTTP-EQUIV=Refresh CONTENT="0;URL=../" /HEAD BODY
You seem to be viewing this page in a WWW browser. Visit the a href="../" main page /a


Only other thing I can think of is inspite of what the other messages about error 500 say, there's another meaning to it beyond the the standard cgi catch-all error.

Do the trace and sent it me...let's see what the server is saying to you exactly

---

Or try a Canadian, US or Mexican proxy see if that helps. Here's some...never used em and nothing guaranteed...use at own risk.

IP:Port
Host name Hosting country Proxy type Support HTTPS (SSL) Last good check
(hh:mm ago) Uptime % Average Response Time(ms) Check now Whois Smart
traceroute
195.242.36.3:3128
nina.se.uu.net Sweden
SE Transparent Y 00:00 98.74 666 check whois traceroute
148.244.150.58:80
host-148-244-150-58.block.alestra.net.mx Mexico
MX High anonymity N 00:01 96.05 678 check whois traceroute
195.14.50.25:3128
zazel.corbina.net Russian Federation
RU Anonymous Y 00:01 99.29 803 check whois traceroute
195.14.50.25:8000
zazel.corbina.net Russian Federation
RU Anonymous Y 00:00 99.30 820 check whois traceroute
207.248.240.119:80
host-207-248-240-119.block.alestra.net.mx Mexico
MX High anonymity N 00:00 96.82 1040 check whois traceroute
158.43.240.11:3128
webcache4.pipex.net Great Britain
GB Transparent Y 00:00 99.02 1295 check whois traceroute
207.248.240.118:80
host-207-248-240-118.block.alestra.net.mx Mexico
MX High anonymity N 00:00 96.81 1672 check whois traceroute
158.43.240.15:3128
webcache8.pipex.net Great Britain
GB Transparent Y 00:00 97.83 1701 check whois traceroute
212.0.138.27:80
Name unavailable Sudan
SD High anonymity N 00:00 98.95 1758 check whois traceroute
213.219.51.80:80
Name unavailable Great Britain
GB Transparent N 00:00 84.69 1815 check whois traceroute
212.0.138.26:80
Name unavailable Sudan
SD High anonymity N 02:00 93.90 1844 check whois traceroute
158.43.240.13:3128
webcache6.pipex.net Great Britain
GB Transparent Y 02:03 97.65 1880 check whois traceroute
213.237.198.25:80
unassigned.legend.co.uk Great Britain
GB Transparent N 04:59 86.66 1894 check whois traceroute
158.43.240.9:3128
webcache2.pipex.net Great Britain
GB Transparent Y 04:05 97.53 1902 check whois traceroute
158.43.240.8:3128
webcache1.pipex.net Great Britain
GB Transparent Y 04:30 97.37 1965 check whois traceroute
158.43.240.10:3128
webcache3.pipex.net Great Britain
GB Transparent Y 00:55 97.29 1989 check whois traceroute
158.43.240.14:3128
webcache7.pipex.net Great Britain
GB Transparent Y 02:01 96.27 2030 check whois traceroute
80.249.72.161:80
Name unavailable Algeria
DZ Transparent N 04:32 81.25 2117 check whois traceroute
194.254.4.178:3128
Name unavailable France
FR Transparent Y 00:27 98.59 2408 check whois traceroute
62.189.34.9:3128
webcache00.lnd.ops.eu.uu.net Great Britain
GB Transparent Y 05:19 97.02 2536 check whois traceroute
62.189.34.58:3128
lnd10eusosrv52.lnd.ops.eu.uu.net Great Britain
GB Transparent Y 00:29 96.95 2601 check whois traceroute
195.54.84.14:3128
proxy.ford.eu.uu.net Denmark
DK Transparent Y 00:05 98.07 2610 check whois traceroute
200.165.58.195:80
Name unavailable Brazil
BR Transparent Y 10:07 56.14 2642 check whois traceroute
200.165.58.204:80
Name unavailable Brazil
BR Transparent Y 06:04 36.47 2649 check whois traceroute
195.175.37.38:80
Name unavailable Turkey
TR Transparent N 20:28 71.42 2650 check whois traceroute

---

After a few months now I am still getting the
17/08/2005 9:26:05 PM|SETI@home|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed with a return value of 500
17/08/2005 9:26:05 PM|SETI@home|No schedulers responded

I've come across several posts that indicate the 500 error is the same error 500 a server generates then there is a cgi problem. This would mean you're connecting alright, but some sort of error is happening once you do connect. A cgi 500 commonly means that permissions aren't set correctly on the server side, there's a problem with Perl, the http header the script sends is invalid, that sort of thing. But all those are problems server side and not something that the remote user as any control over. Have you tried accessing the url (galileo.ssl.berkeley.edu) from a web browser? If you are in fact connecting successfully, you should get a page that shows a "403 Forbidden - you don't have permission to access this server". Or, using the url http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi in a browser should display:

scheduler_reply
scheduler_version>468 /scheduler_version
message priority="low"Incomplete request received. /message
/scheduler_reply
HTML HEAD META HTTP-EQUIV=Refresh CONTENT="0;URL=../" /HEAD BODY
You seem to be viewing this page in a WWW browser. Visit the a href="../" main page /a


Only other thing I can think of is inspite of what the other messages about error 500 say, there's another meaning to it beyond the the standard cgi catch-all error.

Yep, get the same.

Do the trace and sent it me...let's see what the server is saying to you exactly

Tigher, you want more than the tracert shown below or something else?

Paul.

Yep, get the same.

If you're seeing those pages then you are connecting just fine. Not a DNS/proxy/network problem. The only time I've ever seen a 500 message like that in my log was following an outage when the bum's rush was on and the server was flooded with connects. It would flip flop between connection error and error 500. It only lasted about 2 hours and all has been normal since.

Well guys, thank you very much for this advice as it was just the medicine needed. A week ago, just before I went for a week long vacation, I installed a new broadband router. At first glance everything seemed OK, but yesterday when I got back I noticed a week long history of these 500 erorrs only at S@H. So I tried many things and when I saw the topic I tried connecting via proxy and it worked!

Many thanks again,

---

I have had this problem for weeks. At one point 10 machines had not done an update for 3 or 4 days.
Endless 500 error message's. I have done everything I know:-
Changed the proxyserver.
Changed Proxy from freeproxy to another one and back.
Used Ethereal to check the send message.
Rebooted the entire network.
Make some machines connect to the internet direct (no proxy server)
Flushdns

Not one single thing I have done has fixed a thing. All I do is wait - sometimes for days for a machine to update.
There may have been 3 or 4 masterfile updates before an update works. Then a couple of machines will update fine and then go back to the 500 error message.

Sad to say, but I am pleased somebody else has posted this problem.

Hope we can find what the problem is.

Nairb

---

Do the trace and sent it me...let's see what the server is saying to you exactly

Tigher, you want more than the tracert shown below or something else?

Paul.

Yeah an ethereal trace would be nice so I can see if the server is giving a reason along with the 500 error message.

I have seen this with seti before and it was a rouge MTU size then...but would like to have a look to see if I can spot anything for you.

---

Don't feel alone, there are likely more people with this error than anyone thinks. Myself included.

I have seen this with seti before and it was a rouge MTU size then...but would like to have a look to see if I can spot anything for you.

Maybe there's something to this MTU issue... IIRC TGG, like myself, is on (or behind) dial-up. I'm not certain, but maybe it's the dial-up MTU that needs some adjustment. Although exactly why it only affects SAH is still a mystery.

Personally, I'm still of the opinion that the problem is server-side, and the cgi handler is dying for some as yet unfathomed reason. For me, it's entirely inconsistent and almost impossible to trace due to only being able to see under the hood of one side of the problem. Others have had success switching to proxies, but as TGG says, it is only successful short-term. My take on the successes via proxy are that they are just lucky hits and would have hit irrespective of whether the proxy was used or not.

:-/

Don't feel alone, there are likely more people with this error than anyone thinks. Myself included.

I have seen this with seti before and it was a rouge MTU size then...but would like to have a look to see if I can spot anything for you.

Maybe there's something to this MTU issue... IIRC TGG, like myself, is on (or behind) dial-up. I'm not certain, but maybe it's the dial-up MTU that needs some adjustment. Although exactly why it only affects SAH is still a mystery.

Personally, I'm still of the opinion that the problem is server-side, and the cgi handler is dying for some as yet unfathomed reason. For me, it's entirely inconsistent and almost impossible to trace due to only being able to see under the hood of one side of the problem. Others have had success switching to proxies, but as TGG says, it is only successful short-term. My take on the successes via proxy are that they are just lucky hits and would have hit irrespective of whether the proxy was used or not.

:-/

Well I will help if I can. Error 500 can mean a partially delivered request to the server. This is consistent with MTU issues around dial up.....but can be many other things too. It is often said an MTU of about 550 for dial up is right and 1492 or 1494 for cable/dsl. If you want to change yours and try then great....if it works it will help many for sure.

Let me know please.

---

As i can see i've not been the only one who had the 500 errors forever. Mid of last week it was worst: no connection possible via 56k dial-up modem for days, two hosts out of work the rest short on wus and only 500 errors when trying to connect to the seti-servers. Luckily by end of last week i got a (slow)dsl-connection from my ISP. Since i had no more connection-problems.
Before i was playing around with the MTU-value (578-1492 are possible), which is easily changeable in my router-menus. That did not change anything.

Because of the faster connection working that well, i think, the problem could be the period of time a connection to the server is active. A dial-up modem needs more time to send data up to the server and it needs more time to receive data from the server, so the possibility of loosing a connection (or at least parts of the data) is higher.

Looking at the many ethereal-dumps i did when on dial-up, the error occured, when there is a double ack send from the server to the host during transmission
e.g.( 66.28.250.124 192.168.0.2 TCP [TCP Dup ACK 27#2] http > 3681 [ACK] ).
Surely this was mentioned before in an other thread.
Maybe that is a straw.

---

_\|/_
U r s

For what it is worth, looking at Paul's trace at the beginning of the thread I would be a bit concerned about the path over the net that he is being forced to take. Seeing times approaching and/or exceeding 200 ms just makes me shudder.... I'm in TX today and here's my tracert - but then again I haven't been having any issues since the DNS change propogated through the net a few weeks ago.... Networks and telcos, gotta love 'em

tracert setiboinc.ssl.berkeley.edu

Tracing route to galileo.ssl.berkeley.edu [128.32.18.173]
over a maximum of 30 hops:

1 8 ms 6 ms 6 ms 10.3.24.1
2 26 ms 26 ms 25 ms 147.225.254.9
3 50 ms 51 ms 50 ms 147.225.207.198
4 52 ms 51 ms 52 ms 72.254.128.1
5 52 ms 51 ms 51 ms 63.111.3.122
6 51 ms 50 ms 51 ms 199.170.227.157
7 52 ms 53 ms 52 ms 198.5.128.141
8 51 ms 50 ms 52 ms 0.so-1-0-0.WR2.ATL5.ALTER.NET [157.130.216.45]
9 49 ms 53 ms 51 ms 112.at-2-1-0.xr2.atl5.alter.net [152.63.3.65]
10 52 ms 51 ms 52 ms 0.so-1-0-0.xl2.atl5.alter.net [152.63.85.193]
11 85 ms 86 ms 88 ms 0.so-6-0-0.xl2.chi13.alter.net [152.63.70.105]
12 92 ms 92 ms 92 ms pos7-0.gw1.chi13.alter.net [152.63.69.181]
13 90 ms 91 ms 94 ms wcgGigECHI-gw.customer.alter.net [157.130.42.210
]
14 91 ms 91 ms 91 ms brvwil1wcx3-pos1-1-oc48.wcg.net [64.200.236.101]

15 107 ms 104 ms 104 ms dnvrco1wcx3-pos13-0-oc192.wcg.net [64.200.240.12
1]
16 125 ms 125 ms 125 ms sntcca1wcx2-pos14-0.wcg.net [64.200.240.182]
17 123 ms 128 ms 125 ms sntcca1wcx1-pos0-0-oc192.wcg.net [64.200.149.61]

18 129 ms 129 ms 129 ms snfcca1wcx3-pos15-0.wcg.net [64.200.249.61]
19 127 ms 129 ms 129 ms snfcca1wcx1-corp-for-ed-gige.wcg.net [64.200.198
.98]
20 133 ms 131 ms 130 ms dc-svl-isp--sfo-isp-t1.cenic.net [137.164.40.209
]
21 131 ms 131 ms 130 ms inet-ucb--svl-isp.cenic.net [137.164.24.106]
22 132 ms 132 ms 133 ms vlan193.inr-201-eva.berkeley.edu [128.32.0.74]
23 131 ms 134 ms 136 ms g6-1.inr-230-spr.berkeley.edu [128.32.255.110]
24 141 ms 131 ms 130 ms solen.ssl.berkeley.edu [128.32.18.209]
25 137 ms 131 ms 133 ms galileo.ssl.berkeley.edu [128.32.18.173]

Trace complete.

---

Wendy



Click Here for BOINC FAQ Service

As i can see i've not been the only one who had the 500 errors forever. Mid of last week it was worst: no connection possible via 56k dial-up modem for days, two hosts out of work the rest short on wus and only 500 errors when trying to connect to the seti-servers. Luckily by end of last week i got a (slow)dsl-connection from my ISP. Since i had no more connection-problems.
Before i was playing around with the MTU-value (578-1492 are possible), which is easily changeable in my router-menus. That did not change anything.

Because of the faster connection working that well, i think, the problem could be the period of time a connection to the server is active. A dial-up modem needs more time to send data up to the server and it needs more time to receive data from the server, so the possibility of loosing a connection (or at least parts of the data) is higher.

Looking at the many ethereal-dumps i did when on dial-up, the error occured, when there is a double ack send from the server to the host during transmission
e.g.( 66.28.250.124 192.168.0.2 TCP [TCP Dup ACK 27#2] http > 3681 [ACK] ).
Surely this was mentioned before in an other thread.
Maybe that is a straw.

Changing MTU size must be done in the registry - I am assuming you are Windows.

Is that just one DUP ACK? or is there a series...I guess just one.
Let me know...send me your ethereal trace if you kept it.....if you want to and where abouts are you in the world please. It may help others.

Thanks

---

As i can see i've not been the only one who had the 500 errors forever. Mid of last week it was worst: no connection possible via 56k dial-up modem for days, two hosts out of work the rest short on wus and only 500 errors when trying to connect to the seti-servers. Luckily by end of last week i got a (slow)dsl-connection from my ISP. Since i had no more connection-problems.
Before i was playing around with the MTU-value (578-1492 are possible), which is easily changeable in my router-menus. That did not change anything.

Because of the faster connection working that well, i think, the problem could be the period of time a connection to the server is active. A dial-up modem needs more time to send data up to the server and it needs more time to receive data from the server, so the possibility of loosing a connection (or at least parts of the data) is higher.

Looking at the many ethereal-dumps i did when on dial-up, the error occured, when there is a double ack send from the server to the host during transmission
e.g.( 66.28.250.124 192.168.0.2 TCP [TCP Dup ACK 27#2] http > 3681 [ACK] ).
Surely this was mentioned before in an other thread.
Maybe that is a straw.

Changing MTU size must be done in the registry - I am assuming you are Windows.

Is that just one DUP ACK? or is there a series...I guess just one.
Let me know...send me your ethereal trace if you kept it.....if you want to and where abouts are you in the world please. It may help others.

Thanks

OS is W2ksp4+.
My network configuration:
external dial-up modem with ethernet-connection to a router. That router has a fast ethernet switch build in that is extended by an other fast ethernet switch. At max. there are 9 machines and a printserver connected. The modem configuration works with PPPoE-menu in the router. It provides an MTU for the WAN connection (dial-up/cable/dsl/...).
Are we talking about the MTU for the dial-up connection or the MTU for the LAN (that would be in the registry)?

...#2... means a second acknowledgement retry. Actually there were three retries in that case:

No. Time Source Destination Protocol Info
1 2005-07-21 17:45:43.560134 192.168.0.2 66.28.250.124 TCP 3681 > http [SYN] Seq=0 Ack=0 Win=65535 Len=0 MSS=1260

Frame 1 (62 bytes on wire, 62 bytes captured)
Internet Protocol, Src Addr: 192.168.0.2 (192.168.0.2), Dst Addr: 66.28.250.124 (66.28.250.124)
Transmission Control Protocol, Src Port: 3681 (3681), Dst Port: http (80), Seq: 0, Ack: 0, Len: 0

No. Time Source Destination Protocol Info
2 2005-07-21 17:45:43.885402 66.28.250.124 192.168.0.2 TCP http > 3681 [SYN, ACK] Seq=0 Ack=1 Win=10164 Len=0 MSS=1452

Frame 2 (62 bytes on wire, 62 bytes captured)
Internet Protocol, Src Addr: 66.28.250.124 (66.28.250.124), Dst Addr: 192.168.0.2 (192.168.0.2)
Transmission Control Protocol, Src Port: http (80), Dst Port: 3681 (3681), Seq: 0, Ack: 1, Len: 0

No. Time Source Destination Protocol Info
3 2005-07-21 17:45:43.885536 192.168.0.2 66.28.250.124 TCP 3681 > http [ACK] Seq=1 Ack=1 Win=65535 Len=0

Frame 3 (54 bytes on wire, 54 bytes captured)
Internet Protocol, Src Addr: 192.168.0.2 (192.168.0.2), Dst Addr: 66.28.250.124 (66.28.250.124)
Transmission Control Protocol, Src Port: 3681 (3681), Dst Port: http (80), Seq: 1, Ack: 1, Len: 0

No. Time Source Destination Protocol Info
4 2005-07-21 17:45:43.896207 192.168.0.2 66.28.250.124 HTTP POST /sah_cgi/cgi HTTP/1.0

Frame 4 (296 bytes on wire, 296 bytes captured)
Internet Protocol, Src Addr: 192.168.0.2 (192.168.0.2), Dst Addr: 66.28.250.124 (66.28.250.124)
Transmission Control Protocol, Src Port: 3681 (3681), Dst Port: http (80), Seq: 1, Ack: 1, Len: 242
Hypertext Transfer Protocol

No. Time Source Destination Protocol Info
5 2005-07-21 17:45:43.897299 192.168.0.2 66.28.250.124 HTTP Continuation or non-HTTP traffic

Frame 5 (1314 bytes on wire, 1314 bytes captured)
Internet Protocol, Src Addr: 192.168.0.2 (192.168.0.2), Dst Addr: 66.28.250.124 (66.28.250.124)
Transmission Control Protocol, Src Port: 3681 (3681), Dst Port: http (80), Seq: 243, Ack: 1, Len: 1260
Hypertext Transfer Protocol

No. Time Source Destination Protocol Info
6 2005-07-21 17:45:44.316622 66.28.250.124 192.168.0.2 TCP http > 3681 [ACK] Seq=1 Ack=243 Win=10164 Len=0

Frame 6 (60 bytes on wire, 60 bytes captured)
Internet Protocol, Src Addr: 66.28.250.124 (66.28.250.124), Dst Addr: 192.168.0.2 (192.168.0.2)
Transmission Control Protocol, Src Port: http (80), Dst Port: 3681 (3681), Seq: 1, Ack: 243, Len: 0

No. Time Source Destination Protocol Info
7 2005-07-21 17:45:44.316760 192.168.0.2 66.28.250.124 HTTP Continuation or non-HTTP traffic

Frame 7 (1314 bytes on wire, 1314 bytes captured)
Internet Protocol, Src Addr: 192.168.0.2 (192.168.0.2), Dst Addr: 66.28.250.124 (66.28.250.124)
Transmission Control Protocol, Src Port: 3681 (3681), Dst Port: http (80), Seq: 1503, Ack: 1, Len: 1260
Hypertext Transfer Protocol

No. Time Source Destination Protocol Info
8 2005-07-21 17:45:44.316780 192.168.0.2 66.28.250.124 HTTP Continuation or non-HTTP traffic

Frame 8 (1314 bytes on wire, 1314 bytes captured)
Internet Protocol, Src Addr: 192.168.0.2 (192.168.0.2), Dst Addr: 66.28.250.124 (66.28.250.124)
Transmission Control Protocol, Src Port: 3681 (3681), Dst Port: http (80), Seq: 2763, Ack: 1, Len: 1260
Hypertext Transfer Protocol

No. Time Source Destination Protocol Info
9 2005-07-21 17:45:44.590836 66.28.250.124 192.168.0.2 TCP http > 3681 [ACK] Seq=1 Ack=1503 Win=10164 Len=0

Frame 9 (60 bytes on wire, 60 bytes captured)
Internet Protocol, Src Addr: 66.28.250.124 (66.28.250.124), Dst Addr: 192.168.0.2 (192.168.0.2)
Transmission Control Protocol, Src Port: http (80), Dst Port: 3681 (3681), Seq: 1, Ack: 1503, Len: 0

No. Time Source Destination Protocol Info
10 2005-07-21 17:45:44.590957 192.168.0.2 66.28.250.124 HTTP Continuation or non-HTTP traffic

Frame 10 (1314 bytes on wire, 1314 bytes captured)
Internet Protocol, Src Addr: 192.168.0.2 (192.168.0.2), Dst Addr: 66.28.250.124 (66.28.250.124)
Transmission Control Protocol, Src Port: 3681 (3681), Dst Port: http (80), Seq: 4023, Ack: 1, Len: 1260
Hypertext Transfer Protocol

No. Time Source Destination Protocol Info
11 2005-07-21 17:45:44.590982 192.168.0.2 66.28.250.124 HTTP Continuation or non-HTTP traffic

Frame 11 (1314 bytes on wire, 1314 bytes captured)
Internet Protocol, Src Addr: 192.168.0.2 (192.168.0.2), Dst Addr: 66.28.250.124 (66.28.250.124)
Transmission Control Protocol, Src Port: 3681 (3681), Dst Port: http (80), Seq: 5283, Ack: 1, Len: 1260
Hypertext Transfer Protocol

No. Time Source Destination Protocol Info
12 2005-07-21 17:45:44.842139 66.28.250.124 192.168.0.2 TCP [TCP Dup ACK 9#1] http > 3681 [ACK] Seq=1 Ack=1503 Win=10164 Len=0 SLE=2763 SRE=4023

Frame 12 (66 bytes on wire, 66 bytes captured)
Internet Protocol, Src Addr: 66.28.250.124 (66.28.250.124), Dst Addr: 192.168.0.2 (192.168.0.2)
Transmission Control Protocol, Src Port: http (80), Dst Port: 3681 (3681), Seq: 1, Ack: 1503, Len: 0

No. Time Source Destination Protocol Info
13 2005-07-21 17:45:44.842260 192.168.0.2 66.28.250.124 HTTP Continuation or non-HTTP traffic

Frame 13 (1314 bytes on wire, 1314 bytes captured)
Internet Protocol, Src Addr: 192.168.0.2 (192.168.0.2), Dst Addr: 66.28.250.124 (66.28.250.124)
Transmission Control Protocol, Src Port: 3681 (3681), Dst Port: http (80), Seq: 6543, Ack: 1, Len: 1260
Hypertext Transfer Protocol

No. Time Source Destination Protocol Info
14 2005-07-21 17:45:45.091341 66.28.250.124 192.168.0.2 TCP http > 3681 [ACK] Seq=1 Ack=4023 Win=10164 Len=0

Frame 14 (60 bytes on wire, 60 bytes captured)
Internet Protocol, Src Addr: 66.28.250.124 (66.28.250.124), Dst Addr: 192.168.0.2 (192.168.0.2)
Transmission Control Protocol, Src Port: http (80), Dst Port: 3681 (3681), Seq: 1, Ack: 4023, Len: 0

No. Time Source Destination Protocol Info
15 2005-07-21 17:45:45.091486 192.168.0.2 66.28.250.124 HTTP Continuation or non-HTTP traffic

Frame 15 (1314 bytes on wire, 1314 bytes captured)
Internet Protocol, Src Addr: 192.168.0.2 (192.168.0.2), Dst Addr: 66.28.250.124 (66.28.250.124)
Transmission Control Protocol, Src Port: 3681 (3681), Dst Port: http (80), Seq: 7803, Ack: 1, Len: 1260
Hypertext Transfer Protocol

No. Time Source Destination Protocol Info
16 2005-07-21 17:45:45.091505 192.168.0.2 66.28.250.124 HTTP Continuation or non-HTTP traffic

Frame 16 (1314 bytes on wire, 1314 bytes captured)
Internet Protocol, Src Addr: 192.168.0.2 (192.168.0.2), Dst Addr: 66.28.250.124 (66.28.250.124)
Transmission Control Protocol, Src Port: 3681 (3681), Dst Port: http (80), Seq: 9063, Ack: 1, Len: 1260
Hypertext Transfer Protocol

No. Time Source Destination Protocol Info
17 2005-07-21 17:45:45.341635 66.28.250.124 192.168.0.2 TCP http > 3681 [ACK] Seq=1 Ack=5283 Win=10164 Len=0

Frame 17 (60 bytes on wire, 60 bytes captured)
Internet Protocol, Src Addr: 66.28.250.124 (66.28.250.124), Dst Addr: 192.168.0.2 (192.168.0.2)
Transmission Control Protocol, Src Port: http (80), Dst Port: 3681 (3681), Seq: 1, Ack: 5283, Len: 0

No. Time Source Destination Protocol Info
18 2005-07-21 17:45:45.341792 192.168.0.2 66.28.250.124 HTTP Continuation or non-HTTP traffic

Frame 18 (1314 bytes on wire, 1314 bytes captured)
Internet Protocol, Src Addr: 192.168.0.2 (192.168.0.2), Dst Addr: 66.28.250.124 (66.28.250.124)
Transmission Control Protocol, Src Port: 3681 (3681), Dst Port: http (80), Seq: 10323, Ack: 1, Len: 1260
Hypertext Transfer Protocol

No. Time Source Destination Protocol Info
19 2005-07-21 17:45:45.341832 192.168.0.2 66.28.250.124 HTTP Continuation or non-HTTP traffic

Frame 19 (1314 bytes on wire, 1314 bytes captured)
Internet Protocol, Src Addr: 192.168.0.2 (192.168.0.2), Dst Addr: 66.28.250.124 (66.28.250.124)
Transmission Control Protocol, Src Port: 3681 (3681), Dst Port: http (80), Seq: 11583, Ack: 1, Len: 1260
Hypertext Transfer Protocol

No. Time Source Destination Protocol Info
20 2005-07-21 17:45:45.478793 66.28.250.124 192.168.0.2 TCP http > 3681 [ACK] Seq=1 Ack=6543 Win=10164 Len=0

Frame 20 (60 bytes on wire, 60 bytes captured)
Internet Protocol, Src Addr: 66.28.250.124 (66.28.250.124), Dst Addr: 192.168.0.2 (192.168.0.2)
Transmission Control Protocol, Src Port: http (80), Dst Port: 3681 (3681), Seq: 1, Ack: 6543, Len: 0

No. Time Source Destination Protocol Info
21 2005-07-21 17:45:45.478905 192.168.0.2 66.28.250.124 HTTP Continuation or non-HTTP traffic

Frame 21 (1314 bytes on wire, 1314 bytes captured)
Internet Protocol, Src Addr: 192.168.0.2 (192.168.0.2), Dst Addr: 66.28.250.124 (66.28.250.124)
Transmission Control Protocol, Src Port: 3681 (3681), Dst Port: http (80), Seq: 12843, Ack: 1, Len: 1260
Hypertext Transfer Protocol

No. Time Source Destination Protocol Info
22 2005-07-21 17:45:45.478923 192.168.0.2 66.28.250.124 HTTP Continuation or non-HTTP traffic

Frame 22 (1314 bytes on wire, 1314 bytes captured)
Internet Protocol, Src Addr: 192.168.0.2 (192.168.0.2), Dst Addr: 66.28.250.124 (66.28.250.124)
Transmission Control Protocol, Src Port: 3681 (3681), Dst Port: http (80), Seq: 14103, Ack: 1, Len: 1260
Hypertext Transfer Protocol

No. Time Source Destination Protocol Info
23 2005-07-21 17:45:45.624395 66.28.250.124 192.168.0.2 TCP http > 3681 [ACK] Seq=1 Ack=7803 Win=10164 Len=0

Frame 23 (60 bytes on wire, 60 bytes captured)
Internet Protocol, Src Addr: 66.28.250.124 (66.28.250.124), Dst Addr: 192.168.0.2 (192.168.0.2)
Transmission Control Protocol, Src Port: http (80), Dst Port: 3681 (3681), Seq: 1, Ack: 7803, Len: 0

No. Time Source Destination Protocol Info
24 2005-07-21 17:45:45.624480 192.168.0.2 66.28.250.124 HTTP Continuation or non-HTTP traffic

Frame 24 (1314 bytes on wire, 1314 bytes captured)
Internet Protocol, Src Addr: 192.168.0.2 (192.168.0.2), Dst Addr: 66.28.250.124 (66.28.250.124)
Transmission Control Protocol, Src Port: 3681 (3681), Dst Port: http (80), Seq: 15363, Ack: 1, Len: 1260
Hypertext Transfer Protocol

No. Time Source Destination Protocol Info
25 2005-07-21 17:45:45.624490 192.168.0.2 66.28.250.124 HTTP Continuation or non-HTTP traffic

Frame 25 (58 bytes on wire, 58 bytes captured)
Internet Protocol, Src Addr: 192.168.0.2 (192.168.0.2), Dst Addr: 66.28.250.124 (66.28.250.124)
Transmission Control Protocol, Src Port: 3681 (3681), Dst Port: http (80), Seq: 16623, Ack: 1, Len: 4
Hypertext Transfer Protocol

No. Time Source Destination Protocol Info
26 2005-07-21 17:45:45.753288 66.28.250.124 192.168.0.2 TCP http > 3681 [ACK] Seq=1 Ack=9063 Win=10164 Len=0

Frame 26 (60 bytes on wire, 60 bytes captured)
Internet Protocol, Src Addr: 66.28.250.124 (66.28.250.124), Dst Addr: 192.168.0.2 (192.168.0.2)
Transmission Control Protocol, Src Port: http (80), Dst Port: 3681 (3681), Seq: 1, Ack: 9063, Len: 0

No. Time Source Destination Protocol Info
27 2005-07-21 17:45:45.958423 66.28.250.124 192.168.0.2 TCP http > 3681 [ACK] Seq=1 Ack=10323 Win=10164 Len=0

Frame 27 (60 bytes on wire, 60 bytes captured)
Internet Protocol, Src Addr: 66.28.250.124 (66.28.250.124), Dst Addr: 192.168.0.2 (192.168.0.2)
Transmission Control Protocol, Src Port: http (80), Dst Port: 3681 (3681), Seq: 1, Ack: 10323, Len: 0

No. Time Source Destination Protocol Info
28 2005-07-21 17:45:45.965975 66.28.250.124 192.168.0.2 TCP [TCP Dup ACK 27#1] http > 3681 [ACK] Seq=1 Ack=10323 Win=10164 Len=0 SLE=11583 SRE=12843

Frame 28 (66 bytes on wire, 66 bytes captured)
Internet Protocol, Src Addr: 66.28.250.124 (66.28.250.124), Dst Addr: 192.168.0.2 (192.168.0.2)
Transmission Control Protocol, Src Port: http (80), Dst Port: 3681 (3681), Seq: 1, Ack: 10323, Len: 0

No. Time Source Destination Protocol Info
29 2005-07-21 17:45:46.099706 66.28.250.124 192.168.0.2 TCP [TCP Dup ACK 27#2] http > 3681 [ACK] Seq=1 Ack=10323 Win=10164 Len=0 SLE=14103 SRE=15363 SLE=11583 SRE=12843

Frame 29 (74 bytes on wire, 74 bytes captured)
Internet Protocol, Src Addr: 66.28.250.124 (66.28.250.124), Dst Addr: 192.168.0.2 (192.168.0.2)
Transmission Control Protocol, Src Port: http (80), Dst Port: 3681 (3681), Seq: 1, Ack: 10323, Len: 0

No. Time Source Destination Protocol Info
30 2005-07-21 17:45:46.099836 192.168.0.2 66.28.250.124 HTTP Continuation or non-HTTP traffic

Frame 30 (1314 bytes on wire, 1314 bytes captured)
Internet Protocol, Src Addr: 192.168.0.2 (192.168.0.2), Dst Addr: 66.28.250.124 (66.28.250.124)
Transmission Control Protocol, Src Port: 3681 (3681), Dst Port: http (80), Seq: 10323, Ack: 1, Len: 1260
Hypertext Transfer Protocol

No. Time Source Destination Protocol Info
31 2005-07-21 17:45:46.099859 192.168.0.2 66.28.250.124 HTTP Continuation or non-HTTP traffic

Frame 31 (1314 bytes on wire, 1314 bytes captured)
Internet Protocol, Src Addr: 192.168.0.2 (192.168.0.2), Dst Addr: 66.28.250.124 (66.28.250.124)
Transmission Control Protocol, Src Port: 3681 (3681), Dst Port: http (80), Seq: 12843, Ack: 1, Len: 1260
Hypertext Transfer Protocol

No. Time Source Destination Protocol Info
32 2005-07-21 17:45:46.117434 66.28.250.124 192.168.0.2 TCP [TCP Dup ACK 27#3] http > 3681 [ACK] Seq=1 Ack=10323 Win=10164 Len=0 SLE=16623 SRE=16627 SLE=14103 SRE=15363 SLE=11583 SRE=12843

Frame 32 (82 bytes on wire, 82 bytes captured)
Internet Protocol, Src Addr: 66.28.250.124 (66.28.250.124), Dst Addr: 192.168.0.2 (192.168.0.2)
Transmission Control Protocol, Src Port: http (80), Dst Port: 3681 (3681), Seq: 1, Ack: 10323, Len: 0

No. Time Source Destination Protocol Info
33 2005-07-21 17:45:46.210293 66.28.250.124 192.168.0.2 TCP http > 3681 [ACK] Seq=1 Ack=12843 Win=10164 Len=0 SLE=16623 SRE=16627 SLE=14103 SRE=15363

Frame 33 (74 bytes on wire, 74 bytes captured)
Internet Protocol, Src Addr: 66.28.250.124 (66.28.250.124), Dst Addr: 192.168.0.2 (192.168.0.2)
Transmission Control Protocol, Src Port: http (80), Dst Port: 3681 (3681), Seq: 1, Ack: 12843, Len: 0

No. Time Source Destination Protocol Info
34 2005-07-21 17:45:46.325480 66.28.250.124 192.168.0.2 TCP http > 3681 [ACK] Seq=1 Ack=15363 Win=10164 Len=0 SLE=16623 SRE=16627

Frame 34 (66 bytes on wire, 66 bytes captured)
Internet Protocol, Src Addr: 66.28.250.124 (66.28.250.124), Dst Addr: 192.168.0.2 (192.168.0.2)
Transmission Control Protocol, Src Port: http (80), Dst Port: 3681 (3681), Seq: 1, Ack: 15363, Len: 0

No. Time Source Destination Protocol Info
35 2005-07-21 17:45:46.737263 66.28.250.124 192.168.0.2 TCP http > 3681 [ACK] Seq=1 Ack=16627 Win=10164 Len=0

Frame 35 (60 bytes on wire, 60 bytes captured)
Internet Protocol, Src Addr: 66.28.250.124 (66.28.250.124), Dst Addr: 192.168.0.2 (192.168.0.2)
Transmission Control Protocol, Src Port: http (80), Dst Port: 3681 (3681), Seq: 1, Ack: 16627, Len: 0

No. Time Source Destination Protocol Info
36 2005-07-21 17:45:46.737598 192.168.0.2 66.28.250.124 HTTP Continuation or non-HTTP traffic

Frame 36 (1314 bytes on wire, 1314 bytes captured)
Internet Protocol, Src Addr: 192.168.0.2 (192.168.0.2), Dst Addr: 66.28.250.124 (66.28.250.124)
Transmission Control Protocol, Src Port: 3681 (3681), Dst Port: http (80), Seq: 16627, Ack: 1, Len: 1260
Hypertext Transfer Protocol

No. Time Source Destination Protocol Info
37 2005-07-21 17:45:46.737664 192.168.0.2 66.28.250.124 HTTP Continuation or non-HTTP traffic

Frame 37 (1314 bytes on wire, 1314 bytes captured)
Internet Protocol, Src Addr: 192.168.0.2 (192.168.0.2), Dst Addr: 66.28.250.124 (66.28.250.124)
Transmission Control Protocol, Src Port: 3681 (3681), Dst Port: http (80), Seq: 17887, Ack: 1, Len: 1260
Hypertext Transfer Protocol

No. Time Source Destination Protocol Info
38 2005-07-21 17:45:46.737698 192.168.0.2 66.28.250.124 HTTP Continuation or non-HTTP traffic

Frame 38 (204 bytes on wire, 204 bytes captured)
Internet Protocol, Src Addr: 192.168.0.2 (192.168.0.2), Dst Addr: 66.28.250.124 (66.28.250.124)
Transmission Control Protocol, Src Port: 3681 (3681), Dst Port: http (80), Seq: 19147, Ack: 1, Len: 150
Hypertext Transfer Protocol

No. Time Source Destination Protocol Info
39 2005-07-21 17:45:46.737856 66.28.250.124 192.168.0.2 TCP [TCP Dup ACK 35#1] http > 3681 [ACK] Seq=1 Ack=16627 Win=10164 Len=0

Frame 39 (60 bytes on wire, 60 bytes captured)
Internet Protocol, Src Addr: 66.28.250.124 (66.28.250.124), Dst Addr: 192.168.0.2 (192.168.0.2)
Transmission Control Protocol, Src Port: http (80), Dst Port: 3681 (3681), Seq: 1, Ack: 16627, Len: 0

No. Time Source Destination Protocol Info
40 2005-07-21 17:45:46.778600 66.28.250.124 192.168.0.2 TCP [TCP Dup ACK 35#2] http > 3681 [ACK] Seq=1 Ack=16627 Win=10164 Len=0

Frame 40 (60 bytes on wire, 60 bytes captured)
Internet Protocol, Src Addr: 66.28.250.124 (66.28.250.124), Dst Addr: 192.168.0.2 (192.168.0.2)
Transmission Control Protocol, Src Port: http (80), Dst Port: 3681 (3681), Seq: 1, Ack: 16627, Len: 0

No. Time Source Destination Protocol Info
41 2005-07-21 17:45:46.778683 192.168.0.2 66.28.250.124 HTTP Continuation or non-HTTP traffic

Frame 41 (1314 bytes on wire, 1314 bytes captured)
Internet Protocol, Src Addr: 192.168.0.2 (192.168.0.2), Dst Addr: 66.28.250.124 (66.28.250.124)
Transmission Control Protocol, Src Port: 3681 (3681), Dst Port: http (80), Seq: 16627, Ack: 1, Len: 1260
Hypertext Transfer Protocol

No. Time Source Destination Protocol Info
42 2005-07-21 17:45:47.300034 66.28.250.124 192.168.0.2 TCP http > 3681 [ACK] Seq=1 Ack=17887 Win=10164 Len=0

Frame 42 (60 bytes on wire, 60 bytes captured)
Internet Protocol, Src Addr: 66.28.250.124 (66.28.250.124), Dst Addr: 192.168.0.2 (192.168.0.2)
Transmission Control Protocol, Src Port: http (80), Dst Port: 3681 (3681), Seq: 1, Ack: 17887, Len: 0

No. Time Source Destination Protocol Info
43 2005-07-21 17:45:47.444902 66.28.250.124 192.168.0.2 TCP http > 3681 [ACK] Seq=1 Ack=19297 Win=10164 Len=0

Frame 43 (60 bytes on wire, 60 bytes captured)
Internet Protocol, Src Addr: 66.28.250.124 (66.28.250.124), Dst Addr: 192.168.0.2 (192.168.0.2)
Transmission Control Protocol, Src Port: http (80), Dst Port: 3681 (3681), Seq: 1, Ack: 19297, Len: 0

No. Time Source Destination Protocol Info
44 2005-07-21 17:45:47.526825 66.28.250.124 192.168.0.2 HTTP HTTP/1.1 500 Internal Server Error (text/html)

Frame 44 (861 bytes on wire, 861 bytes captured)
Internet Protocol, Src Addr: 66.28.250.124 (66.28.250.124), Dst Addr: 192.168.0.2 (192.168.0.2)
Transmission Control Protocol, Src Port: http (80), Dst Port: 3681 (3681), Seq: 1, Ack: 19297, Len: 807
Hypertext Transfer Protocol
Line-based text data: text/html

No. Time Source Destination Protocol Info
45 2005-07-21 17:45:47.531821 66.28.250.124 192.168.0.2 TCP http > 3681 [FIN, ACK] Seq=808 Ack=19297 Win=10164 Len=0

Frame 45 (60 bytes on wire, 60 bytes captured)
Internet Protocol, Src Addr: 66.28.250.124 (66.28.250.124), Dst Addr: 192.168.0.2 (192.168.0.2)
Transmission Control Protocol, Src Port: http (80), Dst Port: 3681 (3681), Seq: 808, Ack: 19297, Len: 0

I hope i didn't post anything that shouldn't be public.

If you want to know were i'm at you could click easily on my name. It'll tell you i'm in germany.

---

_\|/_
U r s

Better use DrTCP, so you don't have to mess with the registry yourself.

It's internet connection MTU. 1492 is fine if you use ADSL, but else use a Tweak test which will tell you what to set it to.

---