Re: Re: slimp3 connector-actively refused

[Stuart Booth]

On Tue, 29 Jul 2003 17:12:14 -0000, "max_adamiec"
<<a
href="/group/xap_automation/post?postID=qDANo_Q_55Van2z0vAIiCsucOyHz-rW_HfuXxJz4OBPWUl6Yy8onzdZXmgPjFwc8WMVjE8cwbjx0FVPOlxDI">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
--
Stuart Booth
xAPFramework.net - a reusable xAP framework for .net

<a href="http://www.xapframework.net/";>http://www.xapframework.net/</a>
<a
href="/group/xap_automation/post?postID=efXnIjlBA8De5FReR4O-zherdQLvjpq3oCXYIa_2HmLjmQgwujpzVG5dmL_ZexY1NIA32Dl582JGvoS2HvRE">stuart@x...</a>