The Information Worker

March 19, 2009

Working SharePoint over Hamachi

Filed under: SharePoint Technology,Sharing Minds — adamclark @ 2:31 pm

Ok, this is a little different to most remote access requirements for MOSS but is a kewl little trick to know if you ever need a quick access method for Internal resources. The Requirement Recently I rebuilt my entire environment to fall in line with the policies lined out by my company Sharing Minds. Being a young company and still finding our feet in the world we need an Intranet to store and share our information and build our IP base. So being SharePoint guys we have of course deployed SharePoint as our Intranet.

The construction of the Intranet is ongoing and takes a back seat to the development of client items, but most important is the ability for the Intranet to be accessible to our resources out on site. Add to this that when we’re in the office we want to access the Intranet over the URL http://intranet and when we’re out of the office we want to access the Intranet over the URL https://Extranet (for example). The Solution With the rebuild of the environment, I have yet to finish configuring the remote access and SSL capabilities for everyone to access the Intranet resources stored securely on our network. SO how is it possible to allow access to the Intranet without SSL and a fully configured remote access policy. The answer is fairly simple, Hamachi and Alternative Access Mappings.

Hamachi is a client to client VPN tool available from , is free and secure. I have used hamachi for various tasks over the years from sharing files to playing games and it has always worked well.

Alternative Access Mappings (AAM) is a way that SharePoint can provide content from a single web site on different URL’s.

To describe the process I used, here are the steps:

1. Create the base SharePoint Site Collection (i.e. http://Intranet)

2. Define a static IP address for the Site Collection and apply that IP Address with a Host Header in IIS.

3. Ensure that a DNS entry has been created for the URL with the IP addressed assigned.

At this point if set-up correctly you will be able to access your site collection via the URL specified.

4. Set-up Hamachi on your SharePoint Server, hamaci will supply the server with an IP address for the VPN connection, you will need to note this IP address.

5. Create a AAM that points to the new URL (i.e. http://Extranet)

6. Assign the Hamachi IP address and DNS name as a new host header in IIS..

7. Create a DNS Entry that points the Hamachi IP address to the DNS name.

From a server perspective your SharePoint site will accept connections from the hamachi (VPN) address to the external DNS name provided. If your remote machines don’t have the correct cached credentials it is possible that you may need to a Hosts file entry that maps the DNS name to the hamachi IP address on the client machine, then it will work. This has turned out to be a quick secure way to get our organisation up and running with a minimum of fuss while we get a full remote environment up and running.


1 Comment »

  1. Adam! Awesome, quick and to the point directions. I went ahead and added the entry in the client machine’s hosts file just in case. Worked on the first try! Thanks!

    Comment by Josh — July 26, 2015 @ 5:36 pm | Reply

RSS feed for comments on this post. TrackBack URI

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s

Blog at

%d bloggers like this: