Hello!

We experienced today an issue with Dude server v6.41 on CHR running on ESXi 6.x and Dude client v6.41 on Windows server 2012R2 Standard x64.

Probably it worked fine because it send us some notification but we can't connect to it using Dude client. It was verified from 2 locations.
We noticed that:
1. WebBox working fine - no CPU load observer on the Charts.
2. Winbox working fine - we logged in and looked into the logs - nothing suspicious.
3. Dude client saying - "connecting".

What was done:
1. Dude was disabled and enabled back - doesn't help.
2. Database backup was made - nothing changed.

What helped:
1. ROS restart was initiated from Winbox GUI - 2 times.
2. ROS restart was initiated from Winbox terminal - 3 times.
3. After ~ 3-5 minutes ROS restarted and Dude client has successfully connected to the Dude server.

Maybe someone else experienced similar issue?


Thank you!

Try running the Dude client as an administrator. I have had issues with the due version different than the ROS version. Running the client as an administrator seemed to fix it.

Hello, allstarcomps!

Thank you for reply! I have added additional information about Dude client in the initial post.

Issue you describing is related to the case that for Dude client auto-update administrative privileges are required: Connect the same version of the client, with several different version CHR The Dude servers?

In our case we used Dude client version same as the Dude server v6.41. Dude client connected automatically, without its restart after ROS rebooted.


Thank you!