<p>The easiest way to make this work would be to install cygwin on your windows machine, specifically ssh client package.</p>

<p>Then from a cygwin shell, run ssh -D 8080 user@linuxHost.</p>

<p>Now you can point the qt client to localhost:8080 as the socks proxy. </p>

CC BY-SA 3.0
2015-04-10T14:05:10.003Z
It seems like it works if one changes socks protocol to 4 in Bitcoin-QT.
dma_k
CC BY-SA 3.0
2012-05-15T05:30:42.087Z
is this different from setting up a tunnel using putty like i mentioned above ?
thedrs
CC BY-SA 3.0
2012-05-14T00:35:43.130Z
2012-05-14T00:35:43.130Z
Tuxavant
<p>You can use Putty to create a socks proxy too:</p>

<p><a href="http://www.virtualroadside.com/blog/index.php/2007/04/12/dynamic-socks-proxy-using-putty/" rel="nofollow">http://www.virtualroadside.com/blog/index.php/2007/04/12/dynamic-socks-proxy-using-putty/</a></p>

CC BY-SA 3.0
2013-04-10T00:29:40.863Z
2013-04-10T00:29:40.863Z
Andrew Burns
<p>I am on Windows machine on a network that is closed for all incoming packets and outgoing packets only work for port 80.</p>

<p>In the network I have access to a Linux via SSH that is open for in and out access.</p>

<p>I want to run the wallet client Bitcoin-QT on the restricted Windows machine, I setup a tunnel using D9050 to the open Linux and then I told Bitcoin-QT that there is socks proxy on localhost port 9050.</p>

<p>The client runs and starts to show connections (which is doesn't show without the tunnel) but it doesn't start downloading the block chain :(</p>

<p>Help ?</p>

CC BY-SA 3.0
2012-05-13T15:17:35.917Z
i think i should have some process listening on 8332 on the linux so that when other nodes try to contact me they will reach something ... but i am not sure
thedrs
<client>
How can I run Bitcoin-QT client behind a restrictive firewall using a putty tunnel?
thedrs
# How can I run Bitcoin-QT client behind a restrictive firewall using a putty tunnel?

(Asked by: username_0 on 2012-05-13)

I am on Windows machine on a network that is closed for all incoming packets and outgoing packets only work for port 80.

In the network I have access to a Linux via SSH that is open for in and out access.

I want to run the wallet client Bitcoin-QT on the restricted Windows machine, I setup a tunnel using D9050 to the open Linux and then I told Bitcoin-QT that there is socks proxy on localhost port 9050.

The client runs and starts to show connections (which is doesn't show without the tunnel) but it doesn't start downloading the block chain :(

Help ?

**Tags:** client

> **Comments:**
> **username_0**: i think i should have some process listening on 8332 on the linux so that when other nodes try to contact me they will reach something ... but i am not sure  

---

## 2 answers

### Answer by username_1 on 2012-05-14. Score: 2

The easiest way to make this work would be to install cygwin on your windows machine, specifically ssh client package.

Then from a cygwin shell, run ssh -D 8080 user@linuxHost.

Now you can point the qt client to localhost:8080 as the socks proxy.

> **Comments:**
> **username_0**: is this different from setting up a tunnel using putty like i mentioned above ?  
> **username_2**: It seems like it works if one changes socks protocol to 4 in Bitcoin-QT.  

---

### Answer by username_3 on 2013-04-10. Score: 2

You can use Putty to create a socks proxy too:

<http://www.virtualroadside.com/blog/index.php/2007/04/12/dynamic-socks-proxy-using-putty/>


---

