Headboy100 wrote:
> I don't know if this will help (or if its poor protocol to copy chunks
> of files directly into messages) but here is a dump of the relevant part
> of the Touch log file. Hopefully someone with more knowledge of this
> than me might spot something. Is the bit about skipping wake on lan
> significant?
>
> I couldn't see anything in the LMS log file that seemed to relate to the
> connection attempt.
>
> Oct 19 23:30:29 squeezeplay: INFO applet.ChooseMusicSource -
> ChooseMusicSourceApplet.lua:215 Using existing server with same ip
> address: SlimServer {192.168.0.39}
> Oct 19 23:30:31 squeezeplay: INFO applet.ChooseMusicSource -
> ChooseMusicSourceApplet.lua:648 connectPlayerToServer() LocalPlayer
> {Squeezebox Touch} SlimServer {192.168.0.39}
> Oct 19 23:30:31 squeezeplay: WARN squeezebox.server -
> SlimServer.lua:624 wakeOnLan(): SKIPPING WOL, self.mac: nil,
> self:isSqueezeNetwork(): false
> Oct 19 23:30:31 squeezeplay: INFO squeezebox.player -
> LocalPlayer.lua:203 connectToServer(): connecting localPlayer to
> serverSlimServer {192.168.0.39} via internal call
> Oct 19 23:30:31 squeezeplay: INFO net.slimproto - SlimProto.lua:592
> connect to 192.168.0.39 (192.168.0.39)
> Oct 19 23:30:31 squeezeplay: INFO net.slimproto - SlimProto.lua:152
> Send HELO: reconnect-bit=0 bytesReceived(H,L)=0,27362083
> Oct 19 23:30:51 squeezeplay: WARN applet.ChooseMusicSource -
> ChooseMusicSourceApplet.lua:634 Connection failure or Timeout, current
> count: 21
I do not read code that well, but I know some background facts .
WakeOnLan aka WOL is something the squeezebox always try against it
latest conected server , this is quite neat as many modern computers
will be in sleep mode when not used for a while and hence not visible to
the Touch .
Even a successfully WOL can take some time depending on the computers
status how fast it wakes . It can even boot the computer. In such case
you try to choose "my music" Touch find no server but it sends out the
WOL command either waking or booting the machine , but if this takes to
long you will have an error message ignore that and don't touch anything
and it will fix itself when things are ready , that is how it is
supposed to work .
Now I don't know if this is relevant to your NAS at all if it has a
sleep mode or if it is supporting wakeOnLan at all .
What can throw in a spanner here is that almost no wifi network cards
supports WOL , but this probably does not apply to your NAS . But in
such cases LMS running on a wifi conected laptop that goes to sleep
could be unavailable until someone manually wakes it up .
This is another reason to why we recommend thatnthe server should be
wired .
Back to,the subjects of ports . There can be another problem that can
thwart conectivity that is if the server and the player is not on the
same network and subnet for example in your case 192.168.0.x and subnet
mask 255.255.255.0 where x differs on the clients . You can get this
even if you think have the rigth ip adresses by using another router as
wifi ap but connecting or setting it up the wrong way so that it forms
it own network ,it may itself be a client to the main router .
------------------------------------------------------------------------
Mnyb's Profile: http://forums.slimdevices.com/member.php?userid=4143
View this thread: http://forums.slimdevices.com/showthread.php?t=96804
_______________________________________________
Touch mailing list
[email protected]
http://lists.slimdevices.com/mailman/listinfo/touch
