Connect to SQL Server behind NAT from remote machine The scenario is that this is a SQL Server behind a corporate firewall with your standard setup to allow only minimal outbound traffic and zero inbound.  However, port 80/443 are open, per the usual allowance.

Has anyone tried, or is it possible to


Connect to a remote machine port 80, say using Telnet.
On the local machine, note the bound address and port [1], e.g. netstat
Disconnect from telnet.  Start port forwarder and listen on [1], mapped to SQL Server TCP/IP listener
On remote machine, connect to SQL Server on [1]


What do you think?  I just need to get some testing done and I don't want to move my huge database outside for this one-off.  I am familiar with and have used UDP hole punching for NAT traversal, mainly for push to mobile phones, but am interested to know if this works with TCP as well.

References:


TCP Hole Punching
UDP Hole Punching
TCP Hole Punching #2


I am open to other suggestions.
I doubt that it's easy to do hole punching with TCP or switch the process connected to a port.

Try this for a reverse proxy through the firewall:
http://www.dest-unreach.org/socat/doc/socat-gender.txt

This solutions relies on socat, a swiss-army-knife like network tool which can connect almost any two endpoints and is bidirectional, unlike netcat or the |-pipes in command processors. It should be available for Windows, too.

You can either use socat easily to forward a TCP connection, or in this case: Reverse the "gender" of it: You'll have two socats running, one on each side of the firewall. One continuously connects to the outside. On the outside, socat will wait for a connection from someone else. Only if he connects, the outside socat will accept a connection from the inside socat. Once the inside socat connects to the outside socat, it will connect to the SQL-server. Voila, you can connect from outside to the SQL-server inside, and from the point of the firewall and from the point of TCP the connection looked like it was actually from inside to outside.

To copy from the link:


  1) Start the double client on the inside server
  // every 10 seconds, it tries to establish a connection to the outside host.
  // whenever it succeeds, it forks a sub process that connect to the internal
  // service and starts to transfer data


$ socat -d -d -d -t5 tcp:outside-host:80,forever,intervall=10,fork tcp:localhost:80



  2) Start double server on the outside client
  // wait for a connection from a local client. whenever it accepted it, forks
  // a subprocess that tries to bind to the socket where the inside double 
  // client tries to connect (might need to wait for a previous process to 
  // release the port) 


$ socat -d -d -d tcp-l:80,reuseaddr,bind=127.0.0.1,fork tcp-l:80,bind=outside-host,reuseaddr,retry=10