Remote Desktop to Fedora 28?

[DustinB3403]

To add a user to a specific group

useradd -G {group-name} username should work. You likely will need to run under sudo to do this though.

[JaredBusch]

@dustinb3403 said in Remote Desktop to Fedora 28?:

To add a user to a specific group

useradd -G {group-name} username should work. You likely will need to run under sudo to do this though.

I like to use sudo gpasswd -a username groupname personally. but it all gets the job done.

[siringo]

@gjacobse said in Remote Desktop to Fedora 28?:

Thought I would give this ago also... this is what I ran into

This is from Windows to Fedora.

Yep, that is what I was getting also. Can you log in with root?

I was getting that error & the one I posted above. I rebooted several times for various reasons and things started to become a bit more reliable.

Thanks everyone for the help.

[gjacobse]

@siringo said in Remote Desktop to Fedora 28?:

@gjacobse said in Remote Desktop to Fedora 28?:

Thought I would give this ago also... this is what I ran into

This is from Windows to Fedora.

Yep, that is what I was getting also. Can you log in with root?

I was getting that error & the one I posted above. I rebooted several times for various reasons and things started to become a bit more reliable.

Thanks everyone for the help.

Here's what I have done since.

Added my <USER> to the wheel usergroup and rebooted. Since, I seem to be able to sign in. but yes,.. I was able to sign in as <ROOT>

[stacksofplates]

@dustinb3403 said in Remote Desktop to Fedora 28?:

To add a user to a specific group

useradd -G {group-name} username should work. You likely will need to run under sudo to do this though.

If you don't add a -a it removes all secondary groups other than the one you define. You pretty much always want to do usermod -aG group user

[black3dynamite]

@stacksofplates said in Remote Desktop to Fedora 28?:

@dustinb3403 said in Remote Desktop to Fedora 28?:

To add a user to a specific group

useradd -G {group-name} username should work. You likely will need to run under sudo to do this though.

If you don't add a -a it removes all secondary groups other than the one you define. You pretty much always want to do useradd -aG group user

I guess using sudo gpasswd -a username groupname avoids remembering to add -aG?

[stacksofplates]

@black3dynamite said in Remote Desktop to Fedora 28?:

@stacksofplates said in Remote Desktop to Fedora 28?:

@dustinb3403 said in Remote Desktop to Fedora 28?:

To add a user to a specific group

useradd -G {group-name} username should work. You likely will need to run under sudo to do this though.

If you don't add a -a it removes all secondary groups other than the one you define. You pretty much always want to do useradd -aG group user

I guess using sudo gpasswd -a username groupname avoids remembering to add -aG?

Yeah. I've always done usermod but it's personal preference.

However the only way I know of to remove a user from a group is gpasswd

[gjacobse]

It occurred to me just now, that you should not need a full reboot after adding the <user> to your group... All that should be needed is a log out/in

@scottalanmiller or @JaredBusch - please correct me if I have that incorrect.

[JaredBusch]

@gjacobse said in Remote Desktop to Fedora 28?:

It occurred to me just now, that you should not need a full reboot after adding the <user> to your group... All that should be needed is a log out/in

@scottalanmiller or @JaredBusch - please correct me if I have that incorrect.

Log out and log in is all that is required to apply new group permissions.

[gjacobse]

Yes - I learn. here is the same command - but in just three lines:

sudo dnf install xrdp -y
sudo systemctl start xrdp | sudo systemctl enable xrdp
sudo firewall-cmd --permanent --add-port=3389/tcp | sudo firewall-cmd --reload

[travisdh1]

@gjacobse said in Remote Desktop to Fedora 28?:

Yes - I learn. here is the same command - but in just three lines:

sudo dnf install xrdp -y
sudo systemctl start xrdp | sudo systemctl enable xrdp
sudo firewall-cmd --permanent --add-port=3389/tcp | sudo firewall-cmd --reload

You can make anything a one line command if you want. Back when running IRIX if hit their 512 character limit and have to script a single command when compiling open source tools on that. Thankfully haven't run into that issue recently!

[stacksofplates]

@gjacobse said in Remote Desktop to Fedora 28?:

Yes - I learn. here is the same command - but in just three lines:

sudo dnf install xrdp -y
sudo systemctl start xrdp | sudo systemctl enable xrdp
sudo firewall-cmd --permanent --add-port=3389/tcp | sudo firewall-cmd --reload

You can shorten the second. If you do

system to enable --now xrdp

It will enable and start the service at the same time.

[stacksofplates]

@gjacobse said in Remote Desktop to Fedora 28?:

Yes - I learn. here is the same command - but in just three lines:

sudo dnf install xrdp -y
sudo systemctl start xrdp | sudo systemctl enable xrdp
sudo firewall-cmd --permanent --add-port=3389/tcp | sudo firewall-cmd --reload

Also why are you using a pipe?

[travisdh1]

@stacksofplates said in Remote Desktop to Fedora 28?:

@gjacobse said in Remote Desktop to Fedora 28?:

Yes - I learn. here is the same command - but in just three lines:

sudo dnf install xrdp -y
sudo systemctl start xrdp | sudo systemctl enable xrdp
sudo firewall-cmd --permanent --add-port=3389/tcp | sudo firewall-cmd --reload

Also why are you using a pipe?

@stacksofplates said in Remote Desktop to Fedora 28?:

@gjacobse said in Remote Desktop to Fedora 28?:

Yes - I learn. here is the same command - but in just three lines:

sudo dnf install xrdp -y
sudo systemctl start xrdp | sudo systemctl enable xrdp
sudo firewall-cmd --permanent --add-port=3389/tcp | sudo firewall-cmd --reload

Also why are you using a pipe?

That's a good point. For your continuing BASH shell learning @gjacobse, a pipe ~ | ~ passes the output of the first command to the one after it. So ls -lha | grep ".." lists all files including the hidden ones and then searches for any with .. in the string returned. When you just want to run commands one after the other, the proper concatenation been is &&

[black3dynamite]

@travisdh1 said in Remote Desktop to Fedora 28?:

@stacksofplates said in Remote Desktop to Fedora 28?:

@gjacobse said in Remote Desktop to Fedora 28?:

Yes - I learn. here is the same command - but in just three lines:

sudo dnf install xrdp -y
sudo systemctl start xrdp | sudo systemctl enable xrdp
sudo firewall-cmd --permanent --add-port=3389/tcp | sudo firewall-cmd --reload

Also why are you using a pipe?

@stacksofplates said in Remote Desktop to Fedora 28?:

@gjacobse said in Remote Desktop to Fedora 28?:

Yes - I learn. here is the same command - but in just three lines:

sudo dnf install xrdp -y
sudo systemctl start xrdp | sudo systemctl enable xrdp
sudo firewall-cmd --permanent --add-port=3389/tcp | sudo firewall-cmd --reload

Also why are you using a pipe?

That's a good point. For your continuing BASH shell learning @gjacobse, a pipe ~ | ~ passes the output of the first command to the one after it. So ~ ls -lha | grep ".." ~ lists all files including the hidden ones and then searches for any with .. in the string returned. When you just want to run commands one after the other, the proper concatenation been is ~ && ~

What does ; means after a command?

[travisdh1]

@black3dynamite said in Remote Desktop to Fedora 28?:

@travisdh1 said in Remote Desktop to Fedora 28?:

@stacksofplates said in Remote Desktop to Fedora 28?:

@gjacobse said in Remote Desktop to Fedora 28?:

Yes - I learn. here is the same command - but in just three lines:

sudo dnf install xrdp -y
sudo systemctl start xrdp | sudo systemctl enable xrdp
sudo firewall-cmd --permanent --add-port=3389/tcp | sudo firewall-cmd --reload

Also why are you using a pipe?

@stacksofplates said in Remote Desktop to Fedora 28?:

@gjacobse said in Remote Desktop to Fedora 28?:

Yes - I learn. here is the same command - but in just three lines:

sudo dnf install xrdp -y
sudo systemctl start xrdp | sudo systemctl enable xrdp
sudo firewall-cmd --permanent --add-port=3389/tcp | sudo firewall-cmd --reload

Also why are you using a pipe?

That's a good point. For your continuing BASH shell learning @gjacobse, a pipe ~ | ~ passes the output of the first command to the one after it. So ~ ls -lha | grep ".." ~ lists all files including the hidden ones and then searches for any with .. in the string returned. When you just want to run commands one after the other, the proper concatenation been is ~ && ~

What does ; means after a command?

&& will stop if the preceding command throws an error while a semicolon will run the following command no matter if the first one throws an error.

[AdamF]

Does this make a difference if I am running Cinnamon on the Fedora workstation? I installed via the instructions provided in this thread. I can make a connection, but when the screen comes up, it is just a blank window with a blank button. Then clicking the blank button, brings me to the screen below. I cannot type anything in the first drop down. I use my fedora username and password (added to the wheel group) but it just goes back to the blank window.

[dafyre]

I just did a fresh install of Fedora 28 to update my instructions for this, however, I've discovered the by default Fedora 28 has switched to Wayland, and there's no working VNC server that I am aware of that works with it.

This may be part of the problem.

[FATeknollogee]

@dafyre said in Remote Desktop to Fedora 28?:

I just did a fresh install of Fedora 28 to update my instructions for this, however, I've discovered the by default Fedora 28 has switched to Wayland, and there's no working VNC server that I am aware of that works with it.

This may be part of the problem.

ScreenConnect also doesn't play nice w Wayland!

[black3dynamite]

@dafyre said in Remote Desktop to Fedora 28?:

I just did a fresh install of Fedora 28 to update my instructions for this, however, I've discovered the by default Fedora 28 has switched to Wayland, and there's no working VNC server that I am aware of that works with it.

This may be part of the problem.

Its been default to Wayland for awhile but you can switch it to Xorg.