![]() ![]() ![]() If you are able to log in, it already confirmed the system is on and your credentials are good. You can now choose to reboot or troubleshoot some more. The obvious thing when you don’t have ongoing computations or unsaved work is to reboot. If you are not alone, best to contact the others, but you can also look at running processes with ps or one of these to see what is running: top Unfortunately, who or w don’t include everything, so you can use: ps -fp $(pgrep "x2goagent|nxnode|bash|tcsh") | egrep -v "^(root|nx)" You should however also consider that other users may be using the system, so please always check that first. If you are not getting to the desktop screen using either McGill VPN + NoMachine or X2Go, you can try the other one. With X2Go, also try a remote session (e.g. If you’re having difficulties with NoMachine but it was working before, you can try restarting the NX server: sudo systemctl restart rvice MATE, KDE, GNOME, etc) if you were using “ connect to the local desktop”. If it appears you are connecting, but the local session (that includes connecting with NoMachine, and with X2Go with the option “ connect to the local desktop”) is unresponsive or giving you trouble, you can restart the X desktop manager. It’s not quite as drastic as rebooting ALTHOUGH it will affect other users with remote sessions, so DON’T try this unless you are indeed the only person logged in (use the ps command to check): sudo /usr/sbin/service lxdm restart This will end your local session, similarly to doing ctrl-alt-backspace when at the computer. If a process is obviously causing a problem, you can stop it with: kill Otherwise, once you’re logged in via a terminal, you can look at running processes with top or ps commands. Where stands for the process ID # listed by ps or top. One example is the screensaver process, which if frozen will prevent you from logging in, possibly showing only a black screen, or the lock screen. Running NxServer 3.3.0-8 (node and client installed) If you’re able to log in via ssh through login.bic, but you get a timeout error or connection refused when trying to connect directly to your workstation while using the MGill VPN, it may be useful to verify your VPN IP in case McGill added new IP ranges that would be blocked by the workstation firewall.Fedora 10 installed from LiveCD, updates applied If nothing in the list of processes pops out at you, probably best to ask for help. Logging in with nxclient, it shows in the message box: The connection with the remote server was shut down. Unix, GNOME, LAN, 800圆00, use custom settings is not checked Host is listed by it's static IP, port 22 Please check the state of your network connection. No check boxes are checked - disable encryption, disable zlib compression, http proxy, grab kb, disable direct draw, disabled deferred screen updates. #Nomachine connection refused password#. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |