UpdateClemens Vasters released PortBridge at the PDC in November 2009, see
http://blogs.msdn.com/clemensv/archive/2009/11/18/port-bridge.aspx for more information. You should probably consider using that code instead of SocketShifter.
Project DescriptionThe .NET Service Bus provides a way of connecting two endpoints on the Internet using WCF. SocketShifter uses these features to automatically bridge arbitrary TCP endpoints, handling any intermediate firewall traversal.
SocketShifter consists of a server process and a client process. The client process listens on an arbitrary TCP socket which is then connected, via the service bus, to a TCP socket that is established on the server.
So, for instance, a SocketShifter client listening on port 1000 on your laptop can connect to a SocketShifter server running on your office machine, in turn connected to your department server via RDP on port 3389. By connecting your laptop's remote desktop client to localhost:1000 you can log into your server, despite any firewalls that might be in the way.
PrerequisitesDownload and install
The .NET Services SDK (Nov 2009
CTP)(http://go.microsoft.com/fwlink/?LinkID=129448)
You'll also need to sign up for an account:
Azure Services Platform
.NET Services.(http://www.microsoft.com/azure/netservices.mspx)
Download the Source Code and compile it yourself using Visual Studio 2008. See the README.TXT for more instructions.