• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

Thanks Musky

Pitbully

[H]ard|Gawd
Joined
Nov 29, 2011
Messages
1,155
Thanks to your guide I was able to get my second rig up and running Ubuntu last night and folding. It was much less painful then I though it would be. Since I'm a total linux newbie, I did have couple problems, but nothing I couldn't figure out on my own with the help of your guide. Next step is figuring out how to telnet on my network so I can get my second monitor back! :confused:
 
Thanks to your guide I was able to get my second rig up and running Ubuntu last night and folding. It was much less painful then I though it would be. Since I'm a total linux newbie, I did have couple problems, but nothing I couldn't figure out on my own with the help of your guide. Next step is figuring out how to telnet on my network so I can get my second monitor back! :confused:

You will want to use ssh, not telnet. Musky has that configuration as part of his guide. You can use Putty as an ssh client from windows.
 
And do use screen. It took me about a week to figure that out. I think that is also in muskyguide.
 
ssh (although what is in the guide is a lot more setup than I do - I just sudo apt-get install openssh-server and call it done), and screen are both in the guide. If you really like the GUI, try out NoMachine NX, which is also in the guide - it uses ssh, but connect with a graphical interface instead of just command line.

I am glad it was helpful for you.
 
I use ssh to connect to my box. Using screen is killer. Box is setup to run fah on boot. Piece of cake!
 
ssh (although what is in the guide is a lot more setup than I do - I just sudo apt-get install openssh-server and call it done), and screen are both in the guide. If you really like the GUI, try out NoMachine NX, which is also in the guide - it uses ssh, but connect with a graphical interface instead of just command line.

I am glad it was helpful for you.

I downloaded NoMachine NX on my main rig last night, I just need to get it going on my Ubuntu rig, I may try it tonight and see how it goes.
 
I downloaded NoMachine NX on my main rig last night, I just need to get it going on my Ubuntu rig, I may try it tonight and see how it goes.

It is somewhat surprisingly easy. You do need ssh for it to work, though. It is probably the best "remote desktop" app I have ever used.
 
It is somewhat surprisingly easy. You do need ssh for it to work, though. It is probably the best "remote desktop" app I have ever used.
Alright, that's it - next weekend's project for me! It's got Musky's stamp of approval, which means I've got to try it.
 
Ok I got SSH installed/running on the Ubuntu box and went through the config/install with NoMachine, but can't connect to my Ubuntu machine, I get the following from NoMachine.

NX> 203 NXSSH running with pid: 5768
NX> 285 Enabling check on switch command
NX> 285 Enabling skip of SSH config files
NX> 285 Setting the preferred NX options
ssh: connect to host 192.168.1.102 port 22500: Connection refused

102 is my Unbuntu machine, mine is 101. I think I got everything right on the Unbuntu rig, I followed everything in your guide and got no surprises, so I am going to assume everything is kosher there. I don't think I have the settings in NoMachine correct though.
In the config screen I have;
General Tab
Host: 192.268.1.102 Port 22500
Desktop
Windows RDP
Under the "Windows Settings" I'm unsure as to what goes here, is this info about my machine or the Ubuntu machine?!? I have in there my login for Unbuntu machine and its IP (192.168.1.102) but this is obviously not working.
Authentication;
I have "use following credentials" checked, with my Ubuntu name/pw there, but it seems to add its own PW that's like 15 digits long.
Session type;
Run Desktop

edit: ok while typing this I've tried almost every freeking combination I can see, so I'm going to assume somethings not right with the Ubuntu box. I've checked over the SSH config again and can see nothing wrong, it seems to be working fine, (from what I can tell). I can possibly assume theres something wrong with the NoMachine install on the box?!?
 
Host: 192.268.1.102 Port 22500

Hopefully that is a typo on the IP address. Is ssh set up to use port 22500? Can you connect to the Ubuntu box with PuTTY on that port?
 
Yes, it was a typo and yeah I set it up for port 22500, no, I can't connect w/putty.

I double checked all the settings in SSH on the ubuntu box, I have no freeking idea whats going on. Getting late now though, I'll probably mess with it more tomorrow.
 
With NX, that is to be used with their client, not the RDP/MSTSC.EXE in windows.

If you cannot connect using putty, I would double check that sshd is running and that the port is correct.

To restart ssh:
Code:
sudo /etc/init.d/ssh restart
This command shouldrun and no errors present.

To verify the port:
Code:
sudo nano /etc/ssh/sshd_config

Scroll to this:
Code:
# What ports, IPs and protocols we listen for
Port 22

Sometimes you make a typo:)
 
When I try to restart SSH I get this:

Rather than invoking init scripts through /etc/init.d, use the service(8)
utility, e.g. service ssh restart

Since the script you are attempting to invoke has been converted to an
Upstart job, you may also use the restart(8) utility, e.g. restart ssh
ssh start/pre-start, process 2039

everything else in the config seems to be right though....
 
sounds so "complicated" to me .. :D ..
I don't know if I can use windows remote access to ubuntu box or not, but it works with VNC.
All you need to do is setting remote access on your ubuntu box as follow:

Preference --> remote control -->
- allow others to use your desktop --> check box
- allow others to control your desktop --> check box

- ask you for confirmation --> uncheck box --- this would help when you are NOT at the box.
- require password --> check box
- configure network automatic to accept connection --> check box.

I think this should work with windows remote too.
 
When I try to restart SSH I get this:

Rather than invoking init scripts through /etc/init.d, use the service(8)
utility, e.g. service ssh restart

Since the script you are attempting to invoke has been converted to an
Upstart job, you may also use the restart(8) utility, e.g. restart ssh
ssh start/pre-start, process 2039

everything else in the config seems to be right though....

sudo service ssh restart
 
or sudo restart ssh

That is just telling you that you could restart ssh in a couple of different ways.
 
Back
Top