Hi,
Then syslogd service runs fine on our windows server 2016 DC.
But if we open the console, it hangs. Memory and CPU load are ok.
Any idea what I can check ?
Best Regards,
Wouter Jinssen
Siemens
If you look in your errorlog.txt file, do you see any errors?
found that using Snort on same server cause the console to not open when Snort was running on the interface used to receive syslogs. So if you have Snort other network sniffer/monitor app using the same NIC, you would have to seperate them. For Snort, had disable the use of the NIC syslog used and reboot server to get the Syslog Console to open