Forum Discussion

SurfingOnLifeBuoy's avatar
SurfingOnLifeBuoy
Copper Contributor
Apr 01, 2022

Windows 10 Pro don't give permission to access my NAS. My 2 other PC can.

Hi Guys.

 

To understand my problem, even if I would like to make it fast or short, I can't.

I've been on it for 6 weeks now so please, bare with me.

 

I bought a WD MY Cloud OS 3 in 2015.

Worked great until Microsoft and WD did an update that prevent us from using our NAS anymore.

Right after the Win 10 Pro update from 19044.1543 to 19044.1620, could not access it anymore.

Mainly, when I entered \\NASName in the This PC top line in Windows File Explorer, I used to have access directly to the shared folders on the NAS but after this update, just error and permission error message asking for credentials.

 

Tried to replace it by using my windows 10 pro (2nd PC) data server, where my old NAS was connected with other external drives. Too many problems to solve.

 

Windows was popping Windows Security, Enter network credentials to connect to : \\xxx.xxx.x.xx, show username, asked for PW, Remember credentials. Repeatedly.

 

I did add this PC to Windows credentials in Control Panel, no can do.

 

I bought a Asustor AS5202T, 2 bay.

Add 2 harddrives.

Start configuring. Easy.

Good manuals and great explanations.

Good courses too.

Learned a lot and at some point I did reach the end of my knowledgeable tries so I asked for Asustor Support for help and we did a AnyDesk Session.

 

I filmed the whole thing. I could see all the things that are not in the manuals.

Learned that there was a hidden sub menu that I need to activate SMB.

I had selected SMB 3 in one setting but one was hidden, I couldn't have known.

Would have helped to have that info in the config manual.

They showed me that the NAS as absolutely no problem.

They tried to map a shared folder on the NAS, from Windows File Explorer, they spend 30 minutes, at least 20 tries and they were never able to make it add the shared folder.

Each time, Windows was popping Windows Security, Enter network credentials to connect to : \\xxx.xxx.x.xx, show username, asked for PW, Remember credentials. Repeatedly.

They mapped a shared folder from the Asustor Control Center and the mapped shared folder appeared instantly in Windows File Explorer (WFE).

Told me I had to see with Microsoft Windows 10 Support.

 

This morning, I just did a test on my 2nd PC, data server so I entered all the NAS credentials into Windows Credential on Control panel.

I open WFE, and clicked on Network.

My NAS Server Name appeared.

I clicked on it, all shared folders appeared in WFE.

Like nothing.

 

I asked my wife to do the same on her PC (3rd PC), the 3 PC are on the same Network Workgroup.

I entered all the NAS credentials into Windows Credential on Control panel.

I open WFE, and clicked on Network.

My NAS Server Name appeared.

I clicked on it, all shared folders appeared in WFE.

Same thing.

 

Still cannot do the same on my main PC, with which I did the whole installation of the NAS. How Ironic. My brain is bleeding now.

 

I factory default the whole thing 2 times after the first initialization, this week.

I was practicing.

This morning, I did it again to be able to configure the NAS with Link Aggregation (Changed Switch for a IEEE 802.3ad), reconfigured everything with what Asustor Support did that I didn't know.

 

I updated the windows 10 pro version on my data server, from 19044.1543 to 19044.1620, so it be like my main PC.

I did the same test and my data server can access and map the shared folders like I want it to do but it still doesn't work on my main PC.

 

So what Am I missing ?

3 PC.

3 time Windows 10 Pro.

2 OS Build as 19044.1620 and 1 as 19044.1543.

One 19044.1620 and one 19044.1543 can access and map shared folders.

Mine is 19044.1620 and cannot access or map shared folders.

 

What I need is an official Microsoft Windows 10 Pro Support that can connect to my pc remotely and show me what is the difference between my PCs because I really don't know.

 

I have that service with Microsoft 365 but I don't think they can work on Windows 10 Pro Operating system.

 

Because right now, the only thing I get is a window with the message :

"Windows cannot access \\xxx.xxx.x.xx
You do not have permission to access \\xxx.xxx.x.xx . Contact your network administrator to request access.

Same thing when the IP address is replaced by the NAS Name.

 

My main PC is a Lenovo Thinkpad Carbon X1, 

Processor Intel(R) Core(TM) i7-10710U CPU @ 1.10GHz 1.61 GHz
Installed RAM 16.0 GB (15.8 GB usable)
System type 64-bit operating system, x64-based processor
Pen and touch Touch support with 10 touch points

Edition Windows 10 Pro
Version 21H2
Installed on ‎07-‎Jan-‎2022
OS build 19044.1620
Experience Windows Feature Experience Pack 120.2212.4170.0

 

So Guys.

Who can help me with this ?

 

2 Replies

  • Jameswalter's avatar
    Jameswalter
    Copper Contributor
    i don't know, but this is the solution I found. Check with this.
    Step 1. Click the Windows icon (Start Menu) and select Settings.
    Step 2. On the Windows Settings window, select Network & Internet to open a Status window.
    Step 3. Click Change Adapter Options.
    Step 4. Right-click an adapter you use for accessing the NAS device and click Properties
    Step 5. Check/tick (if not checked) Internet Protocol Version 4 (TCP/IPv4), select it, and click the Properties button.
    Step 6. Click the Advanced button on the window that pops up.
    Step 7. On the Advanced TCP/IP Settings window, choose the WINS tab, select Enable NetBIOS over TCP/IP, and then click OK to save changes.
    Step 8. Close all the windows that you opened while making these changes.
    Step 9. Repeat these steps for all the adapters you use for your NAS drives.

    Regards,
    James
  • Avetik's avatar
    Avetik
    Copper Contributor
    Same problem started to appear on my computers already a couple of years ago, with each new major windows update. And every time it gets harder and harder to sort out. In the beginning I found this instructions very helpful.
    https://www.youtube.com/watch?v=5bIcJluf-0Q&t=8s
    But recently they won't solve the problem any more. Got knows what else did they touch in the networking files.