Comments
Sort by recent activity
To address the title, I started getting this error after I removed a test server from our monitoring. Thanks. / comments
To address the title, I started getting this error after I removed a test server from our monitoring. Thanks.
Nevermind, I'm blind I found it / comments
Nevermind, I'm blind I found it
Thanks for all the help Dan, one last question, is there any way to set up a second maintenance window on the same server? For patching weekends / emergency maintenance? / comments
Thanks for all the help Dan, one last question, is there any way to set up a second maintenance window on the same server? For patching weekends / emergency maintenance?
Another feature that would be nice to have, which I didnt see going through the documentation or through the client would be an out of band maintenance window option for when there is planned patching or emergency maintenance being done on the network. / comments
Another feature that would be nice to have, which I didnt see going through the documentation or through the client would be an out of band maintenance window option for when there is planned patch...
Thank you for the quick reply, I'm pretty new to this software so I haven't used the regex yet but here is the error we receive; there's actually two network scans that kick off this same error.
Time raised:
5 Jul 2018 00:41 (UTC-05)
Details
Log entry:
Error: 17836, Severity: 20, State: 17.
Length specified in network packet payload did not match number of bytes
read; the connection has been closed. Please contact the vendor of the client
library. [CLIENT: 192.168.0.150 <- (fake ip address input)]
/ comments
Thank you for the quick reply, I'm pretty new to this software so I haven't used the regex yet but here is the error we receive; there's actually two network scans that kick off this same error.
...