Comments
-
The message volume could have been a temp issue. I would keep an eye on it and look at the errorlog.txt file if the issue comes back.
-
Wireshark see data at the NIC level: where as, Kiwi Syslog sees the data after it has gone the the NIC and been processed by the operating system.
-
Merlin, What type of reply are you wanting to send?
-
Simon, In mine I see: If you are not seeing this, I would reinstall Kiwi Syslog over the top of your current install (as the local admin, not a domain account). This should give you option to uninstall.
-
When it gives you the option to view existing results, or Rescan, select Rescan.
-
Yes the INI file should contain all of your settings. If you run license manager, do you see any errors?
-
After the upgrade you will need to apply your activation key. This is found in your customer portal. Here are migration instructions: http://knowledgebase.solarwinds.com/kb/questions/107/Move+Kiwi+Syslog+Daemon+to+another+machine Keep in mind that if you are moving from a 32 bit system to a 64 bit system you will copy the…
-
You would need to submit a feature request to get this functionality added.
-
Ron, IpMonitor is still being developed. In the last few version we have added new features that have been waited on for years. For example: 1. SNMP v3 support 2. Custome WMI monitors 3. AD integration 4. 64 bit counters
-
You can copy over the dbstore directory for the original installation.
-
If you go into Setup, and click on Inputs, has the IP address of the system sending SNMP traps been added to the list.
-
As a test, try the following: 1. Click File\Setup 2. In the left pane, scroll down and click on DNS Resolution 3. Uncheck the Resolve the address of the sending device box 4. Click OK See if this helps.
-
George, Thank you for your reply. They are currently working to address an issue withe security logs and version 1.2.
-
Thanks for the reply. What OS are you installing on?
-
Please also post a screenshot of the Options tab for the activity.
-
The message will be sent over, and should include the community string. You do not have to specify the string in Kiwi Syslog. Please see this link: http://www.kiwisyslog.com/help/syslog/index.html?setup_snmp_input.htm
-
I see where we are getting back: Do you want to log out (y/n)? Is there a way to disable this prompt?
-
It is possible that the device script has changed. Which device have you selected?
-
Derek, To eliminate a Log Forwarder configuration setting as the cause, please try this: 1. Stop the SolarWinds Log Forwarder for Windows service 2. Rename the LogForwarderSettings.cfg file located in your \SolarWinds\SolarWinds Log Forwarder for Windows directory 3. Restart the service
-
I was discussing ipMonitor with our product marketing manager a few days ago. The TLS fix will be included in the next release, along with some feature requests. He has recently taken over the product, which is the reason for lack or current information.
-
Eric, You will need to use the CatTools scheduler to kick off this activity. You would need to create a feature request to add the ability to launch an activity from a script.
-
Simon, Try using the %DateISO% value. Let me know if that gives you a new file each day.
-
Are you able to relay a message to those addresses from the command line using telnet?
-
Are you running the hotfix 1 for 9.5.0?
-
Please see this link: MSMQ installation errors - SolarWinds Worldwide, LLC. Help and Support
-
Thank you for the update.
-
Web data is stored in a SQL compact database, and this database is queried when retrieving web data.
-
If a layer 3 devices is not being polled via SNMP, NT does not know how to show the connections. Is your SNMP node router or layer 3 switch?
-
Thank you for the update.
-
Please do the following: 1. Use the CatTools File menu to select the "Enable capture mode" option. 2. Run the activity you are having trouble with. This should create a debug file in the \CatTools3\Debug folder. 3. Remember to deselect the "enable capture mode" option again. Remove any sensitive information, and upload the…