Bugzilla – Bug 9454
SqueezeServer setup should reserve ports it needs
Last modified: 2009-09-08 09:16:38 UTC
Microsoft (and other vendors) recently introduced fixes to their DNS servers in order not to make the exploitable. The Microsoft DNS implementation (affects all server products) does this: At service start, it reserves 2500 randomized UDP endpoints for its use. Those may (a 2500/65535 chance) conflict with the ports used by SqueezeCenter. DNS always starts before SqueezeCenter. Resolution: SqueezeCenter Setup should reserve the ports it wants to be available. How this can be done is described here: http://support.microsoft.com/kb/812873/en-us It took me quite some time to figure out why my SqueezeCenter was no longer responding after yesterdays Windows Update and Server Reboot. Reserving ports 9000 and 3483 as described in http://support.microsoft.com/kb/812873/en-us did the trick. This is nasty to track down, and will affect every SqueezeCenter installation (all versions) on Windows, where a DNS server is installed. You should take the necessary steps to reserver the ports in your setup.
some existing (indirect) discussion in the forum: http://forums.slimdevices.com/showthread.php?t=51705
change 23149
Alex - do you have some URL where I could read up on that change in Windows' behaviour? The ports are now reserverd as per your request. But I'd like to better understand what exactly MS did here. Thanks!
Michael says this is fixed
Verified SC reserves port ranges per instructions. 9000-9000 9090-9090 9092-9092 3483-3483
This bug has been fixed in the 7.3.0 release version of SqueezeCenter! Please download the new version from http://www.slimdevices.com/su_downloads.html if you haven't already. If you are still experiencing this problem, feel free to reopen the bug with your new comments and we'll have another look.
Reduce number of active targets for SC