setup is unable to acces the manager

[mohasmr]

Discussed in #12465

^{Originally posted by mohasmr February 29, 2024}
i have a problem i cant even identify the causes when i install a desktop to linked to a distributed manager and try to join it to an existing grid i have problem of connectivity
manager ip:192.168.10.10
desktop ip : 192.168.10.90
they are on the same network , in the manager console i puted the right configuration

even i try with so-firewall-minion --role=DESKTOP --ip=192.168.10.90 there is no changes
i even tryied to shutdow the firewalld and droped all iptables but nothing
the two security onion(desktop and manager) cant even ping each others
please to help im stuck :'(

[kevinelwell]

I have the same challenge. Unable to join the analyst desktop to grid.

[kevinelwell]

I was able to solve my challenge. When prompted to join the desktop vm to the grid, I selected yes. It failed. I ran the command "so-firewall-minion --role=DESKTOP --ip=192.168.1.10" on the manager vm. The command ran successfully. I then went back to the desktop vm and selected "try again" and it ran successfully. I then was able to see the desktop vm in the grid.

[mohasmr]

is your manager installed like a distributed manager or a standalone ??

[kevinelwell]

Standalone

[InfosecGoon]

Okay, just to make sure that I'm answering the right question - you're trying to join a Security Onion Desktop to an existing Security Onion grid? How did you install the Desktop?

[mohasmr]

I got 2 different pcs and security onion desktop is installed and the manager is installed on the other one ,every security onion is on bridged mode and is connected on the same Ethernet cable , all the virtual cards and the ethernet are on the same ip range which is 192.168.10.0/24
In the installation of security onion desktop i have chosen to join it to an existing grid which is SO MANAGER
I noticed that the 2 SO VMS cannot see or even ping on each other

[mohasmr]

[mohasmr]

the issues caused by a missconfiguration on the switch the so-firewall-minion --role=DESKTOP --ip=192.168.10.90 working correctly