NNSquad - Network Neutrality Squad
[ NNSquad ] Re: How do I detect connection disruption by my IAP?
You would want to zero in on TCP SYN packets immediately followed by a
TCP RST packet, i.e., the handshake would never complete.
These type of things are high on the sketchy behavior list.
If you are not the intended recipient of this message (including attachments), or if you have received this message in error, immediately notify us and delete it and any attachments. If you no longer wish to receive e-mail from Edward Jones, please send this request to messages@edwardjones.com. You must include the e-mail address that you wish not to receive e-mail communications. For important additional information related to this e-mail, visit www.edwardjones.com/US_email_disclosure
-----Original Message-----
From: nnsquad-bounces+robert.holtz=edwardjones.com@nnsquad.org
[mailto:nnsquad-bounces+robert.holtz=edwardjones.com@nnsquad.org] On
Behalf Of Fred Reimer
Sent: Thursday, November 08, 2007 2:38 PM
To: B.J. Herbison (Mailing lists); nnsquad@nnsquad.org
Subject: [ NNSquad ] Re: How do I detect connection disruption by my
IAP?
You can download WireShark at www.wireshare.org for a packet capture and
analysis program. You'd need to know a bit about TCP/IP in order to
make good use of it, but you can search for TCP packets with the RST bit
set. That would be a "forced"
close. You CAN get them from some valid destinations, but they should
be rare, and should only happen at the end of a connection anyway. A
normal closure would be the use of the FIN flags.
Fred Reimer, CISSP, CCNP, CQS-VPN, CQS-ISS Senior Network Engineer
Coleman Technologies, Inc.
954-298-1697
-----Original Message-----
From: nnsquad-bounces+freimer=ctiusa.com@nnsquad.org
[mailto:nnsquad-bounces+freimer=ctiusa.com@nnsquad.org] On Behalf Of
B.J. Herbison (Mailing lists)
Sent: Thursday, November 08, 2007 10:08 AM
To: nnsquad@nnsquad.org
Subject: [ NNSquad ] How do I detect connection disruption by my IAP?
I have Comcast as my Internet access provider. I've been sending large
messages regularly via Gmail (almost daily for a couple of years). I
sent a message without problem Monday through Wednesday.
This morning I tried to send a message and it failed five times.
The attachment is large, but a little smaller than yesterday.
The error was:
Oops... a server error occurred and your email was not sent.
(#001)
(Similar error if I try to "save" the message.)
The five send failures and save failure were with Firefox, my standard
browser. Then I tried from IE and the message was sent.
Then it failed again from Firefox. (Chance? Coincidence?
Time-outs somewhere? I'd love to construct a formal experiment with
multiple computers, different browsers and add-ons, and stop-watch
controlled timing intervals. Unfortunately, I have a
life.)
How can I tell whether there is a problem with Google today, some issue
"out on the Internet", a Firefox problem, or whether Comcast is messing
with my connections?
Are there any Windows XP tools to monitor my connections (either inside
or out of Firefox) to see if there was a forced close?
Thanks,
B.J.
--
B.J. Herbison / bj@herbison.com /
http://www.herbison.com/herbison/bj.html
The Next Asylum / 203 Long Hill Road / Bolton, MA 01740-1421 /
+1 978 634-1061
_______________________________________________
NNSquad mailing list information:
http://lists.nnsquad.org/mailman/listinfo/nnsquad