The problem can be related to address changes of Windows DLLs after a Windows update operation. That behaviour may create collisions for more static Cygwin DLLs, especially in a 32-bit environment. We suggest to reboot the system as a first measure. You may need to install Copssh again by using our recipe which allows to keep an existing configuration intact. Consider to install the 64-bit version (available only in the product edition) if the problem still persists.

Activating users/groups can be done in multiple ways:

• Using AllowUsers/AllowGroups directives globally - requires that user does have a Windows profile directory

• Create a match block for a specific user/group (you can use directory isolation to specify a specific directory instead of user profile directory)

Copying public key can be done via Tools → Copy public key. It uses the tool ssh-copy-id. You can use localhost to contact the copssh server.

In some situations, it may be necessary to make a clean install to make an upgrade work. You can do it by following steps below:

• Backup your host keys in etc directory (etc/ssh_host*)
• Uninstall the existing version of Copssh
• Remove remnants of the installation directory except home directories if they exist
• Make sure that the service account and the sshd account are removed if they exist
• Install new Copssh
• Restore host keys back to etc directory
• Start Copssh Control Panel and verify that the service is running
• Activate your users again and specify their existing home directories as the home directory during the activation

Copssh 8 syslog daemon writes log messages to /var/log/messages as default. You may need to introduce a log rotation scheme to keep growth of that file under control.

You can use the recipe below to use our free tool logwot8 for that purpose.

• Install logwot8 to a separate directory
• Edit the configuration file logwot8.conf according to your requirements. The example below will rotate the log file weekly by keeping last 12 weeks of log activity in compressed files. See documentation for more options.

# Remember cygwin path conventions: 'c:\work' becomes '/cygdrive/c/work'
compress
create

"/cygdrive/c/copssh_x64/var/log/messages {
    rotate 12
    weekly
}

• Create a Windows scheduled task running the batch file logwot8.cmd weekly.

Sometimes it may be necessary to see directly how the openssh daemon reacts to startup or connection requests, to be able to locate daemon-related problems.

• Stop OpenSSH SSHD (system name: OpenSSHServer) service
• Right click Start a Unix Bash Shell from Copssh start menu (assuming that you have admin privileges)
• Enter the following command from the bash prompt:
  /bin/sshd -p <listening port> -D -d -e

This will start openssh daemon in standalone debug mode and messages will be displayed on the screen. You may specify up to three -d for increased output verbosity.

• Try to initiate a putty session and watch messages at the server side.

• Start a bash shell, locally or remotely
• Change to the user's home directory if it is not already done
• Link a directory or network share to a local name by using ln command

Examples:

ln -s "/cygdrive/d/pub/" "pub"

creates a link from D:\pub to pub in the user's home directory.

ln -s "//myserver/netdata" "netdata"

creates a link from \\myserver\netdata to netdata in the user's home directory.

Now, the user can use pub and netdata to access D:\pub and/or \\myserver\netdata respectively.

Some recommendations (not all of them can be applicable in your case, no sorting by importance):

I am fond of fancy and short names :-)

Cygwin + OPENSSH is a qualified guess !!