On the server-side I have the following sshd_config settings: I have tried all of the settings suggested in this almost identical question, but to no avail. Xauth is installed on the server, and after successfully connecting over SSH I do get a MAGIC-COOKIE in ~/.Xauthority. When I ssh in using -X (and add verbosity for troubleshooting -vvv), I successfully connect. When I try to run xclock it fails with an error of " Can't open display: localhost:10.0". This is a STDOUT error and not an error from the ssh -vvv. I do NOT receive any failed X11 attempts in ssh. Then I try to verify the $DISPLAY variable, but get no output (it's not set). It there some other setting somewhere that sets $DISPLAY properly? In this particular case, I can force the setting export DISPLAY=localhost:10.0, which then returns correctly after running echo $DISPLAY. Unfortunately, I still do NOT get any X-Windows program (e.g., xlcock) to come back. I still get the " Can't open display: localhost:10.0" error. ![]() I'm at a loss.For managing remote sessions in a professional way.Īuto-login by saving credentials, Auto reconnecting capability, etc. SSH client for Windows & fork from version 0.71 of PuTTY. SFTP and FTP client for copying a file between local computer & remote server. Multi-tabbed SSH client for copying files and directories. #1) Solar PuTTY, SuperPuTTY, PuTTY Tray, ExtraPuTTY Solar-PuTTY will help you in managing the remote sessions from one console with a tabbed interface. Solar-PuTTY provides a tabbed interface, thus, it will be easier to manage multiple sessions from one console.You will be able to automate all scripts after establishing the connection.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |