Various folder/file sharing has been configured on some devices on a local network and the sharing was working up until about 2 weeks ago. "Out-of-the-blue" I found that a desktop share was no longer available to a tablet. On checking the devices and shares, it was found the desktop could still access all the other devices but none of the other devices could access the desktop anymore. Here is a list of the devices on the local network: Windows 11 Pro 25H2 desktop (with Norton Internet Security) Windows 11 Pro 24H2 laptop ("the laptop") (with Norton Internet Security) Ubuntu 24.04.3 LTS laptop Samsung Galaxy A56 phone Samsung Galaxy Tab S7 tablet Here is the folder/file sharing setup: The desktop and the laptop have folder and file sharing enabled, with Network Discovery, on a Private network. SMB1 was/is disabled on both the desktop and laptop. The same local admin user is setup on both the desktop and the laptop, with saved Windows Credentials. The below shares were setup, with Full Control: Private folder on the desktop Private folder on the laptop ALL of the above shares were working perfectly as follows: The desktop had a network location configured to the laptop (required credentials to initially login). The laptop had a network location configured to the desktop (required credentials to initially login). The Ubuntu laptop could access the desktop share (with credentials login). The Ubuntu laptop could access the laptop share (with credentials login). The phone could access the desktop share (with credentials login). The phone could access the laptop share (with credentials login). The tablet could access the desktop share (with credentials login). The tablet could access the laptop share (with credentials login). Now the desktop share doesn't work from other devices (i.e. 2, 3, 5 & 7). I've searched for a solutions via Google, and used ChatGPT/CoPilot, and tried just about everything suggested, except for registry edits or enabling guest login (I don't believe this should be necessary to solve something that was working and will reduce security) and solutions for duplicated computer ID's (I don't believe this is relevant in my case). I didn't keep an exhaustive list of everything I found and tried but here is a list: All devices can be ping'd from each other using either the device name or IP address. Even though no changes were made to Windows folder and file sharing settings, these were checked and devices were rebooted (sharing on, private network, network discovery on, etc). Temporarily enabled SMB1. Temporarily disable Norton firewall. Remove desktop network location on the laptop and setup new network location using device name or IP address; failed: "The folder you entered does not appear to be valid". Tried to map a network drive on the laptop to the desktop share using device name or IP address; failed: "Windows cannot access ____. Check the spelling of the name. Otherwise there might be a problem with your network. Error code: 0x80070043, The network name cannot be found". Removed saved Windows Credentials on the laptop and retried accessing the desktop share; failed. Created a new local admin user on the desktop, setup a Full Control share on a folder and tried to access that from the laptop; failed. Tried RDP from the laptop to the desktop (failed). Checked that SMB2 is enabled on both the desktop and the laptop (via Powershell). Any help on solving this will be greatly appreciated. Gnugs • 45 Reputation points 2025-11-26T16:22:50.09+00:00 @Grant: Look at https://www.askwoody.com/forums/topic/september-2025-updates-are-out/#post-2808935 1 comment Show comments for this answer Grant Kerr • 0 Reputation points 2025-11-26T19:31:39.99+00:00 Thanks @Gnugs . I had a look but the 445 port is already open on the firewall 0 votes Sign in to comment Add comment @Grant: Look at https://www.askwoody.com/forums/topic/september-2025-updates-are-out/#post-2808935 Grant Kerr • 0 Reputation points 2025-11-26T19:31:39.99+00:00 Thanks @Gnugs . I had a look but the 445 port is already open on the firewall 0 votes Thanks @Gnugs . I had a look but the 445 port is already open on the firewall JC • 8,235 Reputation points • Independent Advisor 2025-11-20T17:05:54.8+00:00 Hello, Could it be that the network needs an ip address refresh for the devices? I’ve had this happen to me one time, everything was fine then one day my main pc was inaccessible through local network. Try running these commands in cmd. ipconfig /release, press Enter, then type ipconfig /renew It worked for me at the time, hope it works for you on your end, JC 5 comments Show comments for this answer Grant Kerr • 0 Reputation points 2025-11-20T18:19:33.35+00:00 Hi, Thanks for the suggestion but unfortunately no change. 0 votes JC • 8,235 Reputation points • Independent Advisor 2025-11-20T20:50:52.73+00:00 After looking for more nonstandard troubleshooting steps I was able to find this. Check services. Open services.msc via the run function with windows+$. Scroll down to Function Discovery Provider and Function Discovery Resources. Make sure both are running. Make sure both are set to auto start. 0 votes Grant Kerr • 0 Reputation points 2025-11-20T22:44:58.4666667+00:00 Although both these services were set to auto start, when I checked them, the Function Discovery Provider Host wasn't running but the Function Discovery Resource Publication was running. Both have been set to Automatic (Delayed Start) and were start manually. The desktop was then rebooted and the services are now running automatically, even after a reboot. However the share connection is still not working.Interestingly, the desktop is not shown on the laptop's Network. But I did come across a post that mentioned that if these services are stopped and restarted after a reboot, that the device will appear in the Network of other devices, which is what happens with my devices. But the share still doesn't connect :( 0 votes JC • 8,235 Reputation points • Independent Advisor 2025-11-21T15:42:00.2266667+00:00 I'm still looking for more troubleshooting steps but these options are a bit more drastic, one post in the forums said they created local accounts for all the devices in their network but that's not worth the hassle, after all our troubleshooting steps I'd suggest using a workaround for the one pc by maybe using an SFTP app or having the network invisible pc folder access to the other devices. 0 votes Grant Kerr • 0 Reputation points 2025-11-25T12:35:07.4533333+00:00 For security reasons and to get Windows local network sharing to work (which in my opinion is far more difficult than it show be, thanks Mr Vendor), there are local accounts for the relevant users setup on the Windows computers on the network already and this is how it was working before "this bug". At the moment, I've got a work around for one of the more critical issues, which is sync'ing certain business folders and files between the desktop and the laptop, which is necessary for when I work remotely or go to clients. Previously the sync was run on the laptop, which would access the desktop, and update the folders/files. Since this is now broken, the folder/file sync is now initiated from the desktop, which can still access the laptop. This work around might be short lived though, because it is possible that the same thing that caused the issue on the desktop will occur on the laptop as well, especially if its Windows 11 updates. Thanks for the suggestion for work arounds, which I'll investigate further. However, at the end of the day, this should work the way it used to. 0 votes Sign in to comment Add comment Could it be that the network needs an ip address refresh for the devices? I’ve had this happen to me one time, everything was fine then one day my main pc was inaccessible through local network. Try running these commands in cmd. ipconfig /release, press Enter, then type ipconfig /renew It worked for me at the time, hope it works for you on your end, Grant Kerr • 0 Reputation points 2025-11-20T18:19:33.35+00:00 Hi, Thanks for the suggestion but unfortunately no change. 0 votes Thanks for the suggestion but unfortunately no change.

JC • 8,235 Reputation points • Independent Advisor 2025-11-20T20:50:52.73+00:00 After looking for more nonstandard troubleshooting steps I was able to find this. Check services. Open services.msc via the run function with windows+$. Scroll down to Function Discovery Provider and Function Discovery Resources. Make sure both are running. Make sure both are set to auto start. 0 votes After looking for more nonstandard troubleshooting steps I was able to find this. Check services. Open services.msc via the run function with windows+$. Scroll down to Function Discovery Provider and Function Discovery Resources. Make sure both are running. Make sure both are set to auto start. Grant Kerr • 0 Reputation points 2025-11-20T22:44:58.4666667+00:00 Although both these services were set to auto start, when I checked them, the Function Discovery Provider Host wasn't running but the Function Discovery Resource Publication was running. Both have been set to Automatic (Delayed Start) and were start manually. The desktop was then rebooted and the services are now running automatically, even after a reboot. However the share connection is still not working.Interestingly, the desktop is not shown on the laptop's Network. But I did come across a post that mentioned that if these services are stopped and restarted after a reboot, that the device will appear in the Network of other devices, which is what happens with my devices. But the share still doesn't connect :( 0 votes Although both these services were set to auto start, when I checked them, the Function Discovery Provider Host wasn't running but the Function Discovery Resource Publication was running. Both have been set to Automatic (Delayed Start) and were start manually. The desktop was then rebooted and the services are now running automatically, even after a reboot. However the share connection is still not working.Interestingly, the desktop is not shown on the laptop's Network. But I did come across a post that mentioned that if these services are stopped and restarted after a reboot, that the device will appear in the Network of other devices, which is what happens with my devices. But the share still doesn't connect :( JC • 8,235 Reputation points • Independent Advisor 2025-11-21T15:42:00.2266667+00:00 I'm still looking for more troubleshooting steps but these options are a bit more drastic, one post in the forums said they created local accounts for all the devices in their network but that's not worth the hassle, after all our troubleshooting steps I'd suggest using a workaround for the one pc by maybe using an SFTP app or having the network invisible pc folder access to the other devices. 0 votes I'm still looking for more troubleshooting steps but these options are a bit more drastic, one post in the forums said they created local accounts for all the devices in their network but that's not worth the hassle, after all our troubleshooting steps I'd suggest using a workaround for the one pc by maybe using an SFTP app or having the network invisible pc folder access to the other devices. Grant Kerr • 0 Reputation points 2025-11-25T12:35:07.4533333+00:00 For security reasons and to get Windows local network sharing to work (which in my opinion is far more difficult than it show be, thanks Mr Vendor), there are local accounts for the relevant users setup on the Windows computers on the network already and this is how it was working before "this bug". At the moment, I've got a work around for one of the more critical issues, which is sync'ing certain business folders and files between the desktop and the laptop, which is necessary for when I work remotely or go to clients. Previously the sync was run on the laptop, which would access the desktop, and update the folders/files. Since this is now broken, the folder/file sync is now initiated from the desktop, which can still access the laptop. This work around might be short lived though, because it is possible that the same thing that caused the issue on the desktop will occur on the laptop as well, especially if its Windows 11 updates. Thanks for the suggestion for work arounds, which I'll investigate further. However, at the end of the day, this should work the way it used to. 0 votes For security reasons and to get Windows local network sharing to work (which in my opinion is far more difficult than it show be, thanks Mr Vendor), there are local accounts for the relevant users setup on the Windows computers on the network already and this is how it was working before "this bug". At the moment, I've got a work around for one of the more critical issues, which is sync'ing certain business folders and files between the desktop and the laptop, which is necessary for when I work remotely or go to clients. Previously the sync was run on the laptop, which would access the desktop, and update the folders/files. Since this is now broken, the folder/file sync is now initiated from the desktop, which can still access the laptop. This work around might be short lived though, because it is possible that the same thing that caused the issue on the desktop will occur on the laptop as well, especially if its Windows 11 updates. Thanks for the suggestion for work arounds, which I'll investigate further. However, at the end of the day, this should work the way it used to. AI answer 2025-11-20T14:16:12.32+00:00 It seems that you are experiencing issues with accessing shared folders on your Windows 11 Pro desktop from other devices on your local network. Here are some troubleshooting steps you can consider: Check Network Sharing Settings : Ensure that file and printer sharing is turned on for your network. You can do this by navigating to the Control Panel, then to the Network and Sharing Center, and checking the advanced sharing settings. Make sure that both file sharing and network discovery are enabled. Verify SMB Configuration : Since SMB1 is disabled, ensure that SMB2 or SMB3 is enabled on both the desktop and laptop. You can check this using PowerShell with the command Get-SmbClientConfiguration and Get-SmbServerConfiguration . Check Firewall Settings : Since you have Norton Internet Security, ensure that it is not blocking SMB traffic. You may need to create exceptions for file sharing or temporarily disable the firewall to test connectivity. Review User Permissions : Double-check the permissions on the shared folders to ensure that the user accounts have the necessary access rights. You can do this by right-clicking the folder, selecting Properties, and then checking the Sharing and Security tabs. Network Profile : Confirm that your network is set to Private and not Public, as this can affect sharing settings. Event Viewer Logs : Check the Windows Event Viewer for any security or access-related errors that might indicate why access is being denied. Look under Windows Logs > Security for any relevant entries. Use the IP Address : When trying to access the share, use the IP address of the desktop instead of the device name to rule out any name resolution issues. Reset Network Settings : If all else fails, consider resetting the network settings on the desktop. This can sometimes resolve underlying issues that may not be immediately apparent. If after trying these steps the issue persists, it may be beneficial to check for any recent updates or changes to your network configuration that could have affected the sharing capabilities. References: Set up your small business network Access Denied when you access an SMB file share in Windows AI-generated content may be incorrect. Read our transparency notes for more information. It seems that you are experiencing issues with accessing shared folders on your Windows 11 Pro desktop from other devices on your local network. Here are some troubleshooting steps you can consider: Check Network Sharing Settings : Ensure that file and printer sharing is turned on for your network. You can do this by navigating to the Control Panel, then to the Network and Sharing Center, and checking the advanced sharing settings. Make sure that both file sharing and network discovery are enabled. Verify SMB Configuration : Since SMB1 is disabled, ensure that SMB2 or SMB3 is enabled on both the desktop and laptop. You can check this using PowerShell with the command Get-SmbClientConfiguration and Get-SmbServerConfiguration . Check Firewall Settings : Since you have Norton Internet Security, ensure that it is not blocking SMB traffic. You may need to create exceptions for file sharing or temporarily disable the firewall to test connectivity. Review User Permissions : Double-check the permissions on the shared folders to ensure that the user accounts have the necessary access rights. You can do this by right-clicking the folder, selecting Properties, and then checking the Sharing and Security tabs. Network Profile : Confirm that your network is set to Private and not Public, as this can affect sharing settings. Event Viewer Logs : Check the Windows Event Viewer for any security or access-related errors that might indicate why access is being denied. Look under Windows Logs > Security for any relevant entries. Use the IP Address : When trying to access the share, use the IP address of the desktop instead of the device name to rule out any name resolution issues. Reset Network Settings : If all else fails, consider resetting the network settings on the desktop. This can sometimes resolve underlying issues that may not be immediately apparent. If after trying these steps the issue persists, it may be beneficial to check for any recent updates or changes to your network configuration that could have affected the sharing capabilities. Set up your small business network Access Denied when you access an SMB file share in Windows Waseem Khan • 5 Reputation points 2025-11-24T19:35:26.79+00:00 I had been facing the same problem since I started using Windows 11, and despite a lot of research, nor any websites, even microsoft fourms, neither any AI generated response could come up with a correct and useful solution. So I decided to keep trying different things on my own and ultimately found a surprisingly easy solution!! I hope this will help a lot of people onwards, as I can see that many people as of today are still stuck with this situation without any way out. The very simple solution is below: ** For advanced users:** You just have to give permission to "Guest" account when sharing the folder in first place. While mapping the shared folder as network drive on the other pc, where it asks authentication and gives error, just enter user name as "guest" and leave the password blank. The folder will be mapped as a drive which you can access now! If any basic user needs to know detailed procedure of above 2 steps, only then you read below text, otherwise skip this as you're already done!! For Basic users: Right click the folder you want to share on the source computer, come on "M ore options ">, " Give access to "> " Specific people ". A Dialog box "Network Access" will open. There, in the drop down list you select " Guest " and click " Add " button beside it. Click " Share " button and then " Done ". That's it! Now you go on the other computer from where you want to access this shared folder. In Windows Explorer, go on " This PC ". Select 3 dots *** for options in the horizontal menu-bar and select " Map Network Drive ". There you enter the path of shared folder e.g. \pcname\sharedfoldername\ (replacing this with actual computer name and actual shared folder name). All the best!! 5 comments Show comments for this answer Grant Kerr • 0 Reputation points 2025-11-25T12:23:27.2433333+00:00 Thank you for the reply and suggestion. However, this is a business's network and accessing shares must be done using authentication. 0 votes Gnugs • 45 Reputation points 2025-11-26T03:00:34.9066667+00:00 @Grant: I commiserate. Have tried just about everything with 4 win11 pro Pcs on a private network. Have the similar (same?) problem. Pc A can get to Pc B and Pc C but not to the shares (OR Remote Desktop) on Pc D. Annoyingly, Pc D can get to all the other Pcs INCLUDING Pc A. Pc B and Pc C can get to all the others as well. I've tried to get to MS techs to help but the only time I got through the call "cut off." MS support is almost impossible to get to anymore so I'm pretty much in the same boat. By the way, I went through all the suggestions everyone has for permissions, credentials, fussing with credentials, etc., etc. The nearest I got to anything helpful was a note on the web somewhere about MS improving system robustness (whatever that means) in some of their later updates and that there might be some problems with older Pcs. But no solution was given and like I said I haven't been able to get through to MS to discuss it. Good luck. 0 votes Gnugs • 45 Reputation points 2025-11-26T03:05:10.69+00:00 Authentication is also required on a private network to access shares. This problem is not reserved just for business networks. It's been referred to elsewhere. 0 votes Grant Kerr • 0 Reputation points 2025-11-26T04:51:25.08+00:00 @Gnugs the MS Tech experience sounds familiar... Have you tried rolling back updates on the problematic PC's? This is my next step 0 votes Gnugs • 45 Reputation points 2025-11-26T05:18:44.4333333+00:00 @Grant: The last time I tried to do that, I had to reinstall two systems. There is a reference somewhere in the web about an update that could cause that. But that update was so far out-of-date that I decided not to try it and I can't even remember the KB number. Good luck if you find and try. If I ever get through to MS, I'll get back to you with the response. 0 votes Sign in to comment Add comment I had been facing the same problem since I started using Windows 11, and despite a lot of research, nor any websites, even microsoft fourms, neither any AI generated response could come up with a correct and useful solution. So I decided to keep trying different things on my own and ultimately found a surprisingly easy solution!! I hope this will help a lot of people onwards, as I can see that many people as of today are still stuck with this situation without any way out. The very simple solution is below: ** For advanced users:** You just have to give permission to "Guest" account when sharing the folder in first place. While mapping the shared folder as network drive on the other pc, where it asks authentication and gives error, just enter user name as "guest" and leave the password blank. The folder will be mapped as a drive which you can access now! If any basic user needs to know detailed procedure of above 2 steps, only then you read below text, otherwise skip this as you're already done!! For Basic users: Right click the folder you want to share on the source computer, come on "M ore options ">, " Give access to "> " Specific people ". A Dialog box "Network Access" will open. There, in the drop down list you select " Guest " and click " Add " button beside it. Click " Share " button and then " Done ". That's it! Now you go on the other computer from where you want to access this shared folder. In Windows Explorer, go on " This PC ". Select 3 dots *** for options in the horizontal menu-bar and select " Map Network Drive ". There you enter the path of shared folder e.g. \pcname\sharedfoldername\ (replacing this with actual computer name and actual shared folder name). Grant Kerr • 0 Reputation points 2025-11-25T12:23:27.2433333+00:00 Thank you for the reply and suggestion. However, this is a business's network and accessing shares must be done using authentication. 0 votes Thank you for the reply and suggestion. However, this is a business's network and accessing shares must be done using authentication. Gnugs • 45 Reputation points 2025-11-26T03:00:34.9066667+00:00 @Grant: I commiserate. Have tried just about everything with 4 win11 pro Pcs on a private network. Have the similar (same?) problem. Pc A can get to Pc B and Pc C but not to the shares (OR Remote Desktop) on Pc D. Annoyingly, Pc D can get to all the other Pcs INCLUDING Pc A. Pc B and Pc C can get to all the others as well. I've tried to get to MS techs to help but the only time I got through the call "cut off." MS support is almost impossible to get to anymore so I'm pretty much in the same boat. By the way, I went through all the suggestions everyone has for permissions, credentials, fussing with credentials, etc., etc. The nearest I got to anything helpful was a note on the web somewhere about MS improving system robustness (whatever that means) in some of their later updates and that there might be some problems with older Pcs. But no solution was given and like I said I haven't been able to get through to MS to discuss it. Good luck. 0 votes @Grant: I commiserate. Have tried just about everything with 4 win11 pro Pcs on a private network. Have the similar (same?) problem. Pc A can get to Pc B and Pc C but not to the shares (OR Remote Desktop) on Pc D. Annoyingly, Pc D can get to all the other Pcs INCLUDING Pc A. Pc B and Pc C can get to all the others as well. I've tried to get to MS techs to help but the only time I got through the call "cut off." MS support is almost impossible to get to anymore so I'm pretty much in the same boat. By the way, I went through all the suggestions everyone has for permissions, credentials, fussing with credentials, etc., etc. The nearest I got to anything helpful was a note on the web somewhere about MS improving system robustness (whatever that means) in some of their later updates and that there might be some problems with older Pcs. But no solution was given and like I said I haven't been able to get through to MS to discuss it. Good luck. Gnugs • 45 Reputation points 2025-11-26T03:05:10.69+00:00 Authentication is also required on a private network to access shares. This problem is not reserved just for business networks. It's been referred to elsewhere. 0 votes Authentication is also required on a private network to access shares. This problem is not reserved just for business networks. It's been referred to elsewhere. Grant Kerr • 0 Reputation points 2025-11-26T04:51:25.08+00:00 @Gnugs the MS Tech experience sounds familiar... Have you tried rolling back updates on the problematic PC's? This is my next step 0 votes @Gnugs the MS Tech experience sounds familiar... Have you tried rolling back updates on the problematic PC's? This is my next step Gnugs • 45 Reputation points 2025-11-26T05:18:44.4333333+00:00 @Grant: The last time I tried to do that, I had to reinstall two systems. There is a reference somewhere in the web about an update that could cause that. But that update was so far out-of-date that I decided not to try it and I can't even remember the KB number. Good luck if you find and try. If I ever get through to MS, I'll get back to you with the response. 0 votes @Grant: The last time I tried to do that, I had to reinstall two systems. There is a reference somewhere in the web about an update that could cause that. But that update was so far out-of-date that I decided not to try it and I can't even remember the KB number. Good luck if you find and try. If I ever get through to MS, I'll get back to you with the response.