Topic: MP3 Blade

[Bob Jenner]

I have the MP3 blade setup on my server at http://ntrigue.tndi.net/music/.
It seems to work ok, only I get a "http 404" not found message when I click to stream any of the content. Am I doing something stupid here or ??

There are spaces in the titles, but that automatically equates to a %20 as it should. I can get to the files and save them locally, just not stream them.

The SME5 server, patched to patch 3 is behind a firewall.
Is there another port I need to open for this to work??

Thanks !

Bob

[Jim Armagost]

Bob,

I am having the same issues as yours if I read your post correctly. I am able to run the MP3s from my blade only if I use the "fetch" link. If I use the stream, it gives me an error "access to the specified device, path, or file is denied".

I have tried a few things and have not gotten it to work correctly.

Just wanted you to know that you are not the only one out there. Hopefully someone else posted too, but I haven't seen anyone.

Good luck!

Jim

[Ralph]

Hello,

Can someone help us out on this issue, I also have the same problem as the two gentlemen above and it's really becoming so frustrating because I don't know where to start but I think it's a mime type problem. Don't tell me it's a bandwidth problem because I have plenty of it?.. Can someone lend us a few pointers here?...

Thanks in advance,

Ralph

[Dan G.]

I believe it is due to a hostname problem on your server.  Can you get to your server by typing http://www.xxYourDomainxx.com/mp3dir?  That's the URL that the scripts try to shove at winamp --- even if you try to use the IP address of the box.

[Bob Jenner]

If I am understanding right then, since my server is NOT www.tndi.net (that goes to another server) but ntrigue.tndi.net, that's why the blade does not work. Is that correct? I have two questions then ...

1. Assuming the above is true, WHY does the "fetch" link work?
2;. How do we fix it? Where do we need to edit what to make it work?

Thank You

[Dan G.]

I am going to investigate fixing it today, but I don't know how successful I'll be --- not much experience in picking apart scripts.

The fetch link could simply be coded with a different path reference...

Dan

[joako]

you dont need to, create a virtual domain so that it is the true domain of your server.

[Dan G.]

In my case, I have another server that actually is www.mydomain.com --- so I'll need to sort it out in the scripts.

[Jim Armagost]

I am not sure I understand. Is this a fix or is this just something to try?

If I have to create a virtual domain, what good is it to have my original domain propogated to the world?  I love the concept of the product and hopefully this will be fixed. But, I am not sure it has much to do with virtual domain names and such.

Joako, please help me to understand your logic in this. If this is something you did, and it fixed it, I will implement a change right away and see if it corrects mine too. If this does fix it, the question would be then, would I just create a new domain name as my "real" domain and then create my existing domain as the virtual so I don't have to make any changes to my DNS?

I like hearing how other people trouble shoot and determine how to correct something. Helps me in the long run and most of the time gives me new ways to expand on my current trouble shooting skill level.

Jim




joako wrote:
>
> you dont need to, create a virtual domain so that it is the
> true domain of your server.

[Bob Jenner]

More info:

Tool a look at the httpd error_log in /var/log/httpd/error_log. Found the following ...

[root@sme1 httpd]# tail error_log
[Fri Dec  7 11:40:44 2001] [error] [client 212.242.227.75] need AuthName: /music/classical guitar/andres segovia - classical guitar.m3u

Does this indicate that something is broken in httpd auth for the streaming m3u file type? Are there any additional log segments I should post?

Thanks to all who have replied.

Bob Jenner

[joako]

you said www.yourdomain.com is another server (not the e-smith server) so create a virtual domain that is the name you can access say sme.yourdomain.com and access the mp3 i-bay from there. Whats happening is that the mp3 software on the server is using the server name that apache is using (www.yourdomain.com) to generate the playlist, but thats another server, so the file cannot be found. If you create a virtual domain and access the mp3's from there then the software will use sme.yourdomain.com to generate the playlist and it will work.

[Dan G.]

Right you are --- it works!

Thanks,

Dan

[Chris Bragg]

OK... I wrestled with this problem for the past couple of days, and I finally fixed it, so I'd like to share with anyone who needs the help how I got past this problem.

First of all, let me just say that I only had this streaming access problem while using the Windows clients on my LAN. My Linux systems using XMMS had no trouble with this at all. (I can hear many of you saying "naturally" right now...) That's how I knew the problem wasn't with the server, but with the client machine, in this case, Windows.

Also, I will tell you that the domain I use for my server is bogus. I only use it on my LAN, not out in the wild. I thought this might be the source of the trouble, but again, my Linux boxes worked OK, so...

In researching the problem, I found that no matter how I logged into the MP3 repository through the browser (either by giving it the IP or the server name), in Windows it always tried to resolve to the bogus domain name. It occurred to me then that Windows 2000 & XP (sorry, I can't vouch for Win9x here)vhave a hosts file just like Linux does. Why couldn't I just put in the IP address of my router twice? Once having a pointer to the hostname of the server, and once having a pointer to www.bogusdomain.com.

I went ahead and ran a search on my WinXP laptop for 'hosts', and it came back with 3 promising files for me. One called 'HOSTS' is in the C:\i386 directory, one called 'hosts' is in the C:\WINDOWS\system32\drivers\etc directory, and the last called 'lmhosts.sam is also in the C:\WINDOWS\system32\drivers\etc directory. So... to each of these files I added in this:

192.168.xxx.xxx        hostname
192.168.xxx.xxx        www.bogusdomain.com

(where xxx.xxx = the last 2 octets of the routers IP address, hostname = the routers hostname, and www.bogusdomain.com = whatever WWW address you have for your router).

Now, I don't know which one of these files did the trick, and I don't really care. All I know is that now streaming audio works on my Windows clients as well as my Linux clients. Sort of sad that Windows requires this much tweaking in order to do the same thing as the Linux boxes, but hey... it worked. Also, if you plan on making your MP3's available over the internet, you'll probably need to come up with a different solution, since you can't likely expect any visitors to your site to edit their hosts files just to stream audio off your site. I'm not concerned with doing that, so my solution works great for me.

I hope this helps someone else get over this roadblock.

Good Luck Everyone!

Chris Bragg

[Dustin Krysak]

I;m running into this exact issue.

so I have the mp3 Ibay created.

then I created a hostname of mp3.mydomain.com and pointed it to my server. (www and others resolve to s different server).

Then I create a virtual domain on my server (mp3.mydomain.com) and point the source to the mp3 ibay.

So now when i access the server http://mp3.mydomain.com/mp3, I should be able to get the playlist to generate with the proper paths -correct?

Well for some reason - the playlist paths still reference the www hostname.

Any ideas?