Firstly my thanks to all of you that helped here, I have solved the problem but it took quite a lot of investigation and I gained a great deal of insight into what had happened. As this may be of use to those searching this thread in the future I'll try to show how this was fixed - and what I think may be the underlying issues. Unfortunately I am certainly not an expert on DNS nor on how this is implemented in squeezeserver.
The issue seems to have arisen when "www.mysqueezebox.com" became a non resolved address for my default DNS server (selected via the router preferences, and usually determined by the Internet Service Provider). This gives the appearance of the MSB website being down, an error messages about unresolved address in the web browser and if you are logged onto a local server access to any of the apps that rely on using your registration at squeezenetwork becoming unavailable (I was listening to last fm at the time and it just mysteriously stopped working). Interestingly it was possible to connect to mysqueezebox.com directly via the player interface (via network setup) and on the diagnostic screen it was able to show connected to mysqueezebox.com with an IP address, a positive 'ping' and an open PORT 3483. Also using the https prefix I was able to access through the web interface. It could also be adressed directly via any browser using the IP addresses shown on the diagnostic screen and which were given by Mnyb above. All very mysterious... Changing the DNS server for the router fixed the ability to contact through the web, but still couldn't access apps via squeezecenter. A clean re-install of squeezecenter did not fix it - including a move back from 7.5 (trunk and embedded) to 7.43 on both computers where I have squeezecenter installed. ipconfig/flushdns did not fix the problem but ipconfig/release and then stopping and restarting squeezecenter did. I note that squeezecenter has a couple of PERL modules that may relate mDNS.pl amd DNS.pl which I think act as fall-backs to alternative DNS servers if the primary fails, or if it accessing via squeezecenter (haven't fully understood the code here). It seems this is cached at the DNS server somewhere - and not at the routers default DNS. So bottom line - for those that search the forum in the future - if this happens on your windows system, I hope it may save you some pain: 1. Stop squeezecenter running 2. Access the cmd prompt via the machine running squeezecenter 3. type ipconfig/release at the prompt It may take several minutes for this to work, depending on your network and the DNS server so wait before restarting the squeezecenter. You will know its ok if you select your local server and apps are available and on the plugins settings page there are no error messages about mysqueezebox.com being unavailable. I will look and see if there is a bug open on this perhaps. Thanks to Mnyb, toby10 and Siduhe for your pointers. PS. For those using linux based systems - DNS handling appears very different, you hopefully will never experience this very special treat! I may just end up installing a linux OS on my main machine after this. -- linvale Squeezcenter running on ACER R1600 Windows XP Fileserver ReadyNAS Duo Main Listening Transporter / Controller Kitchen : SB3 Bedroom : Boom Bath : SBRadio Study: Duo ------------------------------------------------------------------------ linvale's Profile: http://forums.slimdevices.com/member.php?userid=22828 View this thread: http://forums.slimdevices.com/showthread.php?t=76330 _______________________________________________ squeezenetwork mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/squeezenetwork
