Hello all, the issue is as follows"

I'm trying to conncet via ssh my Ubuntu 10.04 netbook to my desktop a windows 7 machine. I've tried COPSSH/Cygwin as the server on the win7 machine, and on the netbook, bitvise + good old fashioned command line ssh

I believe this (and my far more comp-learned friend agrees) is because we've several machines running through a single internet source
that is to say my network runs as:

Target comp--------------------Switcher---Gateway--------------Internet
unique ipv4,6, mac#...............|.............|unique ipv4
............................................|.............|unique mac address
............................................|
Second comp ______________|
unique ipv4,6, mac#

or so sayeth the Windows network map anyways

the point of this being, how can i connect to target comp?
(the port is open, it allows COPSSH and listens at the correct port)
i've been using

http://lifehacker.com/#!205090/geek-...ome-ssh-server

and

http://lifehacker.com/#!237227/geek-...sh-socks-proxy

but with cygwin i get a 1069 error that, many have reported on the web but, few answers were offered for.
Much thanks for reading, any and all notes or assistance is graciously accepted!

This is not a complete answer to your question.

I just wanted to add that the problem is not caused by the 'single internet source', since you are only working within the local network. The gateway would only become a complication if you were trying to ssh in from the outside, because the gateway would not know which machine to route to (though you can explicitly forward requests to a specific machine using port forwarding). Since the server and client are in the same IP address space, it is not a network problem.

It is more likely that the problem is to do with the account settings for the sshd_server on the Windows machine that is preventing the server from starting.

hmm, point taken, really the only thing ive found to change circumvent the 1069 error was the command

passwd sshd_server

to which i got a reply stating such a account didnt exist :/
COPSSH say's its running, but, it has very little to tweak with or get any sort of information from without upgrading their service.

are you aware of any reliable windows virtual servers? or am i just n00bing it up??

(thanks for the reply by the by)

The sshd account in copssh is probably called something like SvcCOPSSH these days (and it should have created a reasonable password already when it was installed).

When you say it is running, how do you know that?

Have you added an activated user?

Where are you seeing the 1069 error?

What error do you see on the linux side?

Ideally what would have happened is:
1. install copssh on the server machine 'foo'.
2. activate user 'bar'
3. start the sshd server from the copssh control panel (if it isn't already going)
4. ssh in using 'ssh bar@foo'

well, ik its running only so far as the large hard to miss button on COPSSH control panel is green and says it is :/

i see the 1069 in cygwin terminal when i type the command


net start sshd

as previously stated, i tried to reset the password for sshd_sever, but, it was not extant.

in linux it states:

ssh: connect to host *********** port **** connection refused

Some of this might be obvious to you, but bear with me. I can't give you exact instructions for Win7 (I have just installed copssh on an old Win2000 box to test this out).

Have a look under the user list (which used to be accessible from the control panel on Windows). If you do not see the SvcCOPSSH service account, you may need to go to an advanced configuration or under the users in the Microsoft computer management app.

Look at the SvcCOPSSH service account and check that it is a member of the Administrators group (perhaps under a properties tab). If it isn't, add it. You can also change the SvcCOPSSH account password here if you desire.

There is another dummy account called sshd, which as far as I know doesn't need to be enabled (it is used for the openssh privilege separation).

Now under the Services app of the computer management, there is a service called Openssh SSHD. You can set the login password here (perhaps under a properties tab), so that the ssh service can log in to its account (which obviously has to match the SvcCOPSSH account password). You can also restart the service here (perhaps by right clicking).

The error you are getting is indicating that the service cannot log in to its account, which means that it will not even be able to listen on the port, let alone start the ssh session.

I don't have the experience to recommend you any other ssh servers for Windows. The copssh one is just openssh bundled up with cygwin, so apart from setting up the Windows side configuration, it is a mature combination of software (and simpler than having to manually install openssh into cygwin yourself). Openssh is renowned for the thought put into its security.