Windows installation sometimes exhausts TCP port allocation

We've seen a few cases where either the initial installation or the process of clustering two nodes together can cause Couchbase to exhaust the number of TCP ports available on Windows systems. This is made worse by the default settings on some Windows installations of only a few thousand available ports and has been worked around by: http://msdn.microsoft.com/en-us/library/aa560610(v=bts.20).aspx

This bug is to investigate both the cause of this, and what the Couchbase server can potentially do to force the increasing of this limit.