[beta 483] UDP listning port not closed at shutdown

[Klaus_1250]

Yesterday I turned on DHT since a long long time. Did its job, downloaded a torrent and then I closed uTorrent. A few hours later, during the same Windows session, I fired uTorrent up again, but I was instantly greeded with a red status light: Listning port not available. I checked with netstat to see what was using it, and found an old unused pid and [system] attached to uTorrents UDP-port. For some reason, after closing uTorrent the last time, the UDP listning pot did get released.

[Switeck]

You wouldn't be using UPnP in µTorrent and on your router would you?

UPnP isn't always smart enough to know when to release ports to other apps (or even the same app!) for reuse.

[Ultima]

What router do you use? It's odd that no one else has reported this before, and I don't think ludde changed UPnP in such a way that it would affect it like that between 474 and 483 =o

[Klaus_1250]

Nope, everything is static. No UPnP (is enabled on router, but don't use it for p2p, just MSN), ports are forwarded, ip is static.

[Ultima]

That's even weirder... does it happen all the time? I've had that happen to me once or twice before (on older versions) when I exited µTorrent improperly (well, more specifically, forced it to quit), but it resolved itself after a few minutes.

[Klaus_1250]

In my case, it didn't resolve itself. The UDP-port was still listning several hours later (needed to reboot). uTorrent was closed properly. Will try to play with it as soon as all active torrents are finished to give some more feedback.