TOR does not start

[Frank648]

Hi,
for some time and several versions I have a TOR-problem.
This is under WinXP SP3 and Win7 SP1 Ultimate.
Both OS are in separate independent partitions and don't know each other.
TOR was working fine some time back and stopped all the sudden.
I put back older images with TOR on it, and it won't work either.

Here are some info -

Vidalia was unable to authenticate to the Tor software. (Control socket is not connected.)
Please check your control port authentication settings.

Settings:
Use TCP-connection (ControlPort)
Address: 127.0.0.1 : 9051

Tor Configuration File: .\Data\Tor\torrc
Data Directory: .\Data\Tor

That all fits.
However, if I open _Edit current torrc_ it does not show the file.
Somewhere along the line the connection to this file is missing.

Strange is, it will not work on two different OS on the same computer,
each having a different Firewall and AntiVirus which were also disabled for testing.

I am out of ideas, also checked BIOS-settings.
TOR seems not to have a forum.
Anyone here with hints?

Frank

[lotuseclat79]

Are you using the latest Tor, and its associated browser bundles and the latest Vidalia? If not, you should update those packages for Windows. They change approximately each month with bug fixes and new features.

-- Tom

[Frank648]

The problem started with version 2.2.34-2 all the sudden without having made any changes to the system.
Tried all following packages up to the actual 2.2.35-7.1.
No way.
Hope, I explained the problem understandable in my first thread.
Meanwhile, I use TOR on a spare computer.
But heck, why won't it start on my main machine

Frank

(thanks to all who have read my entry)

[mirimir]

Why not just boot your spare machine with TAILS?

[Frank648]

So, I am back and have some good news

The problem not starting TOR was Ad Muncher

Settings:
Options > Filter Targets > Default Filter Targets
it showed +vidalia:*

Changing it to -vidalia:* in My Filter Targets fixed the problem.

TOR was working fine and stopped all the sudden.
I guess, some Ad Muncher Update must have done it
as I did not tamper with the settings.

In case someone else is running into this problem...

Frank