Re: Re: slimp3 connector-actively refused

[James]

grin...

If it helps I also found that the linux server used a different port to
the windows one. I havn't got either to hand at the moment but 9001 was
one port and the other was mentioned in a comment in the connector's
config file

and yes it would be great if it could talk to the linux server without
killing it. Random feature or bug? ;-)


HTH

James

On Tue, 2003-07-29 at 20:02, Stuart Booth wrote:
> On Tue, 29 Jul 2003 17:12:14 -0000, "max_adamiec"
> <<a
href="/group/xap_automation/post?postID=rfAKfM_hFQ40gHvFfhZl-3U9E_Gs8FA_wm5vtyGzsCglppmh6rkEivPIkr4GVLFzuBWD2wZzxkmMnTGtwSwij9p0">max@v...</a>>
wrote:
>
> >I've set the correct port number. As you say, the server defaults
to
> >9001.
> >Now the console reads
> >slimp3 server: 192.168.1.11[192.168.1.11:9001]
> >slimp3 players detected:
> >unable to read data from the transport connection
> >
> >Slimp3 says "cannot connect to the slimp3 server. is a server
> >running at 192.168.001.011?"
>
> You know, I think I may have crashed the Slim Server software! This
> thought just came to me.
>
> James had a problem with the SliMP3 xAP Connector app causing the
> *Linux* server to crash, whilst the Windows version was unaffected.
> But you're running on WinXP, which makes me think the problem is now
> affecting that as well.
>
> Dean from SlimDevices emailed me about James' problem but I confess
> I've been so busy lately I've not looked into that (Sorry, James, I'd
> all but forgotten until now).
>
> Apparently:
>
> 66
> We got a report from one of our customers about a problem with xAP and
> SLIMP3.
>
> Have you seen this before? I wonder if it has to do with the change
> in the latest version to use the MAC addresses to refer to the players
> rather than IP:port.
> 99
>
> And I'm still using IP:port to address them. I wonder if that's the
> problem in this case.
>
> I actually noticed last night whilst testing the Slim Server port
> number thing I posted about, that I'm running a v4.1beta build of the
> server s/w and haven't updated it in a while.
>
> I'll test that myself later.
>
> S