Home Premium Access PC Products Contact
Online Meetings and Remote Support
Private Hosted Plans
Time needed to setup: 7 minutes.
If you already have a computer with public host name or IP address.

Requirements (Linux, Windows or a Virtual Machine)

1.0GHz CPU or More
256+ MB RAM
10 or 100mbps+ Network Card
You built application will need a public host name or an IP address of your server. e.g. or myserver.mycompany.com
For SSH public port 443 is recommended since its firewall friendly, as an alternate you can use any port, that is reachable by your users.

On Linux

CentOS, Ubuntu, Red Hat (Most all Linux versions have default SSH server)

On Windows

Download and Install one of the following SSH Server for Windows.
1) http://www.freesshd.com/ (It is Free)
2) or http://www.bitvise.com/winsshd (WinSSHD 5 or above recommend)
3) Any other SSH Windows server

Setting up FreeSSHd server on Windows (VM or Server)

(Linux is recommended for future broader support)

1) Install freeSSHd from http://www.freesshd.com/
2) Open freeSSHd Control Panel and allow Port Forwarding as below.

3) Open freeSSHd Control Panel and Add SSH user with tunnel permissions.

4) Select port 443 if possible or default port 22.

Click OK to save. Restart freeSSHd.
If for any reason you cannot connect to your SSH server, please restart your PC and then restart freeSSHd.

Now test your Server.

Setting up WinSSHd server

(Linux is recommended for future broader support)

Open the WinSSHd Control Panel > Edit Advanced Settings

Windows or Virtual Account > Add > Apply the following settings to the new user.

You may disable:
Permit terminal shell. This prevents your users from accessing the command interpreter.
Permit exec requests. This prevents your users from executing arbitrary programs via SSH.

Options that are required:
Permit C2S port forwarding.
Permit S2C port forwarding.

Optional: If you are already running a program on port 443, you may bind to a different port in WinSSHd.
Open the WinSSHd Control Panel > Edit Advanced Settings

Click Binding and UPnP and change the Listen Interface to your IP Address

Click OK to save. Restart WinSSHd.

Now test your Server.
Disable any programs listening on Port 443 or use default port 22.
    Typically apache web server will be listening on this port.
    vi /etc/httpd/conf.d/ssl.conf
    Comment out line #Listen 443
    Restart apache server (/etc/init.d/httpd restart)

Change ssh server listener port to 443
    vi /etc/ssh/sshd_config
    Edit this line in the file ("Port 22" to "Port 443")
    Restart ssh server (/etc/init.d/sshd restart)

Create a new user and change password.(This is the username and password that you will provide us to be embedded in the application)
    /usr/sbin/useradd someuser -s /sbin/nologin
    /usr/bin/passwd showmypcuser
    Enter the new password, when prompted.

  Some SSH server installations are configured to refuse the authentication type "password". Often, they only accept "publickey" and "keyboard-interactive". Enable password authentication. E.g., edit /etc/sshd/sshd_config and change the value of "PasswordAuthentication" to "yes", then send a HUP signal to the daemon so that it re-reads its configuration or Restart server or SSH.

Important last Step. Test your SSH server.

Once your server is setup you may test using a Windows SSH client. Get Putty SSH Client
Make sure you are able to connect from a remote location outside your network using the SSH username and password you are providing us.

Now you may request your application.

Call Us: (888) 930 1116