Windows 10: Windows 10 can see server 2012 shares but refuses access

Discus and support Windows 10 can see server 2012 shares but refuses access in Windows 10 Network and Sharing to solve the problem; Hi Everyone - I've spent several frustrating hours on this problem, and hope by posting to save someone else the grief. Problem: On Windows 10,... Discussion in 'Windows 10 Network and Sharing' started by ChrisNetTech, Apr 5, 2020.

  1. CHRISNETTECH
    ChrisNetTech Win User

    Windows 10 can see server 2012 shares but refuses access


    Hi Everyone -


    I've spent several frustrating hours on this problem, and hope by posting to save someone else the grief.


    Problem: On Windows 10, trying to access some server 2012 shares gives a "you don't have permission...." error. Of course I have triple checked the permissions to the share. The firewall made no difference after I turned it off. The shares are all visible to the W10 machine, just some shares give a permission error, despite correct user permissions.


    I admit I intuited the solution by borrowing an idea from another thread, but the thread was not directly related. Just for the heck of it I tried the following, which makes no sense, but works:


    I edited the hosts file and added an entry for the server. Inexplicably that solved the problem. I was then able to map the drive to the needed share. It already knows where the server is because it can map some folders, not others, and all the shares display properly. Makes no sense, right? Can you say Windows 10? A wild guess is buggy DNS client software.


    Chris

    :)
     
    ChrisNetTech, Apr 5, 2020
    #1
  2. TODD BROWN (TODD.BROWN)
    Todd Brown (todd.brown) Win User

    Windows 10 File Shares not accessible from Server 2012

    Configuration

    Servers:

    • Location 1
      • SCCM-Central1-loc1
        • 2012 R2
        • 10.70.4.228/24
    • Location 2
      • SCCM-DP1-loc2
        • Windows 10 Build 1803
        • 172.22.65.4/24
        • No Symantec Endpoint Protection
      • FILESERVER-FS1-loc2
        • 2012 R2
        • 172.22.65.231/24
    • Location 3
      • SCCM-DP2-loc3
        • Windows 10 Build 1803
        • 172.22.186.4/24
        • Symantec Endpoint Protection
    • Location 4
      • SCCM-DP3-loc4 (Tega)
        • Windows 10 Build 1803
        • 172.22.207.4
        • Symantec Endpoint Protection
        • Citrix Receiver
    • Location 5
      • SCCM-DP4-loc5 (PTZA)
        • Windows 10 Build 1803
        • 172.22.185.4
        • Symantec Endpoint Protection
        • Citrix Receiver


    • We need to be able to attach to the f$ share on each of the “SCCM-DPx-LOCx” servers from the “SCCM-Central1-loc1”.
      • Issue Attempting to connect to
        • \\172.22.65.4\f$
        • \\ SCCM-DP1-loc2\f$
        • \\ SCCM-DP1-loc2.DOMAIN.com\f$
        • \\10.120.186.4\f$
        • \\ SCCM-DP2-loc3\f$
        • \\ SCCM-DP2-loc3. DOMAIN.com\f$
          • Fails from SCCM-Central1-loc1 or any Windows 2012 R2 server outside of the 172.22.65.0/24 subnet.
            • Error:

              Windows cannot access \\ SCCM-DP1-loc2\f$
    Check the spelling of the name. Otherwise, there might be a problem with your network. To try to identify and resolve network problems, click Diagnose.

    See Details shows

    Error Code: 0x80004005

    Unspecified error

    • Works from any Windows 10 workstation even across the VPN. Also works from a Server 2012 R2 server in the 172.22.65.0/24 subnet
    • Works Attempting to connect to
      • \\172.22.65.231\f$
      • \\ FILESERVER-FS1-loc2\f$
      • \\ FILESERVER-FS1-loc2.DOMAIN.com\f$
      • \\ 172.22.207.4\f$
      • \\ SCCM-DP3-loc4\f$
      • \\ SCCM-DP3-loc4. DOMAIN.com\f$
      • \\ 172.22.185.4\f$
      • \\ SCCM-DP3-loc5\f$
      • \\ SCCM-DP3-loc5. DOMAIN.com\f$
        • Works from all locations and all machines
    • Notes:
      • Connecting from any Windows 10 machine to the failing systems works every time (see above).
      • Connecting to a Windows 2012 R2 server in the same subnet as one of the failing systems works every time.
      • Auditing of ports from any location to the systems in this subnet renders the same result:
    Test-NetConnection -port 138 -ComputerName "FILESERVER-FS1-loc2" -InformationLevel "Detailed"

    WARNING: TCP connect to FILESERVER-FS1-loc2:138 failed

    ComputerName : FILESERVER-FS1-loc2

    RemoteAddress : 172.22.65.231

    RemotePort : 138

    AllNameResolutionResults : 172.22.65.231

    MatchingIPsecRules :

    NetworkIsolationContext : Private Network

    IsAdmin : False

    InterfaceAlias : Ethernet

    SourceAddress : 10.70.4.228

    NetRoute (NextHop) : 10.70.4.1

    PingSucceeded : True

    PingReplyDetails (RTT) : 39 ms

    TcpTestSucceeded : False

    Test-NetConnection -port 137 -ComputerName "FILESERVER-FS1-loc2" -InformationLevel "Detailed"

    WARNING: TCP connect to FILESERVER-FS1-loc2:137 failed

    ComputerName : FILESERVER-FS1-loc2

    RemoteAddress : 172.22.65.231

    RemotePort : 137

    AllNameResolutionResults : 172.22.65.231

    MatchingIPsecRules :

    NetworkIsolationContext : Private Network

    IsAdmin : False

    InterfaceAlias : Ethernet

    SourceAddress : 10.70.4.228

    NetRoute (NextHop) : 10.70.4.1

    PingSucceeded : True

    PingReplyDetails (RTT) : 39 ms

    TcpTestSucceeded : False

    Test-NetConnection -port 139 -ComputerName "FILESERVER-FS1-loc2" -InformationLevel "Detailed"

    ComputerName : FILESERVER-FS1-loc2

    RemoteAddress : 172.22.65.231

    RemotePort : 139

    AllNameResolutionResults : 172.22.65.231

    MatchingIPsecRules :

    NetworkIsolationContext : Private Network

    IsAdmin : False

    InterfaceAlias : Ethernet

    SourceAddress : 10.70.4.228

    NetRoute (NextHop) : 10.70.4.1

    PingSucceeded : True

    PingReplyDetails (RTT) : 39 ms

    TcpTestSucceeded : True

    Test-NetConnection -port 445 -ComputerName "FILESERVER-FS1-loc2" -InformationLevel "Detailed"

    ComputerName : FILESERVER-FS1-loc2

    RemoteAddress : 172.22.65.231

    RemotePort : 445

    AllNameResolutionResults : 172.22.65.231

    MatchingIPsecRules :

    NetworkIsolationContext : Private Network

    IsAdmin : False

    InterfaceAlias : Ethernet

    SourceAddress : 10.70.4.228

    NetRoute (NextHop) : 10.70.4.1

    PingSucceeded : True

    PingReplyDetails (RTT) : 39 ms

    TcpTestSucceeded : True

    • Attempted Fixes
      • NSLOOKUP does find the systems
      • Creating a non-Admin share was no different
      • Turning off IPv6 was no help
      • Turning on SMB file sharing did not help
      • Checked and the OS firewall for Domain, Private, Guest or Public, all are off
      • Removing the SCCM-DP1-loc2 from the domain then will respond with a prompting for username and password, but still does not allow login and eventually fails with the same error.
        • Error:

          Windows cannot access \\ SCCM-DP1-loc2\f$
    Check the spelling of the name. Otherwise, there might be a problem with your network. To try to identify and resolve network problems, click Diagnose.

    See Details shows

    Error Code: 0x80004005

    Unspecified error

    • Disabled SMB2/3 and this still fails
    • Verified that SMB1 is present
    Get-WindowsOptionalFeature -Online -FeatureName SMB1Protocol

    FeatureName : SMB1Protocol

    DisplayName : SMB 1.0/CIFS File Sharing Support

    Description : Support for the SMB 1.0/CIFS file sharing protocol, and the Computer Browser protocol.

    RestartRequired : Possible

    State : Enabled
     
    Todd Brown (todd.brown), Apr 5, 2020
    #2
  3. WASTEDSLAYER
    Wastedslayer Win User
    Server 2012

    IF you want to try seizing the FSMO roles to see if it will help, here is a quick guide (this should be done on the DC you want to keep):

    https://blogs.technet.microsoft.com...ation-master-roles-in-windows-server-2012-r2/

    Knowing that this is a DC now I'm really convinced that something is wrong with the AD account for this particular server. It's possible that the promotion to a DC didn't work correctly leaving you with a sort of broken DC.

    A reboot is always worth a shot; has that been tried Ahhzz? If it has, then the next step would be to demote this DC and rejoin it to the domain. Once rejoined you can run DCPromo again. Microsoft best practice is to have at least 2 DCs for redundancy.
     
    Wastedslayer, Apr 5, 2020
    #3
  4. DJRABES
    djrabes Win User

    Windows 10 can see server 2012 shares but refuses access

    Server 2012

    Also don't forget to reset the account in AD Users and Computers to avoid any SID issues.
     
    djrabes, Apr 5, 2020
    #4
Thema:

Windows 10 can see server 2012 shares but refuses access

Loading...

  1. Windows 10 can see server 2012 shares but refuses access - Similar Threads - server 2012 shares

  2. Server 2012 R2 File sharing help

    in Windows 10 Gaming
    Server 2012 R2 File sharing help: I have a dell R320 server running windows server 2012 R2 standard. How do i get windows 10/11 to find it. I went into features and enabled smb 1.0/cifs file sharing support. I tried to setup ftp file sharing but that didn't work so i deleted the ftp server. But windows 10/11...

  3. Server 2012 R2 File sharing help

    in Windows 10 Software and Apps
    Server 2012 R2 File sharing help: I have a dell R320 server running windows server 2012 R2 standard. How do i get windows 10/11 to find it. I went into features and enabled smb 1.0/cifs file sharing support. I tried to setup ftp file sharing but that didn't work so i deleted the ftp server. But windows 10/11...

  4. Can access shared folder but cannot see it in "network:"

    in Windows 10 Software and Apps
    Can access shared folder but cannot see it in "network:": This is the title of a 2018 "locked" question.I found this thread trying to search for my 2nd pc's network that gives me much trouble. I could no really find the solution. I can see my 2 pc under network / view tab, but my new and second pc called 'Desktop-blabla20' not real...

  5. Can access shared folder but cannot see it in "network:"

    in Windows 10 Network and Sharing
    Can access shared folder but cannot see it in "network:": This is the title of a 2018 "locked" question.I found this thread trying to search for my 2nd pc's network that gives me much trouble. I could no really find the solution. I can see my 2 pc under network / view tab, but my new and second pc called 'Desktop-blabla20' not real...

  6. Windows 10 file share access to Server 2012-2019 fails with Access Violation.

    in Windows 10 Network and Sharing
    Windows 10 file share access to Server 2012-2019 fails with Access Violation.: I have read many of the postings on Win10 and issues with file shares. My issues are as follows: I have Server 2012/2012R2 and 2019 2019 being evaluated Non-Domain Local User account setup: UserTest tested as local user and administrator levels Shared a test folder on each...

  7. Windows 10 compatibility with Server 2012

    in Cortana
    Windows 10 compatibility with Server 2012: Hello, At the company I work for, we recently started upgrading our computers from Windows 7 to Windows 10. However, many of the Windows 10 features stop working once I add the PC to the domain. Start Menu, Cortana, the search field next to the start button, and all the...

  8. Installing printer driver # Access Denied – print share server 2012 for some users

    in Windows 10 Drivers and Hardware
    Installing printer driver # Access Denied – print share server 2012 for some users: Greetings Microsoft Support, We installed new print servers 2012 and they are running Safecom G4. They used to be on server 2008. Problem at the moment : Some users are experiencing “access denied error” when trying to connect to the Safecom pull print share...

  9. can't access Shared folders on windows server 2012

    in Windows 10 Network and Sharing
    can't access Shared folders on windows server 2012: I make a driver(F:) on our company's windows server2012 pc as shared folder, and in the [advanced security setting] of F driver, I set the shared feature to <Everyone>, and set the authority to groups and some users(with password) premiusly created. The server's address...

  10. Windows 10 File Shares not accessible from Server 2012

    in Windows 10 Network and Sharing
    Windows 10 File Shares not accessible from Server 2012: We have a newly imaged Windows 10 box that we will be using as an SCCM DP. Currently the Central server cannot access the file shares on the Windows 10 box, after digging deeper we have found that other Windows 10 boxes can hit file shares on it, but Server 2012 R2 systems...