Just to confirm - my Windows LMS runs 24/7 and I still get a timeout on
the first connection of the day (or when it's been idle for a few hours
and the HDD has gone into sleep mode). So presumably the timeouts are
happening while waiting for the HDD to spin up.
To correct my earlier post - I DO a
I have hit a compromise , I WOL from completely shut off , booting my HP
microserver , but then it does not sleep .
So I just boot it when I get home from work , touching any of my players
then let my server run during the evening and then turns it off when I
go to bed .
Some weekends it may run
i desisted to try to use WOL, i could never get it to work so it
wouldn't irritate me. hence i built a relatively low power but good
performance machine that i just leave always on. shame. if anyone has a
fool-proof method i am also very interested. then again my stereo pulls
80w in standby mode,
toby10 wrote:
> What about an actual hardware player attempting to connect by itself (no
> App)? Same result? Sure computer is not going into sleep/hibernation?
> Any chance the computer is getting a different IP (maybe router is
> re-leasing IP's nightly)?
I tried a search from a Squeezebox
Squeezed_Rotel wrote:
> I have always experienced this behavior using 7.3 through 7.8. My server
> is a W7 box that sleeps 24/7, or until a boom or iPad sends a wake up
> (wol). In my case, the server never completes the wake up in time to
> prevent the "waking up server...connecting...cannot con
I have always experienced this behavior using 7.3 through 7.8. My server
is a W7 box that sleeps 24/7, or until a boom or iPad sends a wake up
(wol). In my case, the server never completes the wake up in time to
prevent the "waking up server...connecting...cannot connect..." string
of messages...
What about an actual hardware player attempting to connect by itself (no
App)? Same result? Sure computer is not going into sleep/hibernation?
Any chance the computer is getting a different IP (maybe router is
re-leasing IP's nightly)?
-
I run LMS 7.7.2 on Windows Server 2008. I always find that the first
request sent to the server each day from a mobile device (e.g. the
Logitech Android app) always results in a connection timeout. This can
be song search, or a simple list of New Music for example. I have to
repeat the request sev
