Non-Domain PC Shared Folder Access?

Marc George 171 Reputation points
2021-09-23T01:26:44.04+00:00

Using the latest versions of Windows 10 and Windows Server 2019, there is no longer access to shared folders on the domain server by the non-domain pc. Is it still possible given the recent changes to both security and SMB? I previously had connections. I still have connections to the folders from domain PC's. I attempting to use the same credentials.

I have verified/modified local policies, shared folder settings, registry settings, SMB settings and folder settings. I am told after attempting and diagnostics that the "device is not setup to accept connections on port... SMB". But if I do a port query of either 139 or 445 they are listening.

Windows Network
Windows Network
Windows: A family of Microsoft operating systems that run across personal computers, tablets, laptops, phones, internet of things devices, self-contained mixed reality headsets, large collaboration screens, and other devices.Network: A group of devices that communicate either wirelessly or via a physical connection.
657 questions
0 comments No comments
{count} votes

3 answers

Sort by: Most helpful
  1. Dave Patrick 426.1K Reputation points MVP
    2021-09-23T01:34:56.627+00:00

    Might check NTLM settings.
    https://learn.microsoft.com/en-us/windows-server/security/kerberos/ntlm-overview

    --please don't forget to upvote and Accept as answer if the reply is helpful--

    0 comments No comments

  2. Marc George 171 Reputation points
    2021-09-23T02:02:37.913+00:00

    @Dave Patrick I agree that authentication is needed, but the PC can map drives of other PC's in the domain with the credentials with no problems, thus its capability to authenticate is present. The problem lies with a domain server that has been functioning as common storage.

    0 comments No comments

  3. Dave Patrick 426.1K Reputation points MVP
    2021-09-23T02:05:24.987+00:00

    agree that authentication is needed

    I made no comment either way on this, just suggested checking the NTLM security settings.

    --please don't forget to upvote and Accept as answer if the reply is helpful--

    0 comments No comments