Forum Discussion

Guide

Jul 02, 2020

Solved

Error: 0x80004002 accessing NSA

Okay, here's my problem (yes, I know my NAS is old, but it works great for me): I just upgraded my daughter's system - fresh install of Windows 10 Home 64bit, version 1909. At this time SMB 1 is enab...

oldfart825
Jul 03, 2020
Okay... I unenabled both NetBIOS over TCP/IP and SMB1, restarted pc, re-enabled both again, and added the address and device name into the Hosts file. Restarted pc. No change. Looks like the only way is through the net use command, and that will have to work for now. Just an incentive to replace the NAS as soon as I can.

Thanks everyone for the help! If anyone has any other suggestions I'm certainly open to them.

oldfart825

Guide

Jul 04, 2020

The network neighborhood I don't know about. I don't use a workgroup or anything, and the NAS still doesn't show up in Explorer under Computers in the right pane, or under Network as it does on mine. It only shows up in Storage in the right pane.

oldfart825

Guide

Jul 04, 2020

Oh, and using \\nas-host-name does work.

Sandshark
Sensei
Jul 04, 2020
Right-click on "This Computer" and select "Properties". On that pop-up, it will list the workgroup. If that is different on the two computers, then that's the likely issue with it not appearing in Network. "Change Settings" on that same pop-up will allow you to change it.

But the problem of not being able to easilly access it without resorting to using the HOSTS files is something that has evaded many, myself included. You see postings all over about Linux SMB and Windows having this issue in come cases (Not just ReadyNAS and often not all computers on the same network), and Microsoft just gives their usual "try this" crap that works for nobody and ultimately takes no responsibility.
oldfart825
Guide
Jul 05, 2020
I checked this, and all systems have the same workgroup - WORKGROUP. Since it's accessable now, we'll just go with that. I mean, I've never had problems with Windows, ever...(lol).