| Home | How It Works | Download | Docs | Users | FAQs | Volunteer | Developers | Research | People |

# Running the Tor client on MS Windows

Note that these are the installation instructions for running a Tor client on MS Windows (98, 98SE, NT4, 2000, XP, Server). If you want to relay traffic for others to help the network grow (please do), read the Configuring a server guide.

## Step One: Download and Install Tor

The install for MS Windows bundles Tor, TorCP (a Tor controller that lets you monitor and control Tor), and Privoxy (a filtering web proxy) into one package, with the three applications pre-configured to work together. The latest stable version provides Tor 0.1.0.15, TorCP 0.0.4, and Privoxy 3.0.3. Download it by clicking the link.

If you prefer the experimental (unstable) versions of Tor, you can try the experimental bundle that includes Tor 0.1.1.10-alpha. You need the experimental bundle if you want to run a Tor server and configure it via TorCP.

If the bundles don't work for you, you can download Tor by itself from the Win32 download directory, and then install and configure Privoxy on your own.

If you have previously installed Tor, TorCP, or Privoxy you can deselect whichever components you do not need to install in the dialog shown below.

After you have completed the installer, the components you selected will automatically be started for you.

## Step Two: Configure your applications to use Tor

After installing Tor and Privoxy, you need to configure your applications to use them. The first step is to set up web browsing.

If you're using Firefox (we recommend it), check out our Tor SwitchProxy howto to set up a plugin that makes it easy to switch between using Tor and using a direct connection.

Otherwise, you need to manually configure your browser to HTTP proxy at localhost port 8118. (That's where Privoxy listens.) In Mozilla, this is in Edit|Preferences|Advanced|Proxies. In Opera 7.5x it's Tools|Preferences|Network|Proxy servers. In IE, it's Tools|Internet Options|Connections|LAN Settings|Advanced. You should click the "use the same proxy server for all protocols" button; but see this note about Tor and ftp proxies. In IE, this looks something like:

Using Privoxy is necessary because browsers leak your DNS requests when they use a SOCKS proxy directly, which is bad for your anonymity. Privoxy also removes certain dangerous headers from your web requests, and blocks obnoxious ad sites like Doubleclick.

To Torify other applications that support HTTP proxies, just point them at Privoxy (that is, localhost port 8118). To use SOCKS directly (for instant messaging, Jabber, IRC, etc), you can point your application directly at Tor (localhost port 9050), but see this FAQ entry for why this may be dangerous. For applications that support neither SOCKS nor HTTP, take a look at SocksCap or FreeCap. (FreeCap is free software; SocksCap is proprietary.)

For information on how to Torify other applications, check out the Torify HOWTO.

## Step Three: Make sure it's working

Check to see that Privoxy and TorCP are running and that TorCP has successfully started Tor. Privoxy's icon is a green circle with a "P" in it, and TorCP uses a fat grey onion with a green checkmark in your system notification area, as shown below:

Next, you should try using your browser with Tor and make sure that your IP address is being anonymized. ipid.shat.net and showmyip.com are sites that show what IP address and country you appear to be coming from. Click on one of them and see what it says.

If you don't know your current public IP address, this may not be a very useful test. To learn your IP address, go to the Start menu, click Run and enter "`cmd`". At the command prompt, enter "`ipconfig /a`". If you are behind a NAT or firewall, though, you won't be able to learn your public IP address. In this case, you should 1) configure your browser to connect directly (that is, stop using Privoxy), 2) check your IP address with one of the sites above, 3) point your browser back to Privoxy, and 4) see whether your IP address has changed.

If you have a personal firewall that limits your computer's ability to connect to itself, be sure to allow connections from your local applications to local port 8118 and port 9050. If your firewall blocks outgoing connections, punch a hole so it can connect to at least TCP ports 80 and 443, and then see this FAQ entry.

If it's still not working, look at this FAQ entry for hints.

## Step Four: Configure it as a server

The Tor network relies on volunteers to donate bandwidth. The more people who run servers, the faster the Tor network will be. If you have at least 20 kilobytes/s each way, please help out Tor by configuring your Tor to be a server too. We have many features that make Tor servers easy and convenient, including rate limiting for bandwidth, exit policies so you can limit your exposure to abuse complaints, and support for dynamic IP addresses.

Having servers in many different places on the Internet is what makes Tor users secure. You may also get stronger anonymity yourself, since remote sites can't know whether connections originated at your computer or were relayed from others.

Read more at our Configuring a server guide.

If you have suggestions for improving this document, please post them on our bugtracker in the website category. Thanks!

Webmaster - $Id$