I honestly can't say. I thinking you're running into DHCP lease issues
or your router is dropping packets or something arcane like that. If
it helps, yes, this is the very sort of weird network problem you
shouldn't have to sort out on your own. But it's definitely a
networking problem.
The Server IP address is indicative of a network issue. It should be the
same as your EMac. If an odd number is showing up, then the Emac may be
losing the IP address assigned by the router (try lengthening or
reserving the DHCP lease for the Emac).
Also, it seems that there are known issues
I have owned Squeezeboxes for many years and have, from time to time,
experienced problems that required me to delve into Network
Administrator territory. I know little about computer networks and I
don't care to know anything at all about computer networks, just as I
know nothing about fuel
asd123 wrote:
I have owned Squeezeboxes for many years and have, from time to time,
experienced problems that required me to delve into Network
Administrator territory. I know little about computer networks and I
don't care to know anything at all about computer networks, just as I
know
My approach to your problem would first be to uninstall all aspects of
slimserver. somewhere in this forum there's detailed instructions on
how to properly uninstall on a mac. next, upgrade your os to
osx10.4.11.
then I'd try to reinstall the latest version of squeezecenter.
hopefully a clean
Peter wrote:
If you don't want to administer networks you shouldn't try setting one
up in your home.
The reality is that serious networking devices are moving quickly into
mass market, not just SqueezeBoxen, but Chumby, weather stations, and
all sorts of stuff.
The days when folks would
If you're going from SlimServer 6.5.4 to SqueezeCenter, you should
probably remove the SlimServer cache.
There have been changes in the structure of the cache, I forget when
that happened, and your symptoms are typical of a cache issue.
Why 6.5.4 isn't working properly I can't say.
--
danco
Pat Farrell wrote:
I have not worked on a car in about ten years. They are too complex, and
require tools that I don't have in my six foot high tool chest. What the
car designers have done is eliminate all of the simple maintenance, but
when it goes wrong, it really takes an expensive
Peter wrote:
Buy a 21 year old car like mine and you can go back to diy.
Yeah, I did my own on my 85 Mustang GT. It even had a carburetor.
I expect that networks will get there in the near future.
I'm not so sure. Setting up a network used to be much more difficult.
Now it's so easy
This is a networking problem, so to troubleshoot it we need information
specifically about your network. The types of computers, operating
systems, squeezecenter version, and squeezebox firmwares are all pretty
much unrelated to the problem.
Are you using a wired network or a wireless network?
I owned a 67 Mustang and did all the work myself too. Newer cars are
much harder to work on, but fortunately much more reliable as well, so
hiring a professional (at $90 an hour) isn't necessary very often.
Same thing with the Squeezebox. I'd love to have a professional fix the
problem, but it's
11 matches
Mail list logo
