WIndows 10 cant connect to/from network shares

network-sharesnetworkingwindows 10

Problem:

I am unable to connect to/from Windows 7, Mac PCs and Raspberry PIs (Samba Shares on Raspbian) connected via LAN (via 2 dumb Netgear switches). I can ping in both directions without problems. FTP also works. It's just accessing shares in both direction. I can even connect from my PC to another e.g. Win7 PC but it shows no shares. Connecting to hidden share C$ also doesn't work.

Background:

I have multiple networks: USB-LTE (primary internet connection), LAN cable (has internet connectivity but I don't use it), VPN (Cisco to work) and 2x Hyper-V Virtual adapters for Hyper-V VMs (usually not running). I use "route add/delete" to set metrics of each connection to set priority, otherwise Windows sets the default metric of my LAN cable as higher priority even though my LTE connection is 20x faster to the internet. Windows Firewall is deactivated and I use NetLimiter for blocking connections. This setup has worked in Windows 7 for many years and with Windows 10 everything worked until about 1 year ago (I don't remember exactly when, nor did I pay attention to which updates might have caused it). I have tried numerous instructions from various forums and none of the solutions has provided any help. The latest recommended solution to similar issues was to ensure that Peer Networking Grouping service is enabled. Currently the service is set to Manual and won't start, giving the error "Error 1068: The dependency service or group failed to start." – the dependency being Peer Networking Identity Manager service, which also won't start due to "Access Denied". I am unable to determine why, in EventViewer it just says error 5 with no other details.

Further research suggested that I should delete "C:\Windows\ServiceProfiles\LocalService\AppData\Roaming\PeerNetworking\idstore.sst" which I did, as well as all other idstore.* files in this directory. Note: I could not access ServiceProfiles or any directory thereafter without confirming a warning to allow access, since I did not already have permission. After deleting all idstore.* files and rebooting, I still have no network connectivity and I am still unable to start both Peer Networking services.

Other ideas I have tried:

  • enabled the Windows Feature SMB 1.0/CIFS Client as well as SMB Direct

  • setting Peer Networking Identity Manager "Log On" value to Local System account, apply, then set back to "Local Service" (with empty password)

  • sfc /scannow

  • dism /online /cleanup-image /scanhealth

Network and Sharing Center:

  • HomeGroup > Create a homegroup:

enter image description here

Network and Sharing Center toggles (tried both settings in all cases):

  • Private: Turn on/off network discovery

  • Private: Turn on/off file and printer sharing

  • Private: Allow Windows to manage homegroup connections / Use user accounts and passwords to connect to other computers

  • Guest/Public: Turn on/off network discovery

  • Guest/Public: Turn on/off file and printer sharing

  • All Networks: Turn on/off sharing so anyone with network access can read and write files in the Public Folders

  • All Networks: Use 128-bit encryption/Enable file sharing for devices that use 40- or 56-bit encryption

  • All Networks: Turn on/off password protected sharing

  • Start the HomeGroup troubleshooter > Troubleshoot network problems > "Troubleshooting couldn't identify the problem"

  • Start the HomeGroup troubleshooter > Skip This Step > "Troubleshooting couldn't identify the problem"

  • Enable Homegroup Listener and Homegroup Provider services

EDIT:

  • disabled all NetLimiter 4 features and disabled system service

Best Answer

You want to make sure the samba server is running SMB v3 or higher. This allows modern versions of Windows to access the server. Homegroup is not going to solve your problem.

Related Question