UnraidC

Just some feedback from a very recent new user of Unraid. I have been mostly happy with the experience up to now. In theory legacy users will not be affected (not that I put any money on "Trust me bro" statements right after previous model turnarounds, but that is a different matter), but I care about more than just myself when I am going around recommending stuff to people as I have been doing with Unraid since I started with it a few weeks ago. It is your product and you are free to do with it what you want, obviously. I am not coming at this from any "moral" perspective or anything like that. At the same time, your end user does not care about your internal issues and cost structures (at least not the new ones signing up). That does not mean that I do not get the need for recurring income, but there are other models for doing so that are also proven in the market and that I personally find more palatable (e.g. paid business support, saying this as a business owner by the way who would potentially end up paying such support). The reality is that without security updates (as confirmed in the FAQ) you are de facto turning it into a subscription model for an internet-connected server system. You can twist and turn about that as much as you want, but the twisting and turning about it is perhaps the most offputting element of this to me to be honest, more than the model change itself. At least don't insult people's intelligence, I believe my own lying eyes and cannot be convinced that gravity does not affect me while observing that objectively it does. If this had been announced a few weeks ago in this manner I would have never gotten into Unraid, and I will also not be recommending it anymore to others. A friend of mine just received his server hardware on my recommendation but I told him to look elsewhere after reading this. That at least is 1 lost customer, nearly 2 if I had known before (but of course I myself will ride it out now with the legacy license while it lasts). In any case, it completely shifts the USP and perception of the product and the company, and for sure made the alternatives much more attractive. I am purely from a business perspective very curious to see what this will lead to in the mid to long run, fully assuming you know best how to run your own company even though from my own perspective I raised an eyebrow and shook my head at the course you are pursuing here.

Unfortunately the problem came back a few days later now: again got the "check spelling" error... Really don't know what to do anymore. Any help or thoughts would be appreciated

I'm hesitant to say it but for the past 2 days the issue seems to have improved (watch it going wrong tomorrow of course). I am not sure what made the difference, but I think it may have been putting every exported file to "Yes" now and no more "Yes - hidden" Was not able to set up the Network Neighborhood with any results. Will see how it goes and report back if anything changes. Thanks for the suggestions, fingers crossed that it remains stable...

I tried that in my earlier post but would get the same "check spelling" error in the end. As you say, the internet solutions do not seem to be working... What a mess indeed, was hoping for a smoother experience when I got started with Unraid

I think the instructions skip a step because when just creating a Network Neighborhood folder on my desktop it does not become shared? I am indeed working from the Admin account of the windows desktop.

Quick question on the Network Neighborhood instructions: The Network Neighborhood folder I created per the instructions is not automatically shared like shown in the sceenshot in the "Unraid & Windows 10 SMB Setup" pdf referred to above. When I click the Share button in the Properties/Share tab of my Network Neighborhood folder, it says: After a while, I get this message: No idea what the problem would be. To circumvent this, I click Advanced Sharing then I can tick a box to "share this folder": This then results in the folder appearing to be shared like in the "Unraid & Windows 10 SMB Setup" pdf: I then copy the blacked out network path (which refers to the folder on the desktop). Following that, I try to add the network location as instructed, resulting in this: So that does not seem to solve things

OK, I will give it a try and report back. Yes, aside from the recurring reboots sometimes to try and get the shares to show up again up to now (hopefully resolved at some point and then in theory to stay on permanently). This is a tricky one given my use case and circumstances, will try the Network Neighbourhood first - fingers crossed. Thanks for your time and assistance!

Both desktop and server have wifi turned off and running on an ethernet lan connection. No but I thought that was only necessary when you don't have this view automatically (from the "Unraid & Windows 10 SMB setup" PDF referenced earlier in this thread): Under Network, I can see the Unraid server when it works (like ELSIE1 in the example screenshot above, but with my own unraid server name), but often after waking dekstop from sleep it is not there anymore. All of the shares have been added individually as network locations, as well as the unraid server itself. But I have done it directly and not in a separate "Network Neighbourhood" folder, is there any reason why adding the extra step of a folder would change anything you think? Yes when it works I can access the server via Windows Explorer. The problem is that often it does not show up under Network, thus not allowing me to access the shares from Windows Explorer (not from the "Network" view like in the screenshot above, not from the mapped drives under This PC and not from the quick access links referring to them). Originally I was only using the server name. Because of the issues I experienced I also tried to use the IP, but the issue persists ("check spelling" error and not seeing the server nor the shares in windows explorer when waking desktop from sleep). I have not noticed any differences whether or not I am connecting through IP or server name, nor with having only 1 or multiple credentials (i.e. only or both based on name and IP) set up. All the drives were added as a network location individually and afterwards those netword locations were pinned to quick access as well (i.e. the experienced issue is not due to typo's). Curious about your thoughts!

Given the context the server is intended to be used in I do not want other people on the network to be able to put something onto a public share, (i.e. all exported shares must be private for my use case). As such I did not have any public shares set up. Even so, I added one just now to see if it makes any difference going forward (but would not want one structurally). Will report back on this later if this would solve anything.

Yes, I had several shares as export "Yes - Hidden". Based on your post I changed all exported shares to just "Yes" now, but this did not change anything: after desktop went to sleep and logging back on I again got the "check spelling" error. Re: case sensitivity: my shares are structured like this for example: 1. Documents 2. Images I.e. a digit followed by a dot and a space followed by a capitalized word. Do you think that is causing issues?

Hello, Apologies for the delayed reply, have been completely swamped by work the past few days but still very eager to follow up on this I am trusting your expertise over mine, so diagnostics attached below: [diagnostics file removed] Additional information re: desktop: Windows 11 Pro Version 22H2 (when checking for updates it says everything is up to date). I have followed all the guides mentioned above I believe (private network, credentials set up (originally for only the name, then also for the IP - sometimes the IP one works when the name one does not, but almost always when 1 has the issue the other gets the "check spelling" error as well), set up network drives, no insecure guest logons, SMB 1.0 turned off in Windows Features - screenshots in OP). The desktop does not share any folders (only Unraid exports shares, all private). Would be great if you would be willing to have a look - thank you in advance!

Edit: diagnostics added in a post below.

Edit: diagnostics added in a post below.

Edit: what seems to have stabilized things a bit is not using the shares export option "Yes-Hidden" anymore, but using only "Yes" or "No". Edit: turns out a few days later that the problem occurred again, to my despair Any help or thoughts would be appreciated. Hello, Context: Have set up Unraid server, which is the most IT-technical project I have ever done - my professional expertise lies elsewhere but I am eagerly trying to learn. Docker containers etc. work fine, up to now have always been able to access webgui's so that has not been an issue (yet). The problem I am running into is that often I cannot access the shares through my Windows Explorer. It is very inconsistent, sometimes I can, sometimes I cannot (e.g. after a reboot of pc, or of Unraid, or most often after pc went to sleep, etc.). The "solution" is then to reboot the desktop and/or unraid (sometimes several times) but it is a hassle and cannot be the intended way of working. The error message that I get is Windows cannot access "server name" and to "check the spelling". At that stage the server is also not detectable in the network. It basically makes the Unraid server unusable for the purpose it was intended when I cannot consistently access the shares through windows explorer... I have tried everything I could find online I think, sometimes based on posts of several years ago, but the problem remains so I now landed at the point of complete desperation after having wasted a lot of frustration and hours of very scarce free time on this. I hope something positive can still be salvaged from it with the help from people here who know better. The current situation is as follows: Router set to allocate a fixed local IP address to the Unraid server. In Unraid itself the IPv4 address assignment is set to automatic and it picks up the IP address allocated to it by the router (edit: afterwards have also tried changing it to static with the same router allocated IP while also still letting the router allocate the IP, but does not seem to change anything either way). I can also access all webgui's of Unraid itself and various dockers through this address using the assigned ports. Note: before this I set only a static address in Unraid itself (the same one as now is allocated by the router) and did not have the router assign it, this made no difference (in fact I hoped setting the IP address in the router vs in Unraid would fix things). SMB setting as follows based on some forum posts I found. Note the extra configuration settings, which originally only consisted of the first line (ntlm auth = yes). Whether these settings are here in full, only the first line or nothing at all does not seem to affect anything. All shares are private like this (sometimes export = "yes" and sometimes "yes (hidden)". I always refer to user 1 credentials. Insecure guest logins have been disabled under local group policy editor / local computer policy / computer configuration / administrative templates / network / lanman workstation. Under credential manager in windows the user 1 credentials have been added and allow me to access the shares when they sometimes show up. This is what shows up in the log. Please feel free to request any necessary info I possibly forgot to include here and I will adjust this post accordingly. Any and all help would be welcome and very much appreciated, I genuinely gave it my best try based on the information I was able to piece together from various online sources before bothering people with it here. I hope I did not bite off more than I can chew and end up having wasted my time and money on this but it is looking bleak Thank you so much for having a look!