zumpiez Posted April 27, 2008 Report Share Posted April 27, 2008 I get a red ! in the status bar, but my port is forwarded properly and the web test reports it as open, as do a few other web-based tests. Should I just ignore this or is this actually indicative of a problem? Link to comment Share on other sites More sharing options...
Ultima Posted April 27, 2008 Report Share Posted April 27, 2008 So the port checker in the Speed Guide definitely shows the port to be open as well?Edit: And uh... it looks to me like you're behind a school network, in which case, your port isn't likely to be open in the first place... Link to comment Share on other sites More sharing options...
zumpiez Posted April 27, 2008 Author Report Share Posted April 27, 2008 I'm posting from work, the computer I'm torrenting from is on residential comcast. Sorry for the confusion.Yeah, the port checker shows all clear. Link to comment Share on other sites More sharing options...
Ultima Posted April 27, 2008 Report Share Posted April 27, 2008 Hrm. FWIW, Comcast is known to do stupid things sometimes with regards to BitTorrent. Try another adding another torrent, like from here. Does the status bar light change?Oh, and mouse over the status light next time to check the tooltip. It might be a listening error (where another application is already using the same port that µTorrent is trying to bind to).Edit: Oh, heh, you already mentioned listening error in the title... in which case, you're going to need to figure out which application is using the port, or use a different port for µTorrent altogether. If you want to find out, get TCPView from sysinternals.com and run it on the home computer. If another application is using the port, you'll see on the list. Link to comment Share on other sites More sharing options...
zumpiez Posted April 27, 2008 Author Report Share Posted April 27, 2008 It was indeed a listening error. I just remoted home, changed the port it was using (It was 49153, now 49150) and that worked fine.I can't fathom what was trying to also listen on 49153 of all ports, but thank you!edit: and like magic all of my torrents are running much faster. double win! thanks, you are my hero. Link to comment Share on other sites More sharing options...
Ultima Posted April 27, 2008 Report Share Posted April 27, 2008 Excellent If you want to find out what was using the port, then like I mentioned earlier, TCPView should help you do just that An improper shutdown of µTorrent might also cause this to happen, though that's not very likely to be the cause. Link to comment Share on other sites More sharing options...
Switeck Posted April 27, 2008 Report Share Posted April 27, 2008 Sometimes if you manually port forward AND use UPnP, they conflict and fail to work. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.