streaming issues Pi/samba
by timl from LinuxQuestions.org on (#5T26E)
Hi, I did touch on this yesterday and I don't want to reopen the same thread. This is yesterdays:
https://www.linuxquestions.org/quest...ue-4175704896/
I am trying to play audio/watch videos.
The source files live on a Centos box. This uses samba to share the files
VLC runs on a Raspberry Pi 4
This problem in intermittent. I made a change yesterday which appears to have fixed the problem but it is back with a vengeance. The samba server was set up about 18 months ago. The Pi was set up about 6 months ago so they have both ticked along for a while.
The problem is that I can't play an mp3 file. Last night I watched a 30 minute video (the night before it wasn't working) today I can't listen to an audio file - it cuts out sporadically and resumes.
On the Pi journalctl shows nothing - only that I hve connected via SSH
The centos box is a little more forthcoming:
Quote:
that is about the time I began to run VLC on the Pi and therefore access samba but that message recurs. I did some digging and there was nothing conclusive. Basically my searches suggested my Pi has 2 interfaces (it hasn't - I use the internal wifi).
Hmmm, as I write that I had a thought: 192.168.1.1 is the main router. Both these boxes run though a powerline adapter connected to this router. Wondering whether this becomes a network issue. I would have thought that messages do not need to go back to the main router and should be dealt ith on the adapter
FWIW I shall include my minimal SMB.CONF if anyone has any suggestions (I am using the private share):
Quote:
If anyone gets time it would be good to get feedback
Regards
https://www.linuxquestions.org/quest...ue-4175704896/
I am trying to play audio/watch videos.
The source files live on a Centos box. This uses samba to share the files
VLC runs on a Raspberry Pi 4
This problem in intermittent. I made a change yesterday which appears to have fixed the problem but it is back with a vengeance. The samba server was set up about 18 months ago. The Pi was set up about 6 months ago so they have both ticked along for a while.
The problem is that I can't play an mp3 file. Last night I watched a 30 minute video (the night before it wasn't working) today I can't listen to an audio file - it cuts out sporadically and resumes.
On the Pi journalctl shows nothing - only that I hve connected via SSH
The centos box is a little more forthcoming:
Quote:
Dec 15 12:51:43 Bellona nmbd[1314]: [2021/12/15 12:51:43.722255, 0] ../../source3/nmbd/nmbd_namequery.c:109(query_name_response) Dec 15 12:51:43 Bellona nmbd[1314]: query_name_response: Multiple (2) responses received for a query on subnet 192.168.1.62 for name WORKGROUP<1d>. Dec 15 12:51:43 Bellona nmbd[1314]: This response was from IP 192.168.1.1, reporting an IP address of 192.168.1.1. Dec 15 12:56:46 Bellona nmbd[1314]: [2021/12/15 12:56:46.580489, 0] ../../source3/nmbd/nmbd_namequery.c:109(query_name_response) Dec 15 12:56:46 Bellona nmbd[1314]: query_name_response: Multiple (2) responses received for a query on subnet 192.168.1.62 for name WORKGROUP<1d>. Dec 15 12:56:46 Bellona nmbd[1314]: This response was from IP 192.168.1.1, reporting an IP address of 192.168.1.1. |
Hmmm, as I write that I had a thought: 192.168.1.1 is the main router. Both these boxes run though a powerline adapter connected to this router. Wondering whether this becomes a network issue. I would have thought that messages do not need to go back to the main router and should be dealt ith on the adapter
FWIW I shall include my minimal SMB.CONF if anyone has any suggestions (I am using the private share):
Quote:
[tim@Bellona ~]$ cat /etc/samba/smb.conf [global] workgroup = WORKGROUP server string = Samba Server %v netbios name = samba-server security = user map to guest = bad user dns proxy = no [Public] path = /samba/share/public browsable =yes writable = yes guest ok = yes read only = no [Private] path = /samba/share/private valid users = @private guest ok = no writable = yes browsable = yes |
Regards