Please go into Command Prompt. run the command "netstat -ano | findstr 514" This will report back the bound IP, the Port, and the Process ID of the associated Application for the Port. This is to make sure that the Syslog process is bound to 0.0.0.0 and not only 127.0.0.1.
You will need to make sure that you see:
UDP 0.0.0.0:514 *:* ProcessID#
Next you will need to bring up Task Manager (Ctrl+Alt+Del) and go to Processes View. At the top select View> Select Columns. Select PID (Process Identifier) and select OK. Make sure that the Process ID from netstat matches to
Kiwi Syslog is configured as a Service: Syslogd_Service.exe
Kiwi Syslog is configured as an Application: Syslogd.exe
Netstat shows the port correctly, and the process matches to the correct process, check to see if you have any other firewalls running. One issue I ran into with Wireshark is that it will show you packets flowing in prior to the Firewall rules being applied,