I upgraded my 6.34RC42 to 6.34 RTM, the Dude Client upgraded as it normally does, and I started receiving 10061 errors and not being able to connect.

As I have a backup, I decided to blow away my Dude CHR install, download the 6.34 .vdi file (running on VirtualBox here), resize the partition to a decent size as the default 64MB is uselessly small and start up a fresh Dude Server. I also blew away the Dude Client and installed a freshly downloaded copy. 10061 again.

Is there something seriously wrong with the Dude 6.34 that needs a point release to make it work? I didn't have these issues during the RC stages that often - and when I did, as with other people, disabling and re-enabling the Dude Server (and a pair of reboots) fixed the issues then. But not now...

(Yes, I can ping it and connect using WinBox both directly and through RoMON.)

I've never tried the pre-release versions, but I can confirm that I'm unable to connect with the Windows client to the Dude server. That's on three x86 machines. Then I discovered by doing /dude print, that the Dude server is not in fact running on any of them, even though installation of the server went fine.

Is there a way to manually enable it?

Thanks!

I've never tried the pre-release versions, but I can confirm that I'm unable to connect with the Windows client to the Dude server. That's on three x86 machines. Then I discovered by doing /dude print, that the Dude server is not in fact running on any of them, even though installation of the server went fine.

Is there a way to manually enable it?

Thanks!

Aha, yes - I see the following:

dude print
enabled: no
data-directory: dude
status:

It looks like The Dude in 6.34 RTM is completely bOrked.

What you can do is a "/dude set enabled=yes" which will enable The Dude Server in 6.34 RTM.

dude print
enabled: yes
data-directory: dude
status: running

And this holds after a reboot, too, which is "nice".

It would be handy if this was mentioned somewhere in the release notes, guys!

That's great news, HiltonT. However I can't seem to get the syntax right. I tried "/dude set enabled" but it sez: bad command. Would you pls confirm.... Thx.

Ok, I got it: "/dude set enable=yes"
That turns it on...

Ok, I got it: "/dude set enable=yes"
That turns it on...

Yeah, sorry - my bad. I have updated the command above now to a valid one.

I have now performed a number of RouterOS 6.34 installs and upgrades and can confirm that even though The Dude Server module is installed in the CHR images and appears to be enabled, no matter what you do - unless you run the "/dude set enabled=yes" it will not be running.

@HiltonT

Did you send in supout file from your dude server to support? If so tell me the ticket number and I'll check it.

hello friends .. good just installed 6.34.3 on all charges CCR1009-8G-1S well but could not access with Client DUDE, I would get the error can not connect - 10061
But stated "/ please enable = yes in Sept."
He solucionno no problem, you can now access.
Thanks for the input.