Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
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.
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.
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.
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?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.