I need an sftp windows client and I just installed Bitvise. My windows 10 version runs on Parallels (version 10) on a Mac (OS X Yosemite version 10.10.5). As a test, I tried to open an ssh connection with the Bitvise client to the ssh server running on the Mac. I first went to the Mac, System Preferences -> Sharing and clicked on File Sharing and Remote Login (for all users, just to be sure). I can perfectly ping the Mac from Windows as well. Now when I try to open a connection from Windows to the Mac (Bitvise GUI or simply sftp from the command line), invariably I get this message.
The SSH2 session has terminated with error. Reason: Error class: LocalSshDisconn, code: ConnectionLost, message: FlowSshTransport: received EOF.
Does anybody knows what's going on? I couldn't find that error message anywhere. Just for your info I tried this from the command line
sftp mymacuser#my.mac.ip.address
And then again
ping my.mac.ip.address
works perfectly OK.
Thanks very much in advance.
Related
I am planning on using VS Code to work out of WSL2 installed on a remote machine. Before doing that, I wanted to check the direct connectivity from a Windows 10. I followed the instructions given in this blog. Also, the remote Windows 10 is on a VPN.
When I use the command ssh <username>#<IP address>, I get the message
kex_exchange_identification: read: Connection reset
Is there anything I am missing to get the connection going?
I have PyCharm Pro. I am trying to do remote development on a server. I have read the following Jetbrains tutorials:
Deploying Applications
Remote Development on Raspberry Pi
as well as the very helpful tutorial:
Remote debugging with pycharm the missing tutorial
While I seem to be able to set everything up, authentication fails when I try to connect to the remote server using the 'SFTP' protocol. I can make an SSH and SFTP connection from the CLI in a terminal so I know the ssh configuration settings are correct. However, in my case authentication requires ssh and having a Yubi key connected to my laptop. Does that make a difference?
Has anyone had a similar issue? If so, how did you resolve it?
On MacOS the challenge is where the IDE is getting it's ssh socket agent. To make this work in my case I have to launch the PyCharm Pro IDE from a terminal.
Go to '/Applications/PyCharm.app/Contents/MacOS' directory and launch with './pycharm'
I'm trying to connect my macOS (10.14.4) to L2TP server, but my Mac just pop up a window:
VPN Connection
Your connection failed because of an incorrect PPP setting. Verify your settings and try reconnecting.
photo
I have tried using my iphone to connect L2TP server and it worked perfectly (in the same local network).
Did anyone get the same issue before?
Delete your /etc/ppp/options and try to run this command.
sudo bash -c 'echo "plugin L2TP.ppp">>/etc/ppp/options'
i am connected with cygwin to a ssh server
there i want to open a application via x11-forwarding
i use xming as x11 server on my windows machine
now in putty i had the possibility to automatically forward x11 and so i dont need to export my DISPLAY, thats not a problem i can set it every time i connect to the server.
but if i export my DISPLAY, it wont start the application it always says:
Error: Can't open display: xxx.xx.xx.xx
i really liked the way putty worked and want to user cygwin.
i tried Cygwin/X but there always opens another terminal which i dont really like. i like to open my application from my existing standart cygwin terminal where i also connect to the server
is there any way doing this?!
i startet the xserver with the following command and after that i could start the programms automatically on my remote ssh server and it was forwarded automatically to my xserver
startxwin -- -listen tcp &
after this i even didnt have to set the DISPLAY
I have XQuartz 2.7.9 installed on OS X 10.11.5 and I'm able to successfully ssh with X11 forwarding to Linux machines. At first, I can open X11 windows without a problem. However, after about 20-30 minutes I cannot open any additional X11 windows. The X11 windows I already have open are fine.
With one Linux machine I get the error: "Fatal IO error: client killed". And on another Linux machine I get the error: "Cannot connect to X server".
I've tried messing with the value of ConnectTimeout in /etc/ssh/ssh_config, thinking that this might help, but it didn't. As of now, what I'm doing is exiting the current ssh session and then re-sshing. This gets real annoying, real quick.
ForwardX11Timeout = 500h
in /etc/ssh/ssh_config