QauNuckShin Posted February 19, 2006 Report Share Posted February 19, 2006 Ok, so before 1.4 everything was fine.. Then, things started to freak out. Simply put, when µTorrent is running, I can barely surf. It's really weird. Right now, my halfopen setting is at max 8, and I've patched the SP2 limit to allow 100. I've lowered all my settings. I allow 5 torrents to run at a time (all uploading right now), at 25 kB each. I allow 40 connections total; 10 per torrent and 10 upload per torrent. Global max up rate is 400 (which is not reached right now, cause 25 *5 = 125 kB). I have a 10/10 Mbit connection, so it shouldn't be choked by these speeds at all. My router is a Netgear RP614v2, with latest firmware update. Everything works nicely otherwise, and it's really weird that µTorrent would do this (especially at these _low_ settings; I had much higher in 1.3).Anyone with an idea? Maybe someone could point me to a good networking monitor?Oh, btw.. Running AVG antivirus, but that shouldn't matter. Link to comment Share on other sites More sharing options...
Firon Posted February 19, 2006 Report Share Posted February 19, 2006 And if you bypass the router, what happens? Link to comment Share on other sites More sharing options...
QauNuckShin Posted February 19, 2006 Author Report Share Posted February 19, 2006 Wow, I'm stupid. Haven't even tested. Brb. Edit, so as to not violate the very probable "No double posts"-rule.Nah, didn't help. Start surfing to a page.. nothing happens. Shut down µTorrent.. Page loads instantly. Link to comment Share on other sites More sharing options...
Firon Posted February 19, 2006 Report Share Posted February 19, 2006 Oh, and Microsoft released a patch that overwrites your tcpip.sys, might wanna check it again Link to comment Share on other sites More sharing options...
QauNuckShin Posted February 19, 2006 Author Report Share Posted February 19, 2006 Yeah, I saw that earlier today. Already repatched. :/(checking again, so as to not look like a fool when I finally realize I just _thought_ I did... Nope, it's all good.)Edit: (besides, the max half open is set to 8, which should work with the 10 limit anyways..) Link to comment Share on other sites More sharing options...
Switeck Posted February 20, 2006 Report Share Posted February 20, 2006 Are you using UPnP and/or DHT?Are the torrents you're trying to connect to overloaded with firewalled seeds/peers?If your µTorrent tries to connect to a firewalled seed/peer, it naturally fails...and takes potentially a minute or so to do it. There seems some weird conditions that can also occur which leave those connections unclosed even 10+ minutes later. These pile up...then bad things happen. Link to comment Share on other sites More sharing options...
QauNuckShin Posted February 20, 2006 Author Report Share Posted February 20, 2006 DHT is on, UPnP is off.Now, get this. My ISP is going to shut down for 4 days now, for maintenance. How much does _that_ suck? Anyways, thanks for trying to help, but I'm not going to be able to test it for a few days now. Might still check in here from school, though.And another edit. Once again, I feel so stupid. Sorry for wasting your time. I was using the onboard NIC on an ASUS A8V (NIC was Marvell Yukon 88E8001 something), but before I had a PCI NIC, which I removed. Totally forgot about that. I reinserted it and disabled the onboard one, and what do you know, it seems to work. Not sure quite yet, but it's looking pretty good.Anyways, thanks for helping, and sorry for wasting your time. Link to comment Share on other sites More sharing options...
ul Posted February 20, 2006 Report Share Posted February 20, 2006 Even with an Intel PCI NIC directly connected to a DSL modem, I still get error 4226 occasionally, usually when closing & opening µTorrent. DHT off, UPnP off, standard tcpip.sys, halfopen set to 8.Not a big deal though. Link to comment Share on other sites More sharing options...
1c3d0g Posted February 20, 2006 Report Share Posted February 20, 2006 You need to patch your TPCIP.sys file and change the net.max_half_open parameter accordingly. :/ Link to comment Share on other sites More sharing options...
ul Posted February 20, 2006 Report Share Posted February 20, 2006 Thanks for the suggestion, but µTorrent does a pretty good job of keeping error 4226 to a minimum so I'm not going to patch it. (I don't like having to repatch every time a new security fix to tcpip.sys comes out, which seems to be quite often lately ...) Link to comment Share on other sites More sharing options...
Firon Posted February 20, 2006 Report Share Posted February 20, 2006 Well, you should patch it if you get connectivity issues or tracker timeouts. (the next beta should behave better in any case, this IS an issue with µTorrent) Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.