sj26 Posted March 9, 2006 Report Share Posted March 9, 2006 I just upgraded to 1.5 and was very impressed... until I noticed it wasn't doing anything. Instead I get an error message in the Tracker Status field:An attempt was made to access a socket in a way forbidden by its access permissions.Both tracker and DHT aren't working so I'm not getting any sources so I'm totally boned at the moment. Bummer, huh?This is true for all three torrents I had running which defintly have no problems with their trackers.WinXP SP2, NAT'd through router(s) (ports confirmed open).P4 2.4GHz, 1GB RAM, Gigabyte m/b with onboard Intel-based NICOnly Windows Firewall/Avast Antivirus, all turned OFF during trials.Steps I've tried:- Turned off firewall/av.- Turned off protocol encryption.- Deleted all .dat and profile files.- Re-downloaded uTorrent in case of corruption.- Regressed to µTorrent 1.4.2 Build 435 Beta, same problem.- Regressed to µTorrent 1.4, problem disappeared.Anything else I should try before submitting this to the Found Bugs forum? Problem is I don't have much info to submit with it.Looks to me like it's a core library error... although I'm not sure how uTorrent handles it's connections. Link to comment Share on other sites More sharing options...
Firon Posted March 9, 2006 Report Share Posted March 9, 2006 use process explorer and see what might possibly be hooked into the µtorrent? check the threads tab. (that's all I can think of, ludde has no idea what could be your problem) Link to comment Share on other sites More sharing options...
sj26 Posted March 17, 2006 Author Report Share Posted March 17, 2006 OK, I figured it out.uTorrent 1.5 appears to have some fundamental conflict with Windows OneCare. I was using the Beta and, even when completely disabled, it seems to have been blocking uTorrent. Uninstalling it completely solves the problem. I made no other change between it working and not working. I didn't even have to do the prompted reset, or even restart uTorrent - it just started working.The MOST interesting part is that it only changed between 1.4 and 1.5. Could this be something to do with the encryption libraries ludde is using? I'm not entirely familiar with the MS Cryptographic Services, but I get the feeling that OneCare may be stingy with permissions re: Cryptographic Services + Sockets, depending of course on how he's doing things. Or it could be that OneCare adds it's own layer of "protection" on top of Windows Firewall. :-SIf that error string doesn't look familiar then maybe it's OneCare's.There's probably a hack out there already if you're willing to look, no doubt someone's encounteredt similar problems. It might also be worth submitting a bug to MS, if you can be bothered. I can't, and I don't feel it's my place to, anyway.So a heads up: If a user's having problems and is using Windows OneCare, get them to uninstall it.Merged double post(s):Sorry about the mis-report, by the way: I had been using Avast until I recently decided to trial OneCare and I wasn't at home when I wrote the original post. Link to comment Share on other sites More sharing options...
Firon Posted March 18, 2006 Report Share Posted March 18, 2006 OneCare's blocking µT? Funny. And no, we're not using the cryptographic services. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.