-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
event_listener 3017/tcp Event Listener event_listener 3017/udp Event Listener # Ted Tronson <[EMAIL PROTECTED]> You may have a connection with your Novell theory...maybe GroupWise...? You can always email Ted ;) http://andrew.triumf.ca/cgi-bin/port?udp+3017 Google search: {"Port 3017" AND groupwise} This looks like an email header - http://www.byu.edu/csr/www/solutions/dbook/archives/byucsr-l/Mar-01/22-11:18:04 The only other search results that came up had to do with Traditional-NAT-PT Operation (V6 to V4): Google search: {"Port 3017"} http://www.zvon.org/tmRFC/RFC3022/Output/chapter2.html http://www.zvon.org/tmRFC/RFC2766/Output/chapter3.html http://www.ietf.org/proceedings/99mar/I-D/draft-ietf-ngtrans-natpt-05.txt Don't know if this helps, but the search was fun. jack - --- Steve Bremer <[EMAIL PROTECTED]> wrote: > Can anyone enlighten me as to what might be listening on this > port? After doing a google search, all I find are documents that list > the port as an "Event Listener". No additional, useful information is > provided. Doing an additional search for "event listener"returns > those same documents. > > The machines that have this port open are running windows 98SE. > Is this normal for a windows 98 machine to have this port open? If > so, what is it used for? Can it be disabled? > > The only other thing that these machines all have in common is a > Novell client. I'm in the process of removing a Novell client from > one of them to see if the port closes. > > TIA for any help, > Steve Bremer > NEBCO, Inc. > > > -----BEGIN PGP SIGNATURE----- Version: Hush 2.1 Note: This signature can be verified at https://www.hushtools.com wmMEARECACMFAj0GciscHGphY2tfbWNjYXJ0aHk4QGh1c2htYWlsLmNvbQAKCRAA6VKc ODqCXCTHAJ9THVVbe6pBhlp6og9NlyWO7TSdqwCgpx82bVCpO4Zr30OLZAfErifcDko= =luIx -----END PGP SIGNATURE-----
