I appreciate your time and effort in replying: you / others may be interested in a bit more detail -
"just allow your AV software to access the ports -- you've probably got them blocked off." I have added incoming and outgoing rules for the ports (UDP and TCP) listed in the "Feature Guide", i.e. UDP 3483, TCP 3483 and TCP 9000, also a couple of others that crop up in firewall logs etc. (9090 and 33827). Maybe I haven't quite cracked this yet: in the absence of anybody responding who can give some detailed information I now have a detailed query in to both Avira and Slimdevices. (Attached) "Note -- although this is NOT a Windows Forum I'd suggest you uninstall your current AV software and use MSE (FREE BTW) or Microsofts Forefront Client Security package." I really shouldn't need to switch my AV/Firewall software to suit glitches/difficulties generated by Squeezebox (or any other commercial application/hardware). The system requirements of the SB package do not refer to specific firewall software. "If you look on various Windows Forums you'll find that the AVG package causes far far more problems than it solves and you would be better off switching it to use something else." Probably true - I am sticking with Avira for a number of reasons and reluctant to return to AVG after one attempt which resulted in immediate loss of internet and intranet access. "If you are running XP or Windows 7 why not use MSE (Microsoft Security Essentials) instead -- very small footprint, definitions updated almost dated and does a first class job. Finally with Microsoft involved in protecting their own OS'es the Software SHOULD be good." I installed Live One Care last year and Microsoft subsequently withdrew support (with a partial refund), so I cannot consider them reliable, let alone not wishing to support their OS based market position across the board. "Incidentally 99% of Connectivity problems with squeezebox type devices when using Windows are with IP address conflicts -- the problem often is that your controller / device is trying to use an IP address that's already allocated and Windows won't report IP conflict. If you force your SB server to use 192.x.x.2 or 10.x.x.2 depending on your router / network you normally won't get any problems connecting." This is a new aspect of the problem, again maybe emphasising just how flaky the SB installation is. However I can confirm that my most recent detailed testing was with the SB server running on the machine with an IP address 192.168.1.2. (See attached) Regards John +-------------------------------------------------------------------+ |Filename: Query text 100105.txt.pdf | |Download: http://forums.slimdevices.com/attachment.php?attachmentid=8978| +-------------------------------------------------------------------+ -- BonzoUK ------------------------------------------------------------------------ BonzoUK's Profile: http://forums.slimdevices.com/member.php?userid=35593 View this thread: http://forums.slimdevices.com/showthread.php?t=73535 _______________________________________________ Radio mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/radio
