HI There

 

After reinstalling windows 11 and trying to access the UNC path for the unraid server it asks for a username and password, I have tried the root username and password but it does not accept it, I am able to access the unraid GUI with the same root username and password.

 

So i just wanted to confirm which username and password i should use to access the UNV path of my server \\servername

 

Regards,

 

Sharkie

Root account is never used for SMB, if the shares are exported publicly, try using just a random user name without a password, like "user", and no pass.

Yes the shares are exported publicly, i did try logging in with user with no password and still no luck,

Then there may be a Windows problem, see if you can access the shares from your phone for example.

How would i access the shares from my phone? i did trying accessing other shares over the network (Another server running windows) and i am able to connect successfully.

9 minutes ago, Sharkie said:

How would i access the shares from my phone?

With a file manager app.

 

9 minutes ago, Sharkie said:

i did trying accessing other shares over the network (Another server running windows) and i am able to connect successfully.

Then the problem is Windows.

So this seems to be the error im receiving:

You can't access this shared folder because your organization's security policies block unauthenticated guest access.

 

 

Take a look at this thread, most common issues are mentioned there:

 

I have tried the below option but does not seem to be working:

 

Directions:

Press the Windows key + R shortcut to open the Run command window.

Type in gpedit.msc and press OK.

Select Computer Configuration -> Administrative Templates -> Network -> Lanman Workstation and double click Enable insecure guest logons and set it to Enabled.

Now attempt to access \\tower

I changed the below setting and the share is accessible now:

 

Security Settings > Local Policies > Security Options

 

In the right pane of Security Options, look for Microsoft network client: Digitally sign communications (always) which might be set to Enabled and this is the cause for this issue. Double click on security setting and on the configuration sheet, set it to Disabled, which is also the default setting. Click Apply, followed by OK.