Flavio61

On my server I have a share where I store all the .mkv files of my movies. To watch the movies I use the Zidoo UHD8000 player. The share is open and public with both NFS and SMB. With NFS I can reach the share from the player but on UHD files the playback sometimes freezes. Zidoo support suggested I try SMB sharing. I tried to access via SMB from the Zidoo to the Unraid server but I can't and I keep getting an incorrect credentials error. From Windows PCs I have no problem accessing the same share. What can I check?

Hi, I have been using this docker for a long time without any problems to create .mkv files. Lately I tried to use the 'Backup' function of MakeMKV to have the complete rip of the disk. Everything works but, unlike what happens with .mkv files, the folder that it creates with the rip of the entire disk is not modifiable, not moveable as if an additional permission was needed to work with the folder. The path that I use for ripping is always the same one that I use for .mkv files, in the docker settings I have not changed anything. What can I do? Thanks.

I installed the docker but when I go to the WebUi I have a ERR_CONNECTION_REFUSED. Where I'm wrong?

I thought this too but Zidoo's assistance insists that there is a need for more bandwidth. Is there a method to increase the available bandwidth without changing hardware? Maybe some parameter of my configuration limits the bandwidth but I'm not expert enough to verify it.

Given that my UnRaid system is mainly used to host .mkv files from my DVD and Bluray collection, I recently purchased a new network player (Zidoo UHD8000) and I am having trouble playing 4K files. The player freezes every now and then, remains frozen for two or three seconds and then resumes playing. I sent an email to Zidoo support and they replied that the player requires more bandwidth on the network. My configuration is on the attach image. With the previous player on the same network I did not have this problem but Zidoo support insists that their player needs more bandwidth. When I transfer files from my PC to the UnRaid server on the same network the transfer is done at a speed of 105/110 MBs. What can I do to have more bandwidth on the network?

I'm resuming this discussion because the problem that seemed to be solved by disabling Roon's docker actually always comes up again. Now I've done some tests and I've found that if instead of double-clicking on the Unraid server icon I use the network path with the IP address, the folders all open on the first attempt without problems. So I guess it's DNS issues, I've checked on our DNS server and everything seems fine the entry for the UnRaid server is there and the IP address is properly logged. What can I do?

Yes, with the Roon docker down everything seems to work. But I have no idea how to fix when the docker is active.

n my Windows PC I have problems accessing Unraid server shares, often to be able to access the shares I have to click several times on the server icon before it opens. Investigating the problem I noticed that if instead of using the name of the server (Tower) I use the IP address this opens immediately. In the Unraid server log I found this warning: "WARNING: Detected another IPv4 mDNS stack running on this host. This makes mDNS unreliable and is thus not recommended." lsof -i -P -n | grep 5353 and I have this reply: avahi-dae 15225 avahi 14u IPv4 3572990 0t0 UDP *:5353 RoonAppli 20514 root 280u IPv4 1883480 0t0 UDP *:5353 RoonAppli 20514 root 282u IPv4 1883482 0t0 UDP *:5353 RoonAppli 20514 root 284u IPv4 1883484 0t0 UDP *:5353 It therefore seems that Roon's docker creates an incompatibility with avahi's mDNS. Unfortunately I am not so experienced as to understand how to solve this problem. Any help? Thank you.- Edited 3 hours ago by Flavio61

I think the problem is in the mDNS because I noticed that if I enter the server with its IP address (\\192.168.100.7) the shares open immediately on the first attempt. I tried this command found on the net: lsof -i -P -n | grep 5353 and I have this reply avahi-dae 15225 avahi 14u IPv4 3572990 0t0 UDP *:5353 RoonAppli 20514 root 280u IPv4 1883480 0t0 UDP *:5353 RoonAppli 20514 root 282u IPv4 1883482 0t0 UDP *:5353 RoonAppli 20514 root 284u IPv4 1883484 0t0 UDP *:5353 It therefore seems that Roon's docker creates an incompatibility with avahi's mDNS. Unfortunately I am not so experienced as to understand how to solve this problem. Any help? Thank you.

On my Windows PC I have problems accessing Unraid server shares, often to be able to access the shares I have to click several times on the server icon before it opens. Investigating the problem I noticed that if instead of using the name of the server (Tower) I use the IP address this opens immediately. In the Unraid server log I found this warning: "WARNING: Detected another IPv4 mDNS stack running on this host. This makes mDNS unreliable and is thus not recommended." lsof -i -P -n | grep 5353 and I have this reply: avahi-dae 15225 avahi 14u IPv4 3572990 0t0 UDP *:5353 RoonAppli 20514 root 280u IPv4 1883480 0t0 UDP *:5353 RoonAppli 20514 root 282u IPv4 1883482 0t0 UDP *:5353 RoonAppli 20514 root 284u IPv4 1883484 0t0 UDP *:5353 It therefore seems that Roon's docker creates an incompatibility with avahi's mDNS. Unfortunately I am not so experienced as to understand how to solve this problem. Any help? Thank you.-

From different PC is the same. In the Syslog the only warning that I read is: Sep 30 11:34:42 Tower avahi-daemon[15225]: *** WARNING: Detected another IPv4 mDNS stack running on this host. This makes mDNS unreliable and is thus not recommended. *** Could that be the problem?

I am resuming this discussion because Unraid share connection issues are not resolved. I always have the problem from Windows where I have to click several times on shares to be able to open them. I tried from an Android device to access Unraid nfs shares and nothing opens. Any suggestions? Thank you.

Same problem for me too

Also with a share I have same problem: after some clicks all works:

Any help?