I installed UnRaid 6.11.5 for several months everything works correctly I have only one problem when from Win11 I have to access shared folders. The server is immediately seen when I open the Windows Explorer but to access the folders I have to double click on it for about ten times before it opens. How can I overcome this problem?

 

Any help?

That's a strange one, does it work better if you map a share?

Does it work better if you spin up all the drives (Look on MAIN tab under the Array Operations section for this button) before you open Windows Explorer to access your shares?

 

One other thing to try is set this option for each share in Windows Explorer as shown here:

 

 

You get here by right-clicking on the share and pick Properties from the drop-down list.

 

Also with a share I have same problem:

 

 

 

after some clicks all works:

 

Edited May 24, 20233 yr by Flavio61

Do you have a different computer or even an Android device you could test with?

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.

Try with a different Widows PC to see if it's the same, borrow a notebook from family or a friend if you have to.

 

 

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?

41 minutes ago, Flavio61 said:

Could that be the problem?

Seems unlikely, but no idea what that issue could be since I've never seen anyone else with a similar problem.

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.

Does it wok correctly if you don't have that container running?

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

Look for a support thread/discord for that container:

 

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?

SMB and DNS are two different things.  Start by reading this:

 

        https://learn.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2003/cc737661(v=ws.10)?redirectedfrom=MSDN

and this:

        https://forums.unraid.net/topic/34889-dynamix-v6-plugins/page/44/?tab=comments#comment-462656

 

You can force your Unraid server into becoming the Local Master by adding this to the   SETTINGS   >>>  SMB    >>>  SMB Extras

 

[global]
domain master = no
preferred master = yes
os level = 255

 

It also helps if your Unraid server is on 24-7.    The reason for this is the time it can take to propagate SMB information to all of the clients and servers on your LAN.  (I have the feeling that Windows clients tend to store the information of where to get the table when the client boots up.  If it is always the same computer, things seem to resolve much quicker!  Note in a simple peer-to-peer network---  Which you are running unless you have a Domain Controller ---any SMB client or server on your LAN can be come the Local master!)