Opened 4 years ago

Closed 2 years ago

Last modified 19 months ago

#1812 closed defect (fixed)

TOR not working in Windows 7

Reported by: slah04 Owned by: erinn
Priority: normal Milestone: Tor: 0.2.3.x-final
Component: Tor Version:
Keywords: Cc: edmanm@…
Actual Points: Parent ID:
Points:

Description

I am using Windows 7 32-bit OS with Windows Firewall. I downloaded the TOR Bundle (for Firefox) but when I am starting the Start TOR Browser.. the initial connection is being tried.. but after some time it is terminating with a message "Vidalia was unable to connect to TOR (Connection refused by Peer)"

The message log shows:

Aug 08 11:44:56.410 [Notice] Tor v0.2.1.26. This is experimental software. Do not rely on it for strong anonymity. (Running on Very recent version of Windows [major=6,minor=1] [workstation] {personal} {terminal services, single user})
Aug 08 11:45:17.380 [Warning] Warning from libevent: evsignal_init: socketpair: No error
Aug 08 11:45:17.380 [Notice] Initialized libevent version 1.4.12-stable using method win32. Good.
Aug 08 11:45:17.380 [Notice] Opening Socks listener on 127.0.0.1:9050
Aug 08 11:45:17.380 [Notice] Opening Control listener on 127.0.0.1:9051
Aug 08 11:45:17.380 [Notice] Parsing GEOIP file.
Aug 08 11:45:20.000 [Notice] OpenSSL OpenSSL 0.9.8k 25 Mar 2009 [9080bf] looks like it's older than 0.9.8l, but some vendors have backported 0.9.8l's renegotiation code to earlier versions, and some have backported the code from 0.9.8m or 0.9.8n. I'll set both SSL3_FLAGS and SSL_OP just to be safe.
Aug 08 11:45:20.328 [Notice] We now have enough directory information to build circuits.
Aug 08 11:45:20.328 [Notice] Bootstrapped 80%: Connecting to the Tor network.
Aug 08 11:45:20.546 [Notice] Bootstrapped 85%: Finishing handshake with first hop.
Aug 08 11:45:22.184 [Notice] Bootstrapped 90%: Establishing a Tor circuit.
Aug 08 11:45:24.041 [Notice] Tor has successfully opened a circuit. Looks like client functionality is working.
Aug 08 11:45:24.041 [Notice] Bootstrapped 100%: Done.

.. as such on error messages are evident in the message log. I have also included the tor.exe & tor-resolve.exe in my firewall allowable programs.

Pls Help

slah

Child Tickets

Change History (9)

comment:1 Changed 4 years ago by edmanm

  • Cc edmanm@… added

This isn't a Tor bug. It might be a Vidalia bug, but most likely it just means something (perhaps your Windows firewall) is preventing Vidalia from connecting to Tor's control port. Vidalia typically needs to be able to connect to port 9051 on localhost (127.0.0.1) in order to talk to Tor.

comment:2 Changed 4 years ago by slah04

.. I have check the open/listening ports by currports. Nowhere is it evident that port 9051 is blocked by any other application.

Pls advise how to remove this bug

comment:3 Changed 4 years ago by phobos

Are you firewalling localhost/127.0.0.1? This error Aug 08 11:45:17.380 [Warning] Warning from libevent: evsignal_init: socketpair: No error implies you are.

comment:4 Changed 3 years ago by nickm

  • Component changed from Tor bundles/installation to Tor Client

comment:5 Changed 3 years ago by nickm

  • Milestone set to Tor: 0.2.3.x-final

comment:6 Changed 3 years ago by nickm

Related to #792 .

comment:7 Changed 2 years ago by arma

Time has moved on here. I imagine the user would hit #3464 if he/she upgrades. And once that's fixed, we anticipate no problems for the user.

Should we close this bug and suggest that people using old Tor bundles upgrade?

Or Nick, did you have something in mind here that you still wanted to address?

comment:8 Changed 2 years ago by nickm

  • Resolution set to fixed
  • Status changed from new to closed

I think that's the best idea; the next set of bundles should address the issues here. (If not, please reopen.)

comment:9 Changed 19 months ago by nickm

  • Component changed from Tor Client to Tor
Note: See TracTickets for help on using tickets.