Secure Network Mapping

Manual

Table of Contents
About
Map local drive to remote Windows network share (or Samba server) on the
internet. The connection is secured by using an encrypted SSH connection as
transportation. Below is a screenshot to give a clue.

Screenshot
Copyright
This software is provided 'as-is', without any express or implied warranty.
In no event will the authors be held liable for any damages arising from
the use of this software.
The origin of this software must not be misrepresented; you must not claim
that you wrote the original software. This notice may not be removed or
altered from any source distribution.
Secure Network Mapping is copyrighted by Stefan Sedin and published under
the GNU GPL license. Read the LICENSE file for more information.
Prerequirements
The "File and Printing Sharing" service must be uninstalled before this
this software is able to successfully make an connection.
Go to the following location to make sure the service is not enabled: 
"Start / Settings / Control Panel / Network Connections"
Right-click the icon named "Local Area Connection" and select "Properties".
Select the "File and Printing Sharing" service, if available, from the
property dialog and click "Uninstall".
Requirements
Client: This software running on Microsoft Windows 98/ME/NT/XP/2000/2003
Server: An SSH server with a Windows network share. Samba is used on
systems running Unix flavors for this functionality.
Download
Get sourcecode and binaries from here. For project information go here. 
Installation
Run the secmap.exe setup file by double-clicking on it. The installer
should be pretty straight-forward, just press the next button if you're
satisfied with the defaults.
Usage
When the application is started an icon is shown in the trayicon located to
the right of the toolbar. Right-clicking the trayicon will open the
application menu.
Either select "Options" or double-click the application trayicon to configure
the connection being made. The parameter inputfields are:
- Drive        : Drive letter that will be used for mapping the connection.
- Folder (UNC) : Specify the complete UNC path, this includes the SSH server
                 and sharename. For example:
                 If you shared a directory called "Temp" on an SSH server
                 that's located at TCP/IP address 10.11.12.13 then the
                 complete Folder (UNC) would be "\\10.11.12.13\Temp".
                 The address could also be a domain like "test.dynu.com". In
                 this case the UNC path would become "\\test.dynu.com\Temp"
                 instead.
                 If the SSH daemon is running on a non-default port it can
                 be specified adding :port to the servername, for example
                 \\10.11.12.13:444\Temp will use port 444 instead of the
                 default on port 22.
- Username     : Your login or username on the SSH server.
- Password     : Your password on the SSH server.
- Autostart    : This application will start automatically with Windows.
- Automount    : The connection will be restored as soon as the application
                 is started.
When the above configuration is done and saved you can initialize the
connection by right-clicking the trayicon and selecting "Mapping". The
application will now try to map your selected drive letter to the remote
network share. The trayicon will tell you the connection status by switching
the stoplight to either red, yellow or green.
Right-clicking the trayicon and selecting "Exit" will remove the mapped
network connection and terminate the application until started again.
Future
There are always room for enhancements to any software, this piece is no
exception ofcourse. The following are planned when time allows, but you are
free to contact me if you have more suggestions.

- Retry getting SSH connection automatically upon failure.
- Integrate Plink for more accurate error messages when doing connections.
- Be able to map more than one drive. Should be possible to map other types
  aswell, for instance LPT1:
- Make workaround for the prerequirement dependancy if possible. All ideas
  are welcome for a solution to this problem.
Acknowledgement
This software uses other opensource projects for enhanced functionality.

- Connects using Plink written by Simon Tatham.
- Accessing the registry using CRegistry by Carlos Antollini.
- Shows a trayicon using SS_TrayIcon by Steve Schaneville.
- Packaged using NSIS by courtesy of Nullsoft.
- Hosted at the SourceForge opensource.
Contact
I can be reached by email if filing bug reports, suggestions, comments or if
you want to help me out with this project.

Stefan Sedin (sedda@home.se)