unknown user trying to post to DCE

[DCIM_Support]

can someone please explain with this log from DCE

10/30/19 16:29:27.124 WARN - User [tc4z1Whipu] from IP address [192.168.16.102] is not authorized to post to [/botpost/surveillance]com.netbotz.server.servlets.botpost.BotPostBasicProcessingFilterEntryPoint)

this user is not on the device 

(CID:151061453)

[DCIM_Support]

I searched for a few keywords of your issue and found this message. 

As for the NetBotz based message [10.67.33.83] is not authorized to post to [/botpost/surveillance], are you having surveillance issues? Are you missing clips or images? If so what troubleshooting have you done? If not then again, looking at these logs, you will find events that may cause you concern but without an actual issue on the server you are searching for a non-existent issue.

We can not assist in troubleshooting an issue that does not exist and how would we know if our troubleshooting worked if there is no issue to start with? We couldn't tell if it got better or worse. I strongly suggest staying away from reading the event log if you have no issues.You'll be chasing non-existent issues forever as there are always messages that may look like they're causing an issue.

(CID:151061466)

[DCIM_Support]

Thanks but that's not really an answer, choosing to ignore something doesn't make it go away. The concern I have is that the user (User [tc4z1Whipu]) is not even configured on the Bot  

(CID:151061675)

[DCIM_Support]

I agree, Was just letting you know what was said on another post related to the same topic.

(CID:151061924)

[DCIM_Support]

This is specifically related to Netbotz appliances. If you've ever restored DCE from backup, perhaps changed logins or certs, this could occur. Also, if you have a Netbotz appliance on your network that was not previously configured to post to this server, this could occur.

Locate this netbotz appliance, login to it with Advanced View, remove the DCE's that it's posting to, and rediscover it in this DCE - You do not need to delete it in DCE first. This should resolve the issue.

(CID:151062985)

[DCIM_Support]

This question is closed for comments. You're welcome to start a new topic if you have further comments on this issue.