search

crazytroy / eventlog-to-syslog

Automatically exported from code.google.com/p/eventlog-to-syslog
0 stars 0 forks source link

Why does evtsys.exe listen to a network port? #32

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
I'm testing eventlog-to-syslog, and it looks very interesting - thanks.

However, the evtsys.exe seems to be listening on an UDP port. Why is that? May 
be the documentation should mention it.

Original issue reported on code.google.com by troels.a...@gmail.com on 12 Apr 2011 at 11:50

GoogleCodeExporter commented 8 years ago 
(This issue shouldn't have type "Defect", but it seems there is no way to 
adjust it after the fact.)

Original comment by troels.a...@gmail.com on 12 Apr 2011 at 11:51

GoogleCodeExporter commented 8 years ago 
I'm not sure what you are referring to. What leads you to believe it is 
listening on a port? The utility will bind to ports as of the latest build 
because I now connect each socket to a specific loghost IP address, but ports 
are only opened for writing, no data is ever read from a socket. Also, if you 
are in UDP mode you should notice that the ports are not LISTENING when you 
perform a netstat.

Once I have completed the TCP implementation/documentation I will add this 
information.

-Sherwin

Original comment by sherwin....@gmail.com on 13 Apr 2011 at 4:27

GoogleCodeExporter commented 8 years ago 
Ah - I had forgotten that this is UDP by default, and that it makes sense that 
evtsys.exe is bound to a random UDP port to be able to send messages. Sorry for 
the confusion.

Original comment by troels.a...@gmail.com on 13 Apr 2011 at 8:03

GoogleCodeExporter commented 8 years ago

Original comment by sherwin....@gmail.com on 15 Apr 2011 at 2:50