Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #45749
| Path | csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!nntp.club.cc.cmu.edu!micro-heart-of-gold.mit.edu!bloom-beacon.mit.edu!panix!not-for-mail |
|---|---|
| From | Grant Edwards <invalid@invalid.invalid> |
| Newsgroups | comp.lang.python |
| Subject | Re: Diagnosing socket "Connection reset by peer" |
| Date | Wed, 22 May 2013 19:55:39 +0000 (UTC) |
| Organization | PANIX Public Access Internet and UNIX, NYC |
| Lines | 37 |
| Message-ID | <knj7rr$7ai$1@reader1.panix.com> (permalink) |
| References | <038ecc3e-1272-46c0-84d5-556daeffbde0@googlegroups.com> <mailman.1963.1369227039.3114.python-list@python.org> <slrnkpq80d.3jn.grahn+nntp@frailea.sa.invalid> |
| NNTP-Posting-Host | dsl.comtrol.com |
| X-Trace | reader1.panix.com 1369252539 7506 64.122.56.22 (22 May 2013 19:55:39 GMT) |
| X-Complaints-To | abuse@panix.com |
| NNTP-Posting-Date | Wed, 22 May 2013 19:55:39 +0000 (UTC) |
| User-Agent | slrn/1.0.1 (Linux) |
| Xref | csiph.com comp.lang.python:45749 |
Show key headers only | View raw
On 2013-05-22, Jorgen Grahn <grahn+nntp@snipabacken.se> wrote:
> On Wed, 2013-05-22, Dave Angel wrote:
>> On 05/22/2013 04:46 AM, loial wrote:
>>> <SNIP>
>>>
>>> .... Is there any additional traceing I can do(either within my
>>> python code or on the network) to establish what is causing this
>>> error?
>>
>> Try using Wireshark. It can do a remarkable job of filtering,
>> capturing, and analyzing packets. It can also read and write pcap
>> files, which you could either save for later analysis, or send to
>> someone who might help.
>
> Or use tcpdump, which has a text interface so you can show the problem
> in a text medium like Usenet.
There's also tshark, which is sort of a command-line version of
wireshark.
http://www.wireshark.org/docs/man-pages/tshark.html
>> (Note - unfiltered pcap files can be very large on a busy network,
>> but if you can quiet other traffic, you may not need to filter at
>> all.)
>
> Or simply filter. It's not hard -- the capture filter "host
> my-printer-hostname-or-address" is enough.
Indeed. Even a simple filter can make life several orders of
magnitude easier. If filtering by IP address isn't enough, the next
step is usually to add a port number filter...
--
Grant Edwards grant.b.edwards Yow! Of course, you
at UNDERSTAND about the PLAIDS
gmail.com in the SPIN CYCLE --
Back to comp.lang.python | Previous | Next — Previous in thread | Find similar | Unroll thread
Diagnosing socket "Connection reset by peer" loial <jldunn2000@gmail.com> - 2013-05-22 01:46 -0700
Re: Diagnosing socket "Connection reset by peer" Matt Jones <matt.walker.jones@gmail.com> - 2013-05-22 06:46 -0500
Re: Diagnosing socket "Connection reset by peer" Jorgen Grahn <grahn+nntp@snipabacken.se> - 2013-05-22 19:54 +0000
Re: Diagnosing socket "Connection reset by peer" Dave Angel <davea@davea.name> - 2013-05-22 08:50 -0400
Re: Diagnosing socket "Connection reset by peer" Jorgen Grahn <grahn+nntp@snipabacken.se> - 2013-05-22 19:44 +0000
Re: Diagnosing socket "Connection reset by peer" Grant Edwards <invalid@invalid.invalid> - 2013-05-22 19:55 +0000
csiph-web