On 2013-05-22, Jorgen Grahn wrote:
> On Wed, 2013-05-22, Dave Angel wrote:
>> On 05/22/2013 04:46 AM, loial wrote:
>>>
>>>
>>> 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 Wiresha
On Wed, 2013-05-22, Matt Jones wrote:
> On Wed, May 22, 2013 at 3:46 AM, loial wrote:
>
>> I have a sockets client that is connecting to a printer and occassionally
>> getting the error "104 Connection reset by peer"
>>
>> I have not been able to diagnose what is causing this. Is there any
>> addi
On Wed, 2013-05-22, Dave Angel wrote:
> On 05/22/2013 04:46 AM, loial wrote:
>>
>>
>> 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,
On 05/22/2013 04:46 AM, loial wrote:
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 rea
This typically indicates that the "peer" at the other end of the tcp
connection severed the session without the typical FIN packet. If you're
treating the printer as a "blackbox" then there really isn't anything you
can do here except catch the exception and attempt to reconnect.
*Matt Jones*
O
I have a sockets client that is connecting to a printer and occassionally
getting the error "104 Connection reset by peer"
I have not been able to diagnose what is causing this. Is there any additional
traceing I can do(either within my python code or on the network) to establish
what is causin
