I am trying to get xterm to work on sles 11.2. I did it recently on 10.3 and it was really simple but nothing works on 11.2.
On 10.3 I installed xterm on the server and ran xming for windows on my local PC. Then from a putty went to SSH > X11 > Enable X11 forwarding. When I connected to the server I could run xterm and it worked straight away.
However, when I do the same thing on Sles 11.2 and I try and run xterm it says the display isn't set.
Is there something special I need to do for 11.2 to make it work. There isn't any firewalls enabled so this isn't the problem.
Thanks for any help you can provide.
UPDATE
I have changed the SSH config files as suggested by twalberg but still no luck.
In /etc/ssh/ssh_config I have the following
Host *
# ForwardAgent no
ForwardX11 yes
ForwardX11Trusted yes
In /etc/ssh/sshd_config I have the following
X11Forwarding yes
I then restarted ssh using /etc/init.d/ssh restart and then performed the same steps as mentioned in the question with putty but still getting the display not found
I suspect sshd on your 11.2 box is configured to not allow X11 forwarding for security reasons. It needs to be enabled on the client side (which you are doing) and on the server side (in sshd_config) for it to work, so you might need to tweak the config on the SLES system.
I've managed to find out the problem. I need to install x-core package in yast. Didn't need to do this in sles 10.3 but apparently for 11.2 you do.
Thanks all for your help and suggestions.
Related
Have MAMP 6.3 on an updated macOS 11.2.1
The Configuration popup launches
Web server is working but that is it.
MySQL is not running although indicates Server is 5.7.32
Ports 80 and 30036 or 8888 makes no difference
http://localhost:8888/MAMP ... unable to connect
http://localhost:8888/MAMP/phpmyadmin.php ... unable to connect
Seems like I'm the only one for some reason as doesn't seem to anything I can find
Thanks
Try removing all log files inside of the MAMP/db/mysql directory and restart MAMP.
I'm also using the same MAMP and macOS version as you but it's working.
This is a long story.
I use an old OSX 10.4.11 machine (Power PC) as a web server. Very low use.
It runs X11 at 1.1.3 (XFree86 4.4.0).
For several years I used X-forwarding to show log traffic on a newer Mac Intel machine (Mac mini). At some point after about 2006 this just stopped working. I have never tried to upgrade the 10.4.11 machine as it met and continues to meet my needs for a low cost Web server.
Meantime XQuartz has come and been through several new versions, as has MacOS. Currently I have MacOS 10.13.6 and XQuartz 2.7.11 on the Mac Mini. I am revisiting why the long-defunct X-forwarding sessions to OSX 10.4.11 stopped working.
I find I can do X-forwarding fine from my Linux 18.04 box, which was a surprise. I have spent a lot of time trying various approaches to resolving the issue. It occurs to me that the 10.4.11 setup may just be too old, and therefore incompatible. Hence my question: "mac osx 10.4.11 with x11 1.1.3 (XFree86 4.4.0) - is this compatible to do X-forwarding from Mac OS 10.13.6?".
Any comments will be much appreciated.
I am answering my own question.
I spent several days looking at logs from ssh -v -X user#hostname, with -vv and -vvv for more log info. I also tried the ssh -Y variants of that command.
Reading extensively from stackexchange and elsewhere, I restored and re-edited the ssh_config and sshd_config files on both server and client hosts several times, and coded shell scripts to restart sshd.
The insurmountable problem was that $DISPLAY was not being set up correctly on the client. This is what led to my question.
The only way I could get X-forwarding to work with my OSX 10.4.11 PPC client was:
1) ssh -f user#hostname /usr/X11R6/bin/xterm
then
2) run my local commands on the client from that window (nsu and nsu-go).
I also had to add the correct path to all my commands, including /usr/X11R6/bin for xterm as above, and ~/bin to my commands on the client.
The package I was working with was https://sourceforge.net/projects/nsu/ where detail changes are required.
All,
I do have linux servers which do not have GUI installed and sometimes I just need to use graphical applications, such as installers. So the option is to use X11 forwarding. My question is how X11 forwarding is used with MacOS High Sierra today. What options or applications you do use? On windows I would probably use Xming or similar but are such server also available on MacOS? I know about XQuartz, but I'm reluctant to install it.
XQuartz is standard. It used to come bundled with the OS, but Apple removed it back around Mavericks. It generally works great.
You want to use:
ssh -Y [remote_server]
and you may have to add to your $HOME/.ssh/config file:
Host [remote_server]
ForwardX11 yes
ForwardX11Trusted yes
When I run vagrant up from the command line, it is a crap shoot at best as to whether vagrant will boot up or not. It stops at this line:
SSH auth method: private key
And then may or may not include this line:
Warning: Remote connection disconnect. Retrying...
As I said, sometimes it works and sometimes it does not. Why is this problem happening? For the record it would happen (less often) on my production MacBook at work.
Can I maybe change the auth method if there is no good answer for this? Trust me I have been looking and not found any answer on this yet.
whats happening is the following :
vagrant up will spin a new VM, basically it contacts virtualbox (or the specific provider) and run command to start a VM
the VM will start on the virtualbox side
note: if you run form a command line terminal in macos, you can see the title switching from 'Ruby' to 'VBoxManage'
the VM takes some time to start
because the VM does not send a specific signal when its done, vagrant will check at regular interval if the VM is fully booted and available to ssh-in
once the VM is available, vagrant can run the ssh command and complete the config (network, shared folder, etc...)
so in your case, the VM takes a bit longer to boot (this can be due to high activity on your mac, specific setup of the VM that runs on boot ...)
Basically this is harmless and is not necessarily a bad sign.
Please look at my accepted answer on this. It turns out that this was a memory allocation issue, and I only discovered it when watching the terminal for the VM provider (VirtualBox). Once I closed some programs I was (generally) able to boot up just fine.
There seems to be an incompatibility problem with Vagrant/VirtualBox & the Windows Hypervisor Platform feature in Windows 10
I had this problem and this is how I got get Vagrant & WSL2 working side by side
I have the following environment:
Hardware Virtualization enabled in BIOS
Windows 10 (Insider Program with Release Preview Channel)
-- Windows 10 with WSL 2 Version 10.0.19041 Build 19041
VirtualBox 6.1.12
-- Extension Pack Installed
Vagrant 2.2.9
These are the settings that worked for me:
Windows Hypervisor Platform: Off
Virtual Machine Platform: On
Windows Subsystem for Linux: On
a bit of a background to my issue:
I'm on a OSX El Capitan and I installed openssh7.1 using homebrew, placed all my keys in the ~/.ssh folder, and created ~/.ssh/config to identify each host and the key to be used to authenticate.
When using the terminal, I simply use $ ssh {hostname} and it connects me where I need to be. But when I try to connect from installed applications (like Sequel Pro, FileZilla, XCode) then I'm just unable to connect at all..
I don't even get any feedback from those applications! I'm feeling lost here, anyone has any piece of advice?
FYI, I symlinked /usr/local/bin/ssh to /usr/bin/ssh (and all other openssh binaries as well)