Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I am trying to access a network in our office to allow access to a local server, this server is able to send out but is unable to be reached outside of the office network.

Would it be possible to bridge a vpn network or something similar? If so, how would it be achieved?

share|improve this question

closed as too broad by devicenull, MadHatter, Stephane, Ward, Jenny D Jul 17 '13 at 15:03

There are either too many possible answers, or good answers would be too long for this format. Please add details to narrow the answer set or to isolate an issue that can be answered in a few paragraphs.If this question can be reworded to fit the rules in the help center, please edit the question.

Have you considered simple ssh port forwards? – Robbie Mckennie Jul 16 '13 at 11:58
We do not have access to the layer above our router which is the final point before WAN access. It is rented office space so we are on a shared network (worth mentioning that this isn't against the network policy). – JamieB Jul 16 '13 at 12:00
I'm afraid i don't know quite what you're trying to tell me. Do you mean you can't create a port forward in the router? – Robbie Mckennie Jul 16 '13 at 12:01
You could try something like Hamachi? – Nathan C Jul 16 '13 at 12:03
That looks like overkill to me – Robbie Mckennie Jul 16 '13 at 12:03
up vote 0 down vote accepted

Using plink, you could use something like this:

plink.exe <options> -R *:8888:localhost:8888 -R *:3389:localhost:3389 username@host

Where <options> are things like compression, priv keys, and backgrounding the process. If you just run plink.exe on it's own you can see a list of these options.

share|improve this answer

Not the answer you're looking for? Browse other questions tagged or ask your own question.