It's typically due some type of portscanner application (either by design or malicious) running elsewhere on the network and attempting to make a connection to Avamar that the system is unable to process, generating the message.
If the portscanner program is sending packages to the event listening ports of Avamar grid, Avamar will try to explain this package as an incoming event, we can safely ignore the message.
Phukon
337 Posts
0
May 25th, 2010 12:00
Hi
It's typically due some type of portscanner application (either by design or malicious) running elsewhere on the network and attempting to make a connection to Avamar that the system is unable to process, generating the message.
If the portscanner program is sending packages to the event listening ports of Avamar grid, Avamar will try to explain this package as an incoming event, we can safely ignore the message.
Regards,
Bashan