Setting up Tor with Freecap and Proxomitron

[laighleas]

Ralph Wrote:chrome_waves wrote :

Quote:
ralph whats your configuration? what works for one should work for another

I am on Win98 se with all the latest updates using Sidke's latest config . Motorola modem>Netgear router > IBM pc . I use IE 6 or Maxthon to browse . No software firewall . F-Prot is my viral scanner . Tor works with Privoxy although very slow . I followed Kye-U 's and your guidance verbatim and I can't get " Torified " . No activity in Tor with FreeCap . Thanks for your help .

I've got Proxomitron and Freecap working quite happily with Tor, using SOCKS 5, with IE6 as a browser, XP sp2, .NET, and Zonealarm, with broadband.

I know this probably sounds dim, but doublecheck the connection in IE6, namely that it's pointed at Proxomitron on 8080 and that the 'use a proxy' box is set. Then check the settings in Freecap are pointed at 9050 (Tor) and that it's set to resolve names remotely. If you're using TorCP doublecheck that it's connected - there's a disconnect option. If you're using TorCP you can also display the bandwidth graph - any activity here means that you're connected. If something is then getting your IP, it's using something scripts or SSL to do it.

As I said, I know doublechecking the connections sounds dim, but I had a similar problem the other day. Anything more complicated than a browser goes right over the wife's head (well, it's not that she can't know - she's just not interested in knowing) so I'm likely to find, after she's been surfing, that she's disconnected Proxomitron right back at the browser before she started. Which is exactly what she did a day or two ago - and of course the browser won't talk to the net via Tor in that case. :-(

OTOH, if you have two things trying to use the same port at once, you'll get nowhere equally fast.

Having doublechecked the connections, make certain that you haven't got the remote proxy set in Proxomitron - you need it off, because Freecap is handling that. You don't want Proxomitron thinking that it is using a remote proxy, otherwise you'll get nowhere - well, you may get a warning that Tor is not an HTTP proxy. OTOH, make sure that Proxomitron is actually running socksified - there's a setting in Freecap to run a program when Freecap starts. The chain won't work if Proxomitron isn't socksified.

That's the best I can think of for now. Just back to old-fashioned tracing things through from the start and tugging on leads. If that doesn't sort it, then the problem lies elsewhere.

Kevin