The issues you're experiencing with accessing shared folders across your network may be related to changes introduced in Windows updates, particularly with the handling of SMB (Server Message Block) shares. The update KB5068861 may have affected how guest and user access is managed, especially with the introduction of stricter security measures in newer versions of Windows.
Here are a few steps you can take to troubleshoot and potentially resolve the issue:
- Check Network Discovery and File Sharing Settings: Ensure that network discovery and file sharing are enabled on all computers. You can do this by going to Control Panel > Network and Sharing Center > Change advanced sharing settings and ensuring that both options are turned on for your network profile.
- Review Sharing Permissions: Double-check the sharing permissions on CompA and CompC. Make sure that the folders are shared correctly and that the permissions allow access for the users you intend. You might want to remove and re-add the shares to refresh the settings.
- Enable Insecure Guest Logons: If you are using guest accounts, you may need to enable insecure guest logons. This can be done through the Local Group Policy Editor or by modifying the registry. Note that enabling this can pose security risks, so consider it carefully.
- Check SMB Settings: Ensure that SMB1 is enabled if required, as some older systems may still rely on it. However, be cautious as SMB1 is deprecated due to security vulnerabilities. You can check this in Control Panel > Programs > Turn Windows features on or off.
- Firewall Settings: Check the firewall settings on CompC to ensure that it is not blocking file sharing. You may need to create exceptions for file sharing in the firewall settings.
- Reboot and Update: Sometimes, simply rebooting the machines can resolve connectivity issues. Also, ensure that all machines are fully updated with the latest patches and updates from Microsoft.
If these steps do not resolve the issue, you may want to look into the specific changes made by KB5068861 and consider rolling back the update if necessary, although this should be a last resort.
References: