Forum

Unable to Access Ne...
 
Notifications
Clear all

Unable to Access Network Shares In Windows 10

4 Posts
2 Users
0 Reactions
67 Views
Posts: 3
Topic starter
(@erdinc)
Active Member
Joined: 1 month ago

I'm experimenting with Rasberry Pi5 and OpenMediaVault, I've set up a NAS with 4 X 4TB SSD drives. The SSD drives are combined in one (snapraid) pool. I have multiple laptops and desktops all on the Windows 10 operating system. The machines running Windows 10 full version have no problem accessing the network drive. But on the machines running Windows 10 Tiny 21H2 the network drive is visible but access is denied. All the machines are visible to each other and can access each other's drive. On the machines running on Windows 10 Tiny I'm logged in with a local account, not with my Microsoft account.

1723657080-LENOVO.jpg
3 Replies
eTechniz
Posts: 36
(@etechniz)
Trusted Member
Joined: 4 months ago
  1. Enable Network Discovery and File Sharing:

    • Go to Settings > Network & Internet > Status > Network and Sharing Center.
    • Click on Change advanced sharing settings.
    • Ensure that Turn on network discovery and Turn on file and printer sharing are selected.
  2. Check Network Credentials:

    • Make sure that the local account you're using on Windows 10 Tiny has the necessary permissions to access the shared folders.
    • You might need to enter the credentials of an account that has access to the shared folders.
  3. Enable Insecure Guest Logons:

    • Press W+R , type gpedit.msc and press Enter to open the Group Policy Editor.
    • Navigate to Computer Configuration > Administrative Templates > Network > Lanman Workstation.
    • Double-click on Enable insecure guest logons and set it to Enabled.
  4. Check SMB Protocols:

    • Ensure that SMB 1.0/CIFS File Sharing Support is enabled.
    • Go to Control Panel > Programs > Turn Windows features on or off.
    • Check the box for SMB 1.0/CIFS File Sharing Support and click OK.
  5. Run the Shared Folder Troubleshooter:

    • Go to Settings > Update & Security > Troubleshoot > Additional Troubleshooting.
    • Select Shared Folders and run the troubleshooter.
Reply
Posts: 3
Topic starter
(@erdinc)
Active Member
Joined: 1 month ago

Hello eTechniz

 

First of all thanks for replying, the basic steps you've mentioned are the first steps I've tried with no luck.

The computers that cannot access the NAS sharing, can access each others drive, so network discovery is not the issue.

However, when I navigated to Lanman Workstation to Enable insecure guest logons, my computer gave a lot of error messages and froze up for a few minutes.

- I've checked services, all the services needed are set to automatic.

- Local Policies - Security Options is set to Send LM & NTLM-use NTLMv2 session security if negotiated.

- On the Advanced TCP/IP settings windows, “WINS” tab, NetBIOS over TCP/IP is enabled.

- HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSLicensing hardwareID and Store keys are deleted.

- 4(TCP/IPv4) Reliable multi-cast protocol is installed.

 

These are all the steps I've checked but still no luck.

Still get Error Code: 0x80070035 when I try to access the NAS drive.

 

I have 2 laptops and 3 desktops, they are all visible to each other and can access each other's shared drives without any problem.

 

With 1 laptop and 1 desktop (running on windows 10 pro full version) I can access the NAS drive.

With the other laptop and 2 desktops (running on windows 10 Tiny IoT Enterprise LTSC , 21H2) is the NAS drive visible but I get the Error code 0x80070035.

I've tried to login with my Microsoft account instead of my local account on the Tiny machines, also no luck

 

I hope now you've got a bit more info,

 

Kind regards,

 

Erdinç

Reply
Posts: 3
Topic starter
(@erdinc)
Active Member
Joined: 1 month ago

My best guess is to reinstall the normal windows 10 on the machines running windows Tiny.

I really do like the Tiny version without all the usual, unnecessary bloatware!

And my machines are quite old. I've upgraded the RAM and installed SSD drives to speed them up but still.. Tey run much smoother without all the extra's.

The downside is that I'm probably also missing some of the key features needed.

Reply
Share: