2 hours ago, JorgeB said:

Did to set the shares to export=yes?

Can't believe it was that simple. Find it odd that the default is hidden.

 

Thanks so much.

9 minutes ago, Ramble5 said:

Find it odd that the default is hidden

It wasn't before, but for security reasons it's been like that since 6.9 or there about.

Hello everyone,

 

I have a weird unraid SMB problem, I think it's related to ipv6 but unsure.

 

Let's say my server name is unraid. If I ping unraid, it answer an ipv6. If I ping with -4 I get the ipv4. In Local Master plugin, it says unraid is the local master browser. In PiHole, I have a entry for unraid and unraid.duckdns.org pointing to it's internal and a cname for unraid => unraid.duckdns.org and unraid.unraid.duckdns.org => unraid.duckdns.org.

 

All ping work properly (even ipv6 although I don't route anything in pfsense).

 

Now, sometime, I can access my samba share using \\unraid. But sometime, this doesn't work and I must use \\unraid.duckdns.org even if both show same ip. I tried rebooting, trying from another computer, checking credential (it's the same as my windows account thus it never ask for user/pass). I'm unsure why it stop using the smbios name and then it force me to use the fqdn.

 

Thank you

On 9/16/2020 at 11:23 AM, UnBeastRaid said:

 

This information is GOLD:

1. Open the registry editor and go to Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters

2. Double-click on AllowInsecureGuestAuth

3. Under "Value data:", change it from 0 to 1 

 

Helped me solve a two week issue trying to access my network shares.

 

Thank you

Tried this. Could not find the 'AllowInsecureGuestAuth:

 

 

8 hours ago, B Train said:

Tried this. Could not find the 'AllowInsecureGuestAuth:

 

Might I suggest that you consider not trying to turn off  SMB security settings.  Instead, setup Unraid and your Windows computers in a secure manner.  It is a bit of a hassle to do the first time but it should only be a one time event.  Basically, what you are trying to do is to run SMB using security features that might have been satisfactory for 2010.  MS occasionally  updates SMB security and its settings in its Monthly updates and these updates can break systems that try to defeat them.

 

See here for how to do this:

 

        https://forums.unraid.net/topic/110580-security-is-not-a-dirty-word-unraid-windows-10-smb-setup/

 

16 hours ago, Frank1940 said:

 

Might I suggest that you consider not trying to turn off  SMB security settings.  Instead, setup Unraid and your Windows computers in a secure manner.  It is a bit of a hassle to do the first time but it should only be a one time event.  Basically, what you are trying to do is to run SMB using security features that might have been satisfactory for 2010.  MS occasionally  updates SMB security and its settings in its Monthly updates and these updates can break systems that try to defeat them.

 

See here for how to do this:

 

        https://forums.unraid.net/topic/110580-security-is-not-a-dirty-word-unraid-windows-10-smb-setup/

 

 

Thanks for responding.

I have tried everything on your forum for the last two weeks.

 

I got UnRaid with the impression that it was the most user friendly program for a 'NAS'.

 

Now I am 60hrs deep into this frustrating rabbit hole and I have no idea where I am going.

I have read the sticky and followed the instruction on my two PCs and laptop to no avail.

 

I am not a computer savvy guy and I cannot even make heads or tails about what is 'SAMBA', '110580', Windows Versions, Registry edits plus all the unraid management mentioned out there.

 

This product is not even remotely user friendly for those using Windows 10 (is that not like 99% of all computer users in the world?). Do I need to be an advanced IT professional to use this stuff? What is your target demographic even?

 

At this point I am trying to figure out if learning to use Ubuntu might yield better results and try to access the Unraid server from there. Any solutions besides using Windows 10 + Unraid are very welcome. I am honestly tired of trying to make this work.

 

Edit: The thread that you are referring me to literally leads me to a PDF that leads me to the same problem I posted about. After following the PDF I am back to the same problem: I cannot double-click on AllowInsecureGuestAuth because it does not exist.

 

What you are suggesting is 'not trying to turn off  SMB security settings'. Does that mean following 'Case 2' or 'Case 3' on pg16 of the paper attached on the thread?

Edited July 24, 20232 yr by B Train

On 10/25/2020 at 11:47 AM, cbr600ds2 said:

I don't have the setting AllowInnsecureGuestAuth.   It won't break if I manually add it in or... I don't want to change to much because it works fine from my laptop.  I just want to be able to do stuff on my new desktop.  Is it because this version of Windows isn't registered (yet?)   

Feedback for those who cannot find ' AllowInnsecureGuestAuth':

You will only find this setting on Windows 10 Pro.

I have no idea how to make it this setting appear or work on Windows 10 Home.

I have this problem every time I reinstall Windows, despite having automated "fixes" like adding the registry entry. What would be REALLY useful would be script to create that Network Neighborhood and do the other fixes. So a Windows 10/11 user can just run it....

 

I've done everything except that so far and nothing works... so Network Neighborhood time for me now.

On 2/3/2024 at 6:38 PM, methanoid said:

I have this problem every time I reinstall Windows, despite having automated "fixes" like adding the registry entry. What would be REALLY useful would be script to create that Network Neighborhood and do the other fixes. So a Windows 10/11 user can just run it....

 

I've done everything except that so far and nothing works... so Network Neighborhood time for me now.

I gave up... Nobody responds in this thread (4 months seems reasonable to wait) and there is no guide or anything from Limetech. I tried many things - so many I have probably buggered up my W10 many times over. I try one at a time and see no change. 

 

Edition    Windows 10 Enterprise LTSC   (because I specifically do NOT want updates that keep breaking stuff)
Version    21H2
OS build    19044.1288

 

And when I loaded Kubuntu up instead, it just connected when I type in the IP address.   Its Windows 10, the most common OS out there and @limetech seem indifferent to helping their users actually USE the product with that most common OS.  

 

Definitely not buying more product with total absence of support except from community (if you are lucky!)

 

 

Maybe cause you used ltsc? Have you tried a non ltsc version? I'm on Windows server 2022 no problem running my security camera. Windows 10 ltsc isn't the most common os, and not its not the same as Windows 10 non ltsc. I work with these daily and they don't behave the same and often drivers too. 

 

Like I have an latitude that if I deploy windows 10 ltsc 2019, only the 2nd driver pack from Dell work. All other result in bsod. But on Windows 10 22h2? No problem. 

 

As for update that keep breaking stuff, just install security only update and that's it. But there's no such thing as update that keep breaking stuff unless your just peeky. Managing over 10 000 critical station all with autoupdate on computer age up to 8 years old and no problem. All on Windows 10 22h2. The other 500 I manage are either on ltsc, 7 or xp (yes xp.........). 

1 hour ago, methanoid said:

I gave up... Nobody responds in this thread (4 months seems reasonable to wait) and there is no guide or anything from Limetech. I tried many things - so many I have probably buggered up my W10 many times over. I try one at a time and see no change. 

 

Edition    Windows 10 Enterprise LTSC   (because I specifically do NOT want updates that keep breaking stuff)
Version    21H2
OS build    19044.1288

 

And when I loaded Kubuntu up instead, it just connected when I type in the IP address.   Its Windows 10, the most common OS out there and @limetech seem indifferent to helping their users actually USE the product with that most common OS.  

 

Definitely not buying more product with total absence of support except from community (if you are lucky!)

 

 

Is tbe script to run on the host or guest, may create a new thread rather than posting on a threac that started in 2016. What does script do?

2 hours ago, SimonF said:

Is tbe script to run on the host or guest, may create a new thread rather than posting on a threac that started in 2016. What does script do?

 

Oh, sorry maybe shouldnt have confused matters mentioning script. I install LTSC from ISO and then run a script that sets all up (installs etc).   Always used to work fine with a small reg file that did the LanmanWorkstation Enable InsecureLogons

Did you try without the script just a plain old barebones install? Did you install the virtuiso for the drivers? 

2 hours ago, methanoid said:

 

Oh, sorry maybe shouldnt have confused matters mentioning script. I install LTSC from ISO and then run a script that sets all up (installs etc).   Always used to work fine with a small reg file that did the LanmanWorkstation Enable InsecureLogons

So do you get an error, but the problem is within the guest?

 

I am unclear what the issue is that needs to be fixed.

Yeah he's good to say support is bad but he's not giving much to help. 

I've found the issue and learned some stuff (this is not a VM but my desktop PC but could not connect to unRAID server)

 

My LTSC ISO was the issue... I downloaded new and older ISOs and they work fine. For LTSC the only fix needed to connect is the LanmanWorkstation fix so easily sorted on each install (and automated too). Suspect that is same for all Enterprise Windows 10.

 

I also tried some plain Win10 Pro ISOs to compare and they don't seem to need ANY fix. Just browse the network and map the drive. 

 

So, strange problem but fixed.   

yup like I said, LTSC aren't the same as 10 Enterprise/Pro/Edu/Home. They are a seperate sku and you can't In-Place upgrade/downgrade to these for multiple reason. 

 

It's still unclear what the issue, you just say stuff about LanmanWorkstation requiring a fix but what is the problem? Cause LanmanWorkstation is for insecure login and this been part of W10 forever. You shouldn't use insecure logins on any share and just map with a user/pass. And when LanmanWorkstation is set to insecure, all encryption are toss out of the window since it doesn't support it. Which mean easy to get any authentication by sniffing the network.

On 7/14/2019 at 12:22 PM, technomancer__ said:

click turn windows features on or of and the add roles and extra features wizard popped up from there i installed the services you suggested and it didn't work (same error) but i had an idea and managed to fix it. if you have this issue just install those services and then go to

control panel/credentials manager

from there click on add a windows credential. now enter your ip or computer name, username, and password and it will work

 

btw if you enter your ip and you try to access from your computer name or vise versa it wont work you have to add the name. (you can add both at the same time)

 

hope this helps someone in the future

This worked for me, thank you!!!

 

starting with the simple solution will fix the problem. I've learned that always revert any settings you change before moving on to the next solution because the solution might not then work.

Heya,

yesterday, i stopped being able to access my unraid shares.

i had the main share i use mapped as a drive to windows but if i click it, windows tells me it can't access the location and to check the network adress

if i access the unraid server base directory, i can access that but none of the configured shares are shown.

accessing the management website and watching stuff via my Emby, that's accessing those exact shares works

i have a user set up on unraid that's allowed to read/write access those shares and have entered that users credentials when mapping the drive

i also found a few threads mentioning to add the user credentials to the Windows credentials to the credential manager, but that changed nothing

i'm on Win11 Pro, Version 24H2, Build 26100.5074
i was on unraid 6.12.something when the issue started, checked the website of mine and saw that there was an update available to 7.1.4, updated to that but nothing about my situation changed

i'd appreciate any advice you got for what else to try to get my access back up

The simplest resolution I have found is to add a line in your hosts file (Windows/system32/drivers/etc/hosts) with the local IP address [Tab] Name of your server

The file has to be edited with administrative privileges (right click on Notepad, run as administrator).

I do not know if syntax and spacing are critical (use spaces instead of tab?). I have multiple VM's that started having issues with accessing the shares. In every case, it was resolved by adding IP address (local) and Name of server in the hosts file. I also have always had a username setup in my Unraid with the same username/password as my Windows credentials.

Hope this helps.

3 hours ago, terag1e said:

The simplest resolution I have found is to add a line in your hosts file (Windows/system32/drivers/etc/hosts) with the local IP address [Tab] Name of your server

The file has to be edited with administrative privileges (right click on Notepad, run as administrator).

I do not know if syntax and spacing are critical (use spaces instead of tab?). I have multiple VM's that started having issues with accessing the shares. In every case, it was resolved by adding IP address (local) and Name of server in the hosts file. I also have always had a username setup in my Unraid with the same username/password as my Windows credentials.

Hope this helps.

worked for me, thanks bud!

this regkey won't work forever. Just use a password like you should instead of using guest share. It's already slated to not be compatible in next version of Windows.

I'm on unraid 7.2.0, Windows 10 and 11 Enterprise edition. On both version, no problem accessing my share. Why? Cause I enter a username and a password that I created, it's that simple. I also created a guest user. Stop using the deprecated and unsecure machine guest passwordless account