Windows Cannot Access Unraid Server HELP!

[UnBeastRaid]

Hello, thanks for reading into my issue...it is driving me insane.

 

I have just built my Unraid server and finished the parity overnight.

This morning, I created a share and wanted to test my 10gigabit connection, however, windows has another agenda.

The share that I created via Unraid GUI is a media share and settings were default with public access.

The first time I tried accessing the Unraid server, windows prompted me with acces denied and asked for my server credential for "root"  user. I entered credentials but no  luck. I resorted to "more" credential option and logged in as guest user with "admin" as user and no password.

 

When I am in the Unraid network folder in windows and I try and access my media share, I get this error:

 

My network settings:

 

My default gateway address: 192.168.1.1

My UnraidBeast address: 192.168.1.17

 

I have exhausted all options and super frustrated. Any help would be much appreciated.

 

-Thanks

 

unraidbeast-diagnostics-20200915-0807.zip

[UnBeastRaid]

I have already checked for laman workstation configuration and it was already enabled by default.

 

still no luck

[trurl]

 

[UnBeastRaid]

Well...I have exhausted all measures that were at my disposal to try and figure this out. I have had zero luck of getting the below error message to go away.

 

I have tried everything in this thread:

https://answers.microsoft.com/en-us/windows/forum/windows_10-networking/connecting-pcs-users-for-sharing-xp-vista-7-8-10/fb92e439-5dbc-4367-9857-1ef360e9ffdf

 

And this thread:

https://answers.microsoft.com/en-us/windows/forum/all/no-longer-able-to-access-network-shares-after-1809/5ddbb386-5768-4f57-9c60-2b55055fcb08

 

Not sure what else I can do to solve this issue. Has anyone been able to recover from this error?

 

Thanks

[Frank1940]

OK first thing, is your Unraid server the Local Master? 

 

What happens when you enter the following on the Address bar on Windows Explorer (Window s file manger)?

\\192.168.1.17

Di you look at the Link that @trurl provided in his post above?  Read the first couple of pages and make sure you try those suggestions in your setup.  Then go to the last page and work backwards. 

 

SMB problems are seldom ever simple to troubleshoot and fix.  As I have mentioned many times, SMB is more like witchcraft than science....

[UnBeastRaid]

Hey Frank, thanks for your reply. See below

 

Local Master info:

 

inputing \\192.168.1.17 in file explorer brings up the same error message.

 

I did look at @trurl link provided above and tried many options. I will give it another stab and see what happens.

 

This witchcraft is driving me insane. I should mention that I have zero issues accessing my Unraid server from my Mac device. Completely simple plug and play. I wish windows would fix this.

 

-Thanks

[Frank1940]

Make sure you have these settings:

and

and the last one

Note each setting before you change them.  Later if you want to tighten security up you can go back and do so one at a time.   I know it looks like some of these only apply to the client PC but it seems  like some of them also apply to any client/server you try to access.

 

[UnBeastRaid]

I have confirmed that all settings listed above is what I have set in my client, however, the access error is still persistent.

[Frank1940]

Start at the last page of the Unraid Forum thread and work your way backwards.  I am assuming this is not a company issued computer that might have some Corporation IT group policies enforced...

[UnBeastRaid]

I will try the @trurl thread again. That's correct, not an issued computer.

Thanks for your help Frank. I'll keep you posted in this thread.

Edited September 16, 2020 by UnBeastRaid

[Frank1940]

One more thing you can try.  There is a program you can run on your Windows computer that will scan the SMB network and show what your PC is 'seeing' is on it.  You can find it by goggling:

LANscanner v2.02

The name of the website is  Scottie's Tech.INFO    As with all Internet downloads use due diligence on checking things out. 

 

The output will look like this:

[UnBeastRaid]

Lo and BEHOLD.

 

I am not sure how I missed this amazing piece of information, but I am glad I caught it.

 

This is what solved my issue:

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