|
If no messages are being displayed to the screen or being logged:
| • | Check network connectivity by pinging from the sending device to the Syslog Server machine |
| • | Check only one instance of Kiwi Syslog Server is running (Ctrl-Shift-Esc to get the task-list) |
| • | Disable any personal firewall software such as ZoneAlarm or BlackIce |
| • | Check DNS resolution is working as expected by pinging a hostname from the Command Prompt |
| • | Check that there is a "Display" action setup for the facility and level you are expecting to receive messages on. |
| • | Send a test message to yourself by pressing Ctrl+T |
| • | Install SyslogGen and set it to send a message every second to the address 127.0.0.1 (local host). |
| • | If you see messages appearing, the problem is with the router, switch or Unix box sending the Syslog messages. |
| • | Try sending messages with SyslogGen from another machine to the host running the Syslog Server |
| • | The device that is sending messages to you may not be including a priority code in its message. You can set a default priority to use from the Modifiers option of the Kiwi Syslog Server Setup window. To open the setup window use the File | Setup menu option from the main Kiwi Syslog Server window. |
| • | If you are running a Cisco router and are not receiving messages, use the Logging source-interface command to specify an interface to log from. There is a bug in the Cisco IOS that causes invalid UDP checksums unless this command is specified. |
If the Kiwi Syslog Server still fails to display messages:
| • | Restart the computer (power off as well if possible) |
| • | Disable the DNS settings so that no IP address resolution is performed |
| • | Disable the e-mail settings by un-checking the Alarm and Statistics notification options |
| • | From the Defaults/Import/Export option, press the Load default Rules and Settings button. Then press OK to accept the changes. |
| • | Check the Kiwi Syslog Server errorlog file to see if this contains any information that may be of assistance. This file is called "ErrorLog.txt" and is located in the installation directory. |
| • | If you find a message in the errorlog file stating that Kiwi Syslog Server is unable to bind to a particular port then you will need to close down the application that is using that port before restarting Kiwi Syslog Server again. Further information on this can be found in the FAQ section on our website: http://www.kiwisyslog.com/support. |
If the program still fails to display messages:
If the problem still exists after following the instructions above, then please use the http://www.kiwisyslog.com/support to receive further assistance.
Please provide as much technical detail as possible. This makes the remote troubleshooting a lot easier.
|