For Private it's Local Subnet, so if you're having this issue not on a domain you may need to add any additional subnets to the scope for SMB-In, NB-Datagram-In, NB-Name-In, and NB-Session-In.Ģ) What was most befuddling was that the firewall seemed to inconsistently block the connection to the mapped drive. The default behavior for a domain connection for most of the File & Printer Sharing rules is 'Any' for Remote IPs. Both systems are part of a domain.ġ) The suggestion above about changing the scope on the SMB-In rule ended up not mattering.
To add a bit more information, I tested this out on two workstations with the latest version of Windows 10 (Build 1909). I wanted to share what I found in case anyone else runs into this issue.
Ok, so I ended up figuring this issue out after a spending a lot of time testing things out.
