SSH timeout
 

I just installed my first ever install of Linux (used Fedora) and am using SSH to access it from my Windows machine. It keeps timing out. Is there something I need to set to make it available all the time?

I was able to get the SSH on and to autostart just fine but when I boot up it only works half of the time. I have to move the mouse and keyboard on the Linux machine before it will respond.

Also if I am working on my Windows machine and don't move the mouse or keyboard every now and then it doesn't work.

Anything I need to set?

-N8

Could you be a bit more specific? Are there any error messages for it? Try:
What exactly happens when you use it and it manages to work?

Timing out after a certain amount of time after successfully connecting or timing out as in never managing to connect?

The error messages are on not on machines trying to connect. It says The Network connection has timed out.


The situations where it happens is when I first boot and have not used the keyboard. Or if the machine has been sitting for a while I need to move the mouse or use the keyboard. Also, if I am using SSH I need to keep using it. If I let it sit for too long then try to come back I have to "re-wakeup" the Linux machine.



-N8

is the fedora machine a laptop.

perhaps it has some crazy profile where it goes to sleep/ hibernate after :30 minutes or so.

i am not in front of my fedora laptop now but i remember when the lid is shut and the power is not plugged in it would immediately go to sleep. i had to look thru the power options or screensaver or something to disable it.

I'm guessing power options...
 

I can't get a fix on it but I bet you're right. It's a tower, but it's got to be some kind of power saving setting. Thanks for all your help.

-N8

Well no, that wouldn't turn SSH into a temperamental monster. If its a power saving reason from the information you've given I'll buy you a beer.

I'll explain; the power settings could only be a possible reason if you didn't have to jiggle the mouse about after boot, too. The fact that you have to do this straight after boot to get it to work suggests a different reason.

Now, perhaps you'd like to try and connect a few times to replicate the error, then walk over to the Fedora box and give me the output I asked for. Also, could you try connecting from another machine?