this doesnt sound like a samba problem.
I have noticed equal failures with playing mp3,
in my case i notice that if a connect is interupted , by what failure ever ( switch network etc ) the player stops playing mp3.
For playing mp3 on a 24 hour i would recommend to use linux
and store the mp3 direct on the playing machine.
( using mp3blaster console , or many other ) maybe a nfs mount would do it better.
Using real mp3 streaming may also help you out, cause in streaming the
player caches the sound ,so small interupts are not from interest.
Perhaps you should upgrade you samba version
for suse new samba bins are here
for 8.1
ftp://ftp.suse.com/pub/projects/samba/3.0/i386/8.1/
there are many other possibilities which will work also
what you want
http://www.ampache.org/
http://www.shoutcast.com/
http://www.turnstyle.com/andromeda/
http://www.videolan.org/
http://ffmpeg.sourceforge.net/
switching to reiser may also help
at last you should upgrade to suse 9.1 and samba 3.06
for many security reasons, also check your cabeling and hubs switches
For win xp i cant say the behavior playing mps from a samba share is really different depending on the player ( winamp, media play etc )
so changing the player may help too.
turning on log level high will show you more info in your current setup.
Best Regards
Chris Roubekas schrieb:
Dear all,
I have a SuSE 8.1 Installation running on a box and
mixed windows versions on clients doing domain loggons
etc on the SuSE8.1 box (I have activated Samba on it
and all works just fine!).
One of them has Win2K and it is running a software that plays
MP3s from the SuSE server on a 24hour basis (that is non-stop).
For the past few months, the Win2K client will show an
unexpected error stating :"There is a problem on your hard disk
or the network" which causes all MP3 playing to cease. At that point, I have to terminate the program and restart it
so it can continue. This doesn't make any sense since
all other clients on the network can play those mp3s without
any problems, however they do not play on a 24hour basis.
I have checked for bad clusters etc on the SuSE machine, none
found. I have checked the MP3s which caused the system to stop
but they are absolutely fine and I can play them on any other PC
including the one that stopped!!
In addition, whenever something like this happens, I get the following error in the /var/log/messages log file:
Jul 20 18:01:41 mp3 smbd-classic[18241]: [2004/07/20 18:01:41, 0] lib/util_sock.c:read_data(436) Jul 20 18:01:41 mp3 smbd-classic[18241]: read_data: read failure for 4. Error = Connection reset by peer
Also I do not seem to get any errors in the /var/log/samba/log.smb or log/nmb files which I wonder why....
I have tried to figure out what the hell that error means and I cannot find anything for the life of me!!!
I even changed my network cards on both (client and server) still nothing! The error continues to appear on the client and the server. It does not appear on a periodic interval (i.e. every 6 hours or something like that) so I cannot seem to trace it in any way!!!! I even re-installed my entire SuSE from scratch and fully patched it from fou4s and still no results! The only thing that I have not done yet is to upgrade it to Samba 3 (in case the Samba-Team has fixed something like this for which I have no idea since I am a very new linux user).
Please, please, please help me with this one! It is driving me absolutely CRAZY!!!!
Thank you in advance for your time and effort
Kind Regards, Chris
PS : The client that has these problems is running Windows 2000 SP:2.
-- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
