Comment 3 for bug 1269933

I think it would be better to decide first that if there's anything to fix here at all.

First of all I'd beg to differ to the reporter as since the Automatic Connectivity Setup introduced the amount of passive users in DC network (and along with it, the support requests about connection problems) has been definitely lowered.

Secondly, I fail to see how periodic port mapping re-attempts would result much more active users. If the port mapping fails for the first try it's unlikely it'll succeed for any subsequent tries.

Moreover if the search/download doesn't work, the user won't wait for 30/60/whatever minutes, rather they'll do some action a lot sooner which, in almost all cases, includes a client restart. If the user restarts the client/OS then the required redetect will happen at the next start.

And at last but not least, while the case in comment #1 is not related to this report (it's more likely because of a delayed $UserIP procesing due to the excessive resource demand of auto-connecting to extremly large amount of hubs - and the problem goes away automatically after the sent IP is processed), timely redoing the connection detection possibly results just that exact confusing error message in some hub/script usage scenarios.

So I guess it needs some more thinking of what we can gain and what to lose with this new feature.