Dude Server 3.6 can't connect to Dude agent 3.6 on RB750G

RouterOS The Dude
1

I’ve seen a number of postings regarding this issue, but nothing in the way of a solution

I’ve got an RB750G running on a remote network, with dude agent installed and running. I am attempting to connect to the agent remotely via the 750’s external IP address, but have had no success.

There was one posting saying to set up a separate account for the dude server in order to log into the agent. I tried that, but was unable to connect.

I’ve open port 2210 on all known firewalls between my dude server and agent tried to log in to the agent both securely and non-securely
I’ve set up a separate account on the dude server and tried to log in to the agent both securely and non-securely
I’ve set up a separate account on ROS on the 750 tried to log in to the agent both securely and non-securely
I’m having no success at all. The best I get is an error saying “invalid username or password”. The worst I get is a message stuck on “connecting”

I’ve run torch on the external port of the ROS and I see a brief attempt at a connection from my dude server ip address on port 2210, so something is getting through…

I’m doing something wrong…but what is it?

Specs:
RB750G running ROS4.5 with dude agent 3.6 installed and running (as far as I can tell)
Dude 3.6 running as dude server

2
  1. You should connect to your RB750G running on a remote network (the new agent for a sample whith IP 192.168.168.100) from local The Dude client station.
  2. You should setup new user/password/ip for your The Dude server connection on the new agent - your RB750G ip 192.168.168.100 (for a sample client_user/mysuperpass).
    new_agent.png
  3. Disconnect from your RB750G ip 192.168.168.100 and connect to main The Dude server. Then setup new agent
    main_server.png
3

Hey, thanks for the quick reply!

A few more questions:

  1. You should connect to your RB750G running on a remote network (the new agent for a sample whith IP 192.168.168.100) from local The Dude client station.
  • Can you extrapolate on this? It sounds like you are suggesting I connect with my local dude client to the remote dude agent. This is exactly what I cannot do, and I don’t know why.

You are using an internal IP address for your example. I’m trying to use the remote network’s external IP address to access the dude agent. Would that make a difference? Do I need to VPN into the remote network for this to function?

Here’s what I did:

Using Winbox, log onto the remote RB750
Set up a new user with full privilages
closed winbox

Open the dude, log onto local dude client as admin (logging on as remote user doesn’t work)
create a new admin, user name and password matching that of the new user I just set up on the remote RB750 (as per your instruction #2)
created a new agent username and password matching that of the new user I just set up on the remote RB750 (as per your instruction #3)

It doesn’t work, but that’s because I think I’ve messed up step 1.