Usually the two main reasons for this are:
1. Other networks in your area are using the same channel and causing
confilcts. TO check this you can run Netstumbler on one of the machines
with a wi-fi card. If that is the case try changing the channel of your
network (or get you neighbours to do it
jordimr;263280 Wrote:
> Wow - thank you for your quick replies.
>
> I am running SqueezeCenter 7.0 on Windows Home Server (Windows Server
> 2003).
>
> The player runs firmware 84, and it is wirelessly connected. It obtains
> IP address through DHCP, and has a wireless strength of 96%.
>
> Sque
Wow - thank you for your quick replies.
I am running SqueezeCenter 7.0 on Windows Home Server (Windows Server
2003).
The player runs firmware 84, and it is wirelessly connected. It obtains
IP address through DHCP, and has a wireless strength of 96%.
SqueezeCenter has a static IP address.
I'll
You don't give much information - what OS are you running, what version
of Slimserver and are your running with the SB wired or wireless?
One thing that might cause this (if you are running wireless) is an IP
conflict or a firewall problem. I saw behaviour very like this
recently, when we boot
I think I've seen such a thing, but it was after a firmware update,
never in other circumstances.
I think you have a network problem or something else (dhcp lease?
wireless problems? bottlenecked server?)
If you can, try using SB directly in squeezenetwork with an ethernet
cable to the router, i
Hi there,
I have been using my SB for about three weeks. During this period, I
have had the reset the device at least five or six times, by unplugging
it from power, and plugging it back in.
I don't know what causes it; all I know is that the screen goes black,
and that it doesn't matter what I