Nmap Development mailing list archives
Strange read error from <ip> Transport endpoint is not connected
From: PVM () capmon dk
Date: Tue, 11 Feb 2003 10:41:34 +0100
Hi, We're seeing this in a log file, to which output has been redirected: Strange read error from 172.25.5.248: Transport endpoint is not connected Strange read error from 172.25.5.249: Transport endpoint is not connected Strange read error from 172.25.5.250: Transport endpoint is not connected Strange read error from 172.25.5.251: Transport endpoint is not connected Strange read error from 172.25.5.252: Transport endpoint is not connected Strange read error from 172.25.5.253: Transport endpoint is not connected Strange read error from 172.25.5.254: Transport endpoint is not connected It seems to be repeated over and over, until the unit died when it ran out of HD space. Anyone have any idea (remember :-) what the reason could be? Linux, SuSE 7.2, nmap-2.53-127 (I know its an old Nmap version but it was reported against that version and we don't know how to reproduce it to test with newer versions....) Any help appreciated... Peter P.S: I tried to post here before, but didn't see it turn up, so I'm trying again. Also, is the right place to ask this sort of thing? --------------------------------------------------------------------- For help using this (nmap-dev) mailing list, send a blank email to nmap-dev-help () insecure org . List run by ezmlm-idx (www.ezmlm.org).
Current thread:
- Strange read error from <ip> Transport endpoint is not connected PVM (Feb 11)