This hangs on a windows 10 client, but I really do need to use windows 10 client lately:
ssh -4 -X -i my.pem firstname.lastname@example.org -o ConnectTimeout=604800
Contrastingly, this worked good on a linux ubuntu client in the past:
ssh -X -o ConnectTimeout=604800 -i "my.pem" email@example.com
The microsoft docs link to the OpenBSD docs. However the problem seems to be windows 10 specific. I really need to stay connected a long time.
There was no effect by moving parameters around, nor by the -4 presence or absence, nor by removing the = character.
This interestingly worked good on a windows 10 client, but is missing the option that I require:
ssh -4 -X -i my.pem firstname.lastname@example.org Welcome to Ubuntu 16.04.5 LTS (GNU/Linux 4.4.0-142-generic x86_64)
The big question is, what is the right format for the family of command line options "-o" here on windows 10 clients? And why isn't it identical to linux clients?
I understand there might be a file to contain these options (-o options are a long list of possible strings). However the OpenBSD docs do not and would not be able to describe where to put this file on windows 10. The file name and directory on windows 10 to use would be a mystery to me for now. I imagine the bsd docs might explain the format of this file though.
UPDATE: I tried making a config file with the setting in it, same format as command line, and then launched it 4 different ways and still hang:
ssh -F .config -4 -X -i my.pem email@example.com -o ConnectTimeout=604800 ssh -F ".config" -4 -X -i my.pem firstname.lastname@example.org -o "ConnectTimeout=604800" ssh -F .config -4 -X -i my.pem email@example.com ssh -F ".config" -4 -X -i my.pem firstname.lastname@example.org
Another ssh command I will be needing (below) also hangs. I need to do port forwarding, so I can run a browser process in my client computer, but use the server's web server to host my jupyter notebooks for machine learning projects. It's a different ssh command but it has the same hanging problem. Maybe the ssh isn't really supported on windows 10, and if that's true, I going to abandon windows 10 and go back to building myself a linux workstation for a client, because I know it works right. This makes me mad, as it's such a time waster.
ssh -i my.pem -N -f -L localhost:8889:localhost:8889 email@example.com
UPDATE: With -vvv parameter it shows to be hanging where port 22 is not sending something back to the client:
ssh -4 -X -i my.pem firstname.lastname@example.org -o ConnectTimeout=604800 -vvv OpenSSH_for_Windows_7.7p1, LibreSSL 2.6.5 debug3: Failed to open file:C:/Users/mrcod/.ssh/config error:2 debug3: Failed to open file:C:/ProgramData/ssh/ssh_config error:2 debug2: resolve_canonicalize: hostname 192.168.1.111 is address debug2: ssh_connect_direct: needpriv 0 debug1: Connecting to 192.168.1.111 [192.168.1.111] port 22. debug2: fd 3 setting O_NONBLOCK
Has anyone been able to connect to a unix server from windows 10 yet via ssh? They must have. This isn't an unusual task in 2019, with AWS being the innovating flagship of cloud systems, and web sites using linux servers in the majority globally. I'm not sure why nobody appears to know anything. My english here isn't weak either.
I'm not seeing any real help from the LAST items coming out of the debug output.
For lack of any other ideas submitted here, a next step seems to be to experiment smore more with putting another config file in additional places (directories) that the debug output is saying it was looking for it and see if any settings look possible for fixing the hanging on port 22 problem here. I don't think there is much to go on here really, so I'm pessimistic unless someone chimes in that actually uses ssh on windows 10, since openbsd is what this software was compiled from on windows 10 according to microsoft links I've provided.