As I have been setting up and fiddling around with my development environment, I had quite a few learning in the due course. Firs thing I wanted to do is to access my home server from office (Yes, behind firewall, proxy, etc etc). To cut long story short, here are the steps taken:
1. Make a note of the ports on which the programs are running that are to be accessed remotely.
2. I got a DynDNS account already and hence got a public DNS name of my server.
3. Change the setting in the home modem router to forward the incoming TCP/UDP port request to this particular machine on the relevant program's ports. For instance:
Rule1: Forward TCP xxxx to Machine abc on TCP port yyyy.
4. Adjust the OS firewall running on the server machine to accept the connections on the port yyyy.
Then the real fun starts. After making all these configuration, I was able to access the programs using my public DNS name. However, I could not connect to the machine from behind my office firewall. Apparently the only outbound ports open from the proxy are: 80 and 443.
To get around this:
1. Run SSH on your machine on a particular port (May be 22 or may be 3456 does not matter).
2. Configure modem router to forward the request coming on to port 80 or 443 to the port configured in step 1.
3. Start an SSH tunnel from the office pointing to the machine on port 80 or 443. Two ways to start it:
3.1 - Dynamic port configuration that will enable to access the any ports on the remote server outside the proxy. Any program can be accessed by RemoteServer:
3.2 - Local to Remote port forwarding - Such as accept the request on localhost at port xx that will end up in the remote server on port yy. So any program can be accessed by localhost:xx.
4. Once you are able to start the above session, you are able to access your favorite programs over the internet.
1. Make a note of the ports on which the programs are running that are to be accessed remotely.
2. I got a DynDNS account already and hence got a public DNS name of my server.
3. Change the setting in the home modem router to forward the incoming TCP/UDP port request to this particular machine on the relevant program's ports. For instance:
Rule1: Forward TCP xxxx to Machine abc on TCP port yyyy.
4. Adjust the OS firewall running on the server machine to accept the connections on the port yyyy.
Then the real fun starts. After making all these configuration, I was able to access the programs using my public DNS name. However, I could not connect to the machine from behind my office firewall. Apparently the only outbound ports open from the proxy are: 80 and 443.
To get around this:
1. Run SSH on your machine on a particular port (May be 22 or may be 3456 does not matter).
2. Configure modem router to forward the request coming on to port 80 or 443 to the port configured in step 1.
3. Start an SSH tunnel from the office pointing to the machine on port 80 or 443. Two ways to start it:
3.1 - Dynamic port configuration that will enable to access the any ports on the remote server outside the proxy. Any program can be accessed by RemoteServer:
3.2 - Local to Remote port forwarding - Such as accept the request on localhost at port xx that will end up in the remote server on port yy. So any program can be accessed by localhost:xx.
4. Once you are able to start the above session, you are able to access your favorite programs over the internet.
