This issue and the logging look very familiar. Did you also submit a support ticket?
It might help to make sure port 3121 is open outbound on the client system & inbound on your Protect console system. It could possibly just be complaining about the tracker service being able to communicate with the console.
well spotted. i posted this first but do indeed have a support ticket so will continue with that to resolve the problem