![]() |
|
SSH problem... - Printable Version +- Hack Forums (https://hackforums.net) +-- Forum: Tech (https://hackforums.net/forumdisplay.php?fid=444) +--- Forum: Computing (https://hackforums.net/forumdisplay.php?fid=88) +---- Forum: Linux (https://hackforums.net/forumdisplay.php?fid=85) +---- Thread: SSH problem... (/showthread.php?tid=5481826) Pages: Pages
1
2
|
SSH problem... - severos - Dec 1, 2016 I have Linux Subsystem running in windows. My config file is here: PHP Code However when I try to connect using Code ssh development@localhost -p 2234Code ssh: connect to host localhost port 2234: Connection refusedIt was working well last night though, haven't changed anything since then. * - archangel.dmitry - Dec 1, 2016 If you trying to connect from one OS to other, you need to use host name or IP address. Localhost is applicable when client and server run on the same machine. * - severos - Dec 1, 2016 (Dec 1, 2016 11:11 PM)archangel.dmitry Wrote: If you trying to connect from one OS to other, you need to use host name or IP address. Localhost is applicable when client and server run on the same machine. Linux subsystem runs inside windows on the same IP, on the same machine, under the same OS (it's subsystem feature, not VM) * - archangel.dmitry - Dec 1, 2016 What is Linux subsystem in Windows? * - severos - Dec 2, 2016 (Dec 1, 2016 11:31 PM)archangel.dmitry Wrote: What is Linux subsystem in Windows? A feature in Windows 10 that was released on Anniversary update, it provides a Linux environment for developers, it can also access Windows system, you can think of it as having dual system at same time, ofc it's not real dual system and still have limitations. * - 8lue7ornado - Dec 2, 2016 Did you bridge the connection? * - archangel.dmitry - Dec 2, 2016 (Dec 2, 2016 12:07 AM)severos Wrote: A feature in Windows 10 that was released on Anniversary update, it provides a Linux environment for developers, it can also access Windows system, you can think of it as having dual system at same time, ofc it's not real dual system and still have limitations. No offense, but your question has nothing to do with Linux. You should look for help in Windows 10 section. Check the link below, it could be helpful. http://superuser.com/questions/1111591/how-can-i-ssh-into-bash-on-ubuntu-on-windows-10 * - severos - Dec 2, 2016 (Dec 2, 2016 12:13 AM)8lue7ornado Wrote: Did you bridge the connection?Not sure I understand you, why would I need to bridge the connection? I have a firewall rule to allow inbound connections, but never read about bridging the connection, there's no VM here, the subsystem is running directly on top of windows. (Dec 2, 2016 12:15 AM)archangel.dmitry Wrote: No offense, but your question has nothing to do with Linux. You should look for help in Windows 10 section.I've already tried that, it's how I got it running for the last week, but out of blue it doesn't work today... My question is related to Linux more than Windows since I was asking about what could be causing the error in ssh, which I believe Linux users are more used to them than Windows users. What are the possibilities to refuse an ssh connection?? other than a wrong password/username/port ? * - archangel.dmitry - Dec 2, 2016 Did you check if sshd is listening on port? * - severos - Dec 2, 2016 (Dec 2, 2016 12:34 AM)archangel.dmitry Wrote: Did you check if sshd is listening on port? This seems to be the problem, sshd stops listening whenever I close the bash window and have to restart it... * - 8lue7ornado - Dec 2, 2016 (Dec 2, 2016 12:33 AM)severos Wrote: Not sure I understand you, why would I need to bridge the connection? I have a firewall rule to allow inbound connections, but never read about bridging the connection, there's no VM here, the subsystem is running directly on top of windows. Ops my bad, misunderstood that it was a vm! * - Freshnuts - Dec 2, 2016 (Dec 2, 2016 01:08 AM)severos Wrote: This seems to be the problem, sshd stops listening whenever I close the bash window and have to restart it... For this issue you're running it foreground and not as daemon service. commands "nohup", "&" will help you out. box@box#: nohup [program] & // This will run the program in the background allowing you to exit bash window without // exiting program. * - severos - Dec 2, 2016 (Dec 2, 2016 02:11 AM)Freshnuts Wrote: For this issue you're running it foreground and not as daemon service. I thought "sudo service ssh start" does start the sshd * - archangel.dmitry - Dec 2, 2016 (Dec 2, 2016 02:11 AM)Freshnuts Wrote: For this issue you're running it foreground and not as daemon service. He might be on to something. I wounder, if sshd does not fork out properly from bash. "&" using should help to resolve the issue as it was stated. * - severos - Dec 2, 2016 (Dec 2, 2016 06:46 AM)archangel.dmitry Wrote: He might be on to something. I wounder, if sshd does not fork out properly from bash. "&" using should help to resolve the issue as it was stated. Didn't help, this seems to be a problem in the implementation of Linux subsystem (Windows problem) daemons won't run as windows service, keeping a shell open keeps the service running and solves the problem though. Thanks all for the help :) |