tjohns

Is there any reason why 1.6.1 would startup with "real" random ports (up to 65000+) then? And if the randomize button can allocate ANY port number later, why not allocate the same numbers at startup? And is it just me, or do the UPnP ports NOT get unmapped on exit??? I can start up WireShark & check the network packets to my DG834GT modem to discover the difference between 1.6.1 (that does work) and the beta. Trev

1137 seems to have fixed the UPnP problems I was having with the previous 2 betas, but it still seems to not use a true "random" port at startup (see my post #229). The manual randomize button does give various ports, but startup ports always seem to be low (2000-4000) "generic use" numbers. Can anyone confirm that they ever get high range random ports (up near 40000-65000) at startup?? Also, uTorrent doesn't "unmap" the UPnP port when closed ... my modem shows it still open. Trevor

Running on XP Pro with Netgear DG834GT ADSL2+ modem (Kerio firewall off while testing)... 1.6.1.490 - never a hiccup; everything as per the book 1.7 build 1111 - auto-randomize startup port fine; display issues on General tab & Move Up button; port not unmapped on exit 1.7 build 1137 - always had zero port number at startup; never auto-mapped a startup port; manual randomize would kick in fine (including unmapping old port); port not unmapped on exit; display issue on Move Up button NOTE: even though it showed zero as startup port, uTorrent was "listening" on what appears to be the first "generic" port number it uses. All further connections begin numbering sequentially from this. 1.7 build 1170 - startup port now shows non-zero (but never gets mapped - even after a 10 hour period); startup port isn't "random"...always seems to be a low-thousands generic port as above; manual randomize ok (including unmapping any previous port); port not unmapped on exit Trev

I've got the zero (random) port problem too. I don't thinks it's just a display issue, as it doesn't seem to try mapping ANY port at all. Hitting the randomize button forces a new number in & everythings fine after that. Also in 1137, when I exit uTorrent (from File menu or right-click tray icon) it doesn't unmap the uPNP port it was using. Re-randomizing the port during a session DOES close the old before generating a new one though. Might have been in previous beta as well, as I recall seeing extra ports left open before.