Solved Windows not accepting NAS credentials

The seminary where I am (I do most of the IT) has a Synology RS3621xs+ on the network. For some reason when I try to access it through Windows (either adding it on File Explorer, or typing the IP address in the run box), and it shows the box asking for my credentials, it refuses to accept them.

I know they are correct because if I open a browser, go to the web interface, and enter the exact same credentials, it works perfectly. If I go to another computer on the network (Windows or Mac), and enter the same credentials, it works as it should. But for some reason, when I try to access it through File Explorer on my computer.


I tried everything I could find, but nothing has worked. Any help/ideas much appreciated.

Which version of Windows? Home, Pro, Enterprise?

Can you see it under "Network" in file Explorer?

Dru2 said:

Which version of Windows? Home, Pro, Enterprise?

Can you see it under "Network" in file Explorer?

Click to expand...

Windows 11 Pro - sorry... should have specified that.

Yes, I can see it under "network" in file explorer. It just refuses to accept my (or any) credentials when I attempt to connect to it.

Have you tried all the suggestions from the Windows Club. Fix Enter network credentials error on Windows 11/10

glasskuter said:

Have you tried all the suggestions from the Windows Club. Fix Enter network credentials error on Windows 11/10

Click to expand...

Yes, with no luck.

• Check the Windows Firewall - temp disable if necessary to test.
• Check AV isn't interfering.
• Check Network Discovery Settings are enabled.
• Also is it on the same network to include having the same network name?
• Is the affected PC configured the same as the others that work?
• And can the affected PC see the other PCs on the network?

I know this might seem like a fishing expedition and you probably checked most, but as not to assume, I'm just trying to help narrow down things. Also, the reason I'm not focusing on the NAS yet is because you say it works with other PCs, so that would indicate the affected PC is the issue.

My two cents.

Dru2 said:

• Check the Windows Firewall - temp disable if necessary to test.
• Check AV isn't interfering.
• Check Network Discovery Settings are enabled.
• Also is it on the same network to include having the same network name?
• Is the affected PC configured the same as the others that work?
• And can the affected PC see the other PCs on the network?

I know this might seem like a fishing expedition and you probably checked most, but as not to assume, I'm just trying to help narrow down things. Also, the reason I'm not focusing on the NAS yet is because you say it works with other PCs, so that would indicate the affected PC is the issue.

My two cents.

Click to expand...

Confirmed that AV/firewall is not interfering (I didn't think it was, because I can connect just fine through the web interface by typing the IP address in my browser). All network discovery/sharing settings are on. It is connected to the same network, and is on the same subnet (there are 2 subnets...1 for staff and 1 for students, both are able to access the NAS, and I have the same issue when connected to both).

As far as I can tell, my computer is configured the same as all the other computers on the network, and I can see other PC's on the network (they show up in file explorer.

I appreciate the suggestions/help. I would rather double check the (more) obvious stuff so I am not pulling my hair out over something trivial.


I should also note that the same thing happens no matter how I try to connect to the NAS through Windows - typing the IP address in the run box, mapping a network drive in file explorer, creating a shortcut that points to the NAS, clicking it under the 'network' heading in file explorer, "net use" in CMD (returns "the command completed successfully" but nothing changes).

I should also add that this is not something new. I don't recall when it started, but this NAS has been a nightmare. Originally the only way I could get windows to see it was by typing the IP address in the run box (it would ask for credentials, and then work perfectly). Mapping it on file explorer (even using the IP address, just like in the run box) would not work. Then one day Windows decided that shouldn't work anymore, so that stopped working, and then for a while, my computer refused to see it at all (I could still ping the IP though). Then, a couple weeks ago, it decided to show up in file explorer, under 'network'...it just won't accept my credentials.

First, I have to say network troubleshooting isn't my strong suit; however, I do have a cloud-based NAS (WD PR4100) running and networked without issue, so, some of the things I asked and suggested are things I had to do to get mine working and networked. All my PCs are Windows based - 2 laptops, 2 desktops. My main desktop runs Windows 11, the other 3 PCs run Windows 10. I can see an access the NAS from all PCs.

That's the extent of my experience with NAS and networking. With that, I guess my question would be what "(more) obvious stuff" are you talking/looking at?

organist1958 said:

I appreciate the suggestions/help. I would rather double check the (more) obvious stuff so I am not pulling my hair out over something trivial.

Click to expand...

Additionally, if you're telling us only one of a few other PCs have the issue, should we not be looking at that specific PC?

And BTW, when I asked what version of Windows the affected PC was using was because for me, I was running an Insider's version of Windows 11 Education (equivalent to Enterprise) and had the same issue as you. I finally got it working per this post - Windows 11 Education in the same thread, but after subsequent Insider updates once again I was unable to access the NAS. I ultimately, I moved off Windows 11 Education (insiders as a whole) and all is good now under both Windows 10 Pro and Windows 11 Pro on my fully supported main desktop.

Maybe the above will help, maybe not.

Sorry, not sure how to quote only part of a post.

When I say "more obvious stuff" I am referring to basic things such as double checking AV/firewall, and other things like that. I tried everything I could find, but something is still missing.

"Additionally, if you're telling us only one of a few other PCs have the issue, should we not be looking at that specific PC?" - Yes, that is my intention with this thread...apologies if that was not clear.

I am not on any insider programs (I even have the "get me the latest updates as quickly as possible" slider turned off in settings). I am inclined to think that it may just be a problem with this build of Windows on my particular laptop/configuration. I have had a number of other issues of greater or lesser severity that seemed to come and go randomly, and then just disappear one day and never come back, usually they come/go within a week or two of getting one of the monthly updates (usually, not always). I think this might just be another instance of that.

organist1958 said:

"Additionally, if you're telling us only one of a few other PCs have the issue, should we not be looking at that specific PC?" - Yes, that is my intention with this thread...apologies if that was not clear.

Click to expand...

Which is why all my suggestions focused on the PC and not the NAS.

Not sure this will work for you (be surprised if it did), but...You might give this post a look - Windows 11 Education in trying the "Larman Workstation" fix on the affected PC. It "might" work. Note this was specific to the insider's version Windows 11 Education for me. It worked for a short while, but a few updates later stopped.

I'm not sure enabling SMB 1.0 would also solve anything being the other PCs work, but... There's also a security risk using it. Fortunately for me, it's not needed anywhere.

Outside of that, I'm afraid I'm out of ideas.

Just for fun, try allowing your NAS to use the older and deprecated SMB 1 protocol. I had to do this to allow Sonos to access the shared music folder on my Synology DS-112. On my, very old, NAS, the setting for this is under Control Panel, File Services, SMB/AFP/NFS, Advanced Settingd.

Did you read the thread?

Dru2 said:

Did you read the thread?

Click to expand...

Just who are you being rude to? You didn't make it clear.

kelper said:

Just who are you being rude to? You didn't make it clear.

Click to expand...

So how's that equate to reading the thread???

I tried it on SMB1, but that did not work. A bunch of things broke in an update I received a week or so ago, so I did a completely clean reinstall of Windows, and the problem is gone now.

Thank you all for the help/suggestions.

organist1958 said:

I tried it on SMB1, but that did not work. A bunch of things broke in an update I received a week or so ago, so I did a completely clean reinstall of Windows, and the problem is gone now.

Thank you all for the help/suggestions.

Click to expand...

Glad you got it sorted. Figured it was related to the PC. Thanks for the feedback.

Peace