mherger;467429 Wrote:
I cannot connect to 7.4 running on Mac OS 10.6 via the web interface
on
any computer other than the host Mac. iPeng 1.2 works just fine.
No
If iPeng can access it, you should be able too. What URL are you using
on
your local machine? What on your other
7.4 and 7.4.1 both have real problems with the HTTP Port 9000 setting - when
starting either of them it takes 10 mins before I can communicate via the
Web interface. Initially the new Squeezebox Server Status Window reports
'Failed' against HTTP Port 9000. How do I change the port Squeezebox
H.loads fine for me, loads quickly.
Are you sure 9000 is correct within SBS Settings Advanced
Networking?
Nothing else using 9000 on your system?
--
toby10
toby10's Profile:
Also, what antivirus/internet security are you using - for example,
there is a specific issue with ESET/NOD32 and 7.4 which may show up as a
port 9000 issue - and is fairly easily fixed.
--
Siduhe
Who am I on 'LAST.FM' (http://www.last.fm/user/siduhe)?
-Siduhe Loved Tracks radio got the
7.4 and 7.4.1 both have real problems with the HTTP Port 9000 setting -
when
starting either of them it takes 10 mins before I can communicate via the
Web interface.
But will it then communicate on port 9000 or some other?
___
discuss mailing list
I cannot connect to 7.4 running on Mac OS 10.6 via the web interface on
any computer other than the host Mac. iPeng 1.2 works just fine. No
Softsqueeze, no Squeezeplay. Tried changing more firewall and router
settings than I can remember with no luck. I'd be happy to check my
server log to
I cannot connect to 7.4 running on Mac OS 10.6 via the web interface on
any computer other than the host Mac. iPeng 1.2 works just fine. No
If iPeng can access it, you should be able too. What URL are you using on
your local machine? What on your other machines?
friendlyfire wrote:
Hi,
I'm having a difficult time resolving a problem that I am sure is a
side effect of my LAN topology and hope someone here can offer advice.
Here is the situation:
Most of the PCs in the house connect directly to a primary router
including the slimserver host. All
Hi,
I'm having a difficult time resolving a problem that I am sure is a
side effect of my LAN topology and hope someone here can offer advice.
Here is the situation:
Most of the PCs in the house connect directly to a primary router
including the slimserver host. All of these machines can
