Mapped Drive Headaches on new Domain Network

I just added a VM domain controller on my home network. Previously, I had a workgroup network and set up the mapped drives individually on 4 different computers. My goal is to use the domain controller to keep the admin of the mapped drives to a minimum as well as get some experience in domain controller administration. The problem I am having is on one machine, when I go to NETWORK in WINDOWS EXPLORER, I don't see one of the machine I want to access (I can see other other machines on the network). I CAN enter the UNC path manually and then I can see all the shared folders on that machine. However, when I try to click into any of the shares, I get the dreaded "Windows cannot access \\server\share; you do not have permission to access \\server\share". I only have one user account on the domain and that's what all the machines are logged in as and that is the account used in the share permissions.

So, I'm at a loss here. Can't figure out why this computer that is my daily drive can't access the shares but other machines on the network can.

Could it be the problematic machine is v24H2 build 26100.1742 while the other machines are either 23H2 or 21H2?

If you do have Win 34H2 i'm guessing you're on your own.

Have a look in credentials manager and see whats in there associated with the rouge PC, do you have any matching entries in your HOSTS file, do you have static IP's assigned to your PC's??

Ooops! 24H2. LOL!

Yeah, I've spent some time reviewing the credential manager on all machines especially since I've recently renamed the host for each one. Cleared out any old entries. Yes, using static ip's on all machines in question.

Have a look here for changes in 24H2, particularly around SMB (signing, encryption, etc.).

tjubb said:

Ooops! 24H2. LOL!

Yeah, I've spent some time reviewing the credential manager on all machines especially since I've recently renamed the host for each one. Cleared out any old entries. Yes, using static ip's on all machines in question.

Click to expand...

Flushed the DNS?

I think I figured it out. Had to do with folder ownership. Once I tweaked that I was able to access shares again. Nener had to do that before.

Separate question: When I click on NETWORK in EXPLORER why do only some of the machines on the network show up while on my other machine they all appear. I can still access the missing machines in NETWORK by manually enter \\SERVER\share