You would have to re-authenticate yourself anyway to make sure. You need to arrange for your X authentication data to be passed from the user you logged in as to the user you used su to become. Probably somewhere on the route packets were dropped by network equipments. Ok got you point will try that out. A work around is to use autologin and screen. You run risks of man in the middle attacks during an outage. Please report it to us, and include the exact text from the error message box.
I turned off both the Linux server firewall and Windows 7 client firewall, but login still times out! If success, then you can be certain the issue is not at the Pi at least. So use autologin so putty can auto login on your behalf. It seems sometimes I can log in, but sometimes login times out! Remove these components from the equation and see if that solves the problem. And sometimes I even can't login, getting an error saying timeout. And in 6 seconds you are back right where you left off.
See for more information on this message. It can also occur if you are using in your connection. How you do this depends on your particular system; in fact many modern versions of su do it automatically. It can also occur if you are using keepalives in your connection. This may happen for genuine reasons: if the computer really has run out of memory, or if you have configured an extremely large number of lines of scrollback in your terminal. Other people have reported that keepalives fix this error for them. One way, and my preference, is the setup I show above.
What could be the reason for this problem and how can it be fixed? If you have alternative place that can setup a simple network to test ssh, such as a school, office or a friend's home, you can try to bring the Pi there and try ssh from other environment. Any idea what could be the cause for this issue. This can easily happen if you are using Pageant and have a large number of keys loaded into it, since these servers count each offer of a public key as an authentication attempt. Other people have reported that keepalives fix this error for them. I had a Linksys wireless router suffer this slow death and drop connections and restart them. I thought to myself I have wasted enough time on this problem. This is no longer supported, to prevent the possibility of a downgrade attack.
Tue Jan 09, 2018 10:44 am You need to log in to your router and look at the wifi setup pages if you have a guest network it will normally have a different name to the main network, you will also be able to see if it has wifi isolation activated , will say something like let users see the rest of my network, which will be un-ticked. If the network between your client and server goes down and your client then tries to send some data, Windows will make several attempts to send the data and will then give up and kill the connection. For example, it might happen if you pull the network cable out of the back of an Ethernet-connected computer, or if Windows has any other similar reason to believe the entire network has become unreachable. See for details of this. That kind of situation can only be resolved by the host's security team or waiting long enough for the automatic block to be removed, typically 24 hours. Try to turn of the network service in the machine by manually loggingin to that eaither via console or direct keyboard then stop the network service. Also I tried entering at different times of the day for two days and had the same problem, so I don't believe personally it is a connection issue.
You should contact your server's administrator and see whether they expect the host key to have changed. I had a Linksys wireless router suffer this slow death and drop connections and restart them. It looks like this: You make a snort of contempt, mash down Alt+F4 to close putty, Mash down F6. To avoid scenarios like this in the future, follow the following steps: 1. I've added this variable manually, it wasn't initially defined in the registy of my Windows. Could you post the output of the following commands? We have a hardworking team of professionals in different areas that can provide you with guaranteed solutions to a blend of your problems. If you are getting the error in the middle of session, it means that Windows network code killed an established connection for some reason.
It can also occur if you are using keepalives in your connection. Even better solution, in theory In theory you could script out this entire above process, so the terminal detects when it has been dropped, and does all the above steps for you on restoration of the internet connection. Now, after following your system, I am not encountering network errors anymore. I told that to Godaddy, and that maybe there might be some config file not giving me access because it believes I might have tried to hack inside, though it appears they didn't find anything. Every time the user or my domain account is logged into a newly imaged machine or the user's original machine, I get the following: Status: Connecting to ftp.
Putty can be life saver for windows folks. Windows also generates this error if it has given up on the machine at the other end of the connection ever responding to it. Which causes putty to disconnect. It may be worth checking the Event Log for diagnostic messages from the server giving more detail. It can also occur if you are using keepalives in your connection. When you get kicked out and auto login, you can reattach to your screen.