I am now listening to glorious music pouring through my Eton 11.2
speakers coming from. you guessed it -- the SB2!!!
In my case there were several things going simultaneously and a good,
patient, computer programmer friend came over and plugged away till
suddenly, it worked!!! Problem was,
I have a similar problem.. I followed all the advice here, and posted
my results under my initial query
http://forums.slimdevices.com/showthread.php?t=14740page=2pp=10
Rather than clog up Andy's post, if anyone has the time to take a look
I'd greatly appreciate it.
It's a tad disheartening to
Hi, Adrian -- just a quick note to let you know that I took a breather
from the Slimserver stuff and will answer your questions this evening,
hopefully. Thanks for your continued help. I really do appreciate
it.
Andy
--
awm
___
Discuss mailing
dbls, thanks for the tip. Will make things much easier for me.
Andy
--
awm
___
Discuss mailing list
Discuss@lists.slimdevices.com
http://lists.slimdevices.com/lists/listinfo/discuss
Hi, Adrian -- the address is: 192.168.1.3 or 1.4 For some reason, that
perhaps you'd understand better than I, it's been both, meaning it was
initially 1.3 and now it's 1.4
I assume by netstat output, you mean what shows up when I enter that
command? Stuff similar to what I posted on the
awm wrote:
Btw, is there any way to copy and paste what comes up in the DOS
screen? I'd like to show you directly.
Either click the icon in the title bar, or right-click elsewhere on
the title bar, then choose Edit - Select All from the menu, or
Edit - Mark and select with the mouse; then
Andy,
It seems we are in separate timezones - you may get a faster response calling
slim support
However assuming you want to continue.
1) IP address of the squeezebox is normally dynamically assigned using a protocol called DHCP. The most common case is for your
wireless router to give
Adrian -- I pinged the address and got back info about packets sent (4)
and received (4), evidently successfully, with 0% loss.
Er, now what?
Thanks,
andy
--
awm
___
Discuss mailing list
Discuss@lists.slimdevices.com
Hi, Kirsch -- thanks for the tip. if I could actually get to the config
set-up for the router, I'd try it. Thus far unsuccessful, though I'll
keep trying.
Thanks,
Andy
--
awm
___
Discuss mailing list
Discuss@lists.slimdevices.com
OK this shows that the server can talk to the player, so the wireless link is
working OK.
Could you tell us what the IP address of the player is and what the output of
netstat is?
Did you enter the address of slimserver into the player or let it auto discover [in which case is it trying to
Andy,
Sorry for previous misunderstanding.
When squeezebox starts up it will say something like obtaining IP address and then give a number in the format: A.B.C.D this is
the IP address for the squeezebox that your wireless router has assigned it. Note this down.
To ping this addres: Open a
Hi, adrian -- thanks and I appreciate your attmepts to help, so no
worries at all. I'm at work at the moment and will be able to do the
pinging when I get home later this evening.
Thanks,
Andy
--
awm
___
Discuss mailing list
I am not sure if this will help but I had a similar problem with my SB2.
My solution was to add the MAC address to my Network Router. The MAC
address is on the bottom of the SB2. I had to get to the LINKSYS
configuration and in there was a tab that had MAC addresses. Onced I
addded the SB2's MAC
First off, thank you for responding. I've interspersed the answers to
your questions and sorry for not providing this previously.
) what OS
XP pro
2) what version of slimserver
The latest. I downloaded whatever was on the site last week in an
attempt to see if this was the root problem.
3)
Whoops. The answer to your # 5 about netstat was wrong.
Here is what netstat says:
TCP Mycomputer:http localhost:2920 TIME_WAIT
TCP Mycomputer:2921 localhost:9000 TIME_WAIT
TCP Mycomputer:2927 localhost:9000 ESTABLSIHED
TCP Mycomputer:9000 localhost:2923 TIME_WAIT
TCP
On Sun, Jun 26, 2005 at 01:16:25PM -0700, awm wrote:
:
: Whoops. The answer to your # 5 about netstat was wrong.
:
: Here is what netstat says:
: TCP Mycomputer:http localhost:2920 TIME_WAIT
: TCP Mycomputer:2921 localhost:9000 TIME_WAIT
: TCP Mycomputer:2927 localhost:9000
Hi, Mikeb --
thanks for the tips. I tried what you suggested and got a ton of
listings, but nothing for 9000 or the 3483.
What does this tell you?
Andy
--
awm
___
Discuss mailing list
Discuss@lists.slimdevices.com
Hi, mikeb -- did as you suggested:
Try this;
stop slimserver
netstat -b (make sure nothing is on 9000 or 3483)
start slimserver
check the process list to see if it's running
netstat -b (show us the output of 9000 / 3483)
Then open a cmd window, and run; telnet localhost 9000
If it connects
OK, this is weird. I tried to repeat the suggested procedure, starting
from stopping Slimserver, accessing dos CMD and entering netstat -b.
This time, a lot more stuff went by than previously, and the 9000 port
was included in the following manner: TCP Mycomputer:9000
Localhost:1286
On Sun, Jun 26, 2005 at 02:35:14PM -0700, awm wrote:
:
: Hi, mikeb -- did as you suggested:
:
: OK -- here is where things apparently went awry. Everything went as
: you indicated, and a bunch of HTML flew by. Then, at the bottom, it
: said,Connection to host lost.
:
: So, where does this
Andy,
I think this is OK.
Can you open a web session to slimserver. Open explorer and type in
http://localhost:9000/
This shows port 9000 is working if you get the slim banner.
Then try starting softsqueeze from the web page (go to softsqueeze under help). It should give you two tick boxes
Thanks for the help --
mikeb, I'm pretty sure I don't have a remote box on which to try this,
even if I knew what a remote box was. I just have the laptop, router,
card and SB2.
Triode, I accessed the web interface with Slimserver and went to
Softsqueeze. It worked fine. But, no progress on
Triode, I accessed the web interface with Slimserver and went to
Softsqueeze. It worked fine. But, no progress on connecting.
So this suggests the problem is entirely within the PC as one piece of software
can't speak to the other!
i don't think I tried disabling Spystopper previously.
On Sun, Jun 26, 2005 at 11:31:26PM +0100, Triode wrote:
: Triode, I accessed the web interface with Slimserver and went to
: Softsqueeze. It worked fine. But, no progress on connecting.
:
:
: So this suggests the problem is entirely within the PC as one piece of
: software can't speak to the
Mikeb, you got it. I am able to play music through the Softsqueeze but
the SB2 is unable to connect to Slimserver.
Since I think I have adjusted any and all firewall possibilities, any
idea on what the network problem might be? Everything else on the
network works fine. It's a Netgear
On Sun, Jun 26, 2005 at 04:35:04PM -0700, awm wrote:
:
: Mikeb, you got it. I am able to play music through the Softsqueeze but
: the SB2 is unable to connect to Slimserver.
:
: Since I think I have adjusted any and all firewall possibilities, any
: idea on what the network problem might be?
Sorry to trouble you, but how would I ping the Squeezebox from the
Slimserver? When my friend was over (referred to early in this
thread), he was able to ping something to something, which ruled out
something :) As you can tell, I'm not fluent in the ins outs of
dos/cmd line prompts and
I am 'the other poster' and I solved my problem. The squeezebox was
once connected prior to a fatal hard drive problem on the server box.
Once I got everything rebuilt, then I had connection problems as
detailed above.
The fix for me was simple: do a factory reset of the SB2. Unplug the
SB2,
28 matches
Mail list logo
