SMB shared path issue

Everyone is not always "everyone".

If the user on the client PC is logged in with a local account, then the server cannot authenticate it unless you have defined a local account with the same name and password on the server.

On the client PC, open a command prompt and run "net view". If the account can be authenticated, then you should see SHR2 listed.

net view \\ServerName

If "net view" works, then you likely have a permissions problem on either the share or the folder. This script will report on shares.

# Script: SharePermissionsSimple.ps1
# Author: MotoX80 on Learn.Microsoft.com forums
cls
Get-SmbShare | Where-Object -Property Name -NotLike '*$' | foreach {        # exclude hidden and administrative shares
    write-host -ForegroundColor Blue "----------------------------------------------------------------"
	"             {0}"  -f $_.Name  | write-host -ForegroundColor Yellow 
    write-host -ForegroundColor Blue "----------------------------------------------------------------"
	
	"Share permissions for {0}." -f $_.Name
    $_ | Get-SmbShareAccess | Format-Table -Property AccountName, AccessControlType, AccessRight
    ""
    "NTFS folder permissions on {0}." -f $_.Path
    (Get-Acl -Path $_.Path ).Access | foreach {
        [pscustomobject] @{
            IdentityReference = $_.IdentityReference
            Type = $_.AccessControlType
            Inherit = $_.IsInherited
            Rights = ($_.FileSystemRights.tostring().replace(", Synchronize","").replace("-536805376","Modify (Inherit Only)"))
        }
    } | Format-Table   -AutoSize
} 

If "net view" fails, then check the Security eventlog on the server and look for logon failures.

You might want to explain what user accounts you have defined, how your users authenticate, and what security requirement you have. Does this server host a domain (Active Directory)?

hi Scott Huang,
Error 0x80004005 with SMB shares is often caused by permissions, firewall settings, or SMB authentication issues rather than the New-SmbShare command itself.

A few things to verify:

Get-SmbShare
Get-SmbServerConfiguration

Also check:

The folder C:\shr2 actually exists.

NTFS permissions on the folder allow access.

File and Printer Sharing is enabled in Windows Firewall.

SMB services are running:

Get-Service LanmanServer

Try accessing the share locally first:

\\localhost\shr2

If localhost works but remote access fails, it is likely:

firewall,

network profile,

or SMB authentication related.

Also ensure the server network profile is set to:

• Private or Domain not Public.
  If my answer is useful for you, please hit Accept the answer to support me.

Thank you so much,

Hi Scott,

The error you’re seeing (0x80004005) usually indicates that the SMB share was created but cannot be accessed due to either permissions or name resolution. In your PowerShell command, the -readaccess "ryone" looks like a typo — it should be a valid local or domain account (for example, Everyone). If the account name is invalid, the share is created but access fails. Also confirm that the folder C:\shr2 actually exists and that NTFS permissions allow the connecting user to read or write as intended; SMB share permissions alone are not sufficient if NTFS denies access.

On Windows Server 2025, make sure the “File and Printer Sharing” inbound firewall rule is enabled, and that the SMB protocol is not blocked. Test connectivity by running \\servername\shr2 from a client, ensuring the server name resolves correctly in DNS. If you want anonymous access, explicitly grant Everyone read access both at the share and NTFS level. If you intend to restrict it, use proper domain accounts instead of local placeholders.

In short, correct the access parameter to a valid identity, verify NTFS permissions on C:\shr2, and ensure the firewall allows SMB. Once those are aligned, the share will be accessible without the 0x80004005 error.

If the above response helps answer your question, please hit "Accept Answer" so that others in the community facing similar issues can easily find the solution. Your contribution is highly appreciated.

Harry.