Some important context - I nuked my appdata share permissions with the New Permissions tool, because I'm an idiot who can't read the warning. Thankfully I had the Appdata Backup plugin, and I deleted the nuked appdata share and repopulated a new one of the same name, to avoid having to chmod 777 the existing share. All is well and good on that front, and I have been able to restore my docker containers without issue.

However I now encounter the issue I described in the title. I do not know if this is caused by my New Permissions fuckup, or something else in my troubleshooting/restore steps. But it coincides perfectly with this disaster, so I assume it is related.

To elaborate, my Unraid server used to show up as a connectable computer called "Tower" in my Windows workgroup (as does my desktop called "North_Breton" in the linked screenshot). This was handy since it meant I did not have to mount every share as a network drive/network location, hence cluttering my file explorer.

It no longer appears in that workgroup area (the "Network" section of the Windows file explorer). However I noticed that for a few seconds after boot, the Unraid "Tower" is briefly visible and accessible, but disappears soon after. I also noticed that while the "Tower" disappears, the server and its SMB shares are still accessible when typing the adress manually in adress bar ( "\\TOWER" or "\\TOWER\appdata\plex" for instance ).

Any ideas on what may cause this, and how to resolve this? Thanks in advance.

Edit: forgot attachment.

Edited October 16, 2025Oct 16 by SinoBreizh

Does it show if you stop the array?

It does indeed! How come?

There's a known issue; it happens to some users, so it's difficult to reproduce. LT is investigating; it may be worth retesting with 7.2.0-rc.2 which should be out soon, since Samba is newer, but you can also just map some network drives.

Glad to hear LT is working on it. For now it isn't the end of the world, since I've been able to pin TOWER to the quick access bar with the array stopped.

So therefore the issue is unrelated to my using New Permissions and Appdata Backup? I very recently updated from 6.12.x to 7.1.4, which would explain why I hadn't had the issue until now. It is very likely that I simply didn't notice the workgroup issue in the new update, until my mistake with New Permissions brought my attention to it.

2 minutes ago, SinoBreizh said:

So therefore the issue is unrelated to my using New Permissions and Appdata Backup?

Shoudl be.

Alright, I'll keep an eye on this in the coming updates. Thanks for your help!

1 hour ago, SinoBreizh said:

Alright, I'll keep an eye on this in the coming updates. Thanks for your help!

Don't try holding your breath until this issue is resolved. As detailed in the post below, it also exists for Windows client/servers in a Windows peer-to-peer network for several years. I feel that MS will have to a player in resolving this...)

https://forums.unraid.net/topic/191221-some-musings-on-smb-and-samba-and-unraid-and-windows/#findComment-1561585