Transcript
There are additional options to listen over TCP and secure TCP with the option to listen for SNMP traps. You can enable these options by going to the Inputs section and clicking the respective protocols that you want Kiwi to listen for. You need to make sure that the protocol and ports selected in Kiwi match that of your devices. If your protocol and port match, but you are still not seeing messages, you should verify the firewall is allowing traffic to pass through on the port and protocol selected. If the firewall settings are correct, ensure that no other services are utilizing the port. To find which service is utilizing the port, go to Command Prompt and type netstat-ano. This command will give you a list of active ports and the ID of the process that is bound to them. Check for UDP port that ends in 514 and look up the corresponding process ID. In this example, it reads 4948. Now open the Windows Task Manager and go to the Process tab and look for the process ID 4948. If there is no column shown for process ID, go to View, select Columns, and check the option PID Process Identifier. In this case, we find that the process associated with PID 4948 is syslogd-service.exe. If you find another process listed for this PID, right-click on the process and select End so that the port will now be available to Kiwi. Return to the Kiwi Syslog Server console, click on the Manage menu, and stop syslogd-service and start it again. Now you should begin seeing messages. For more information on Kiwi Syslog Server, contact kiwisales at solarwinds.com.
