PC not seeing NAS, tried everything

Hello all, first post here.

I am the unofficial "tech person" at a seminary I am studying at. We have a Synology RS 3621xs+ on the network (moderate size, everything is Ubiquiti), which most people can see and connect to just fine (either using IP address, path, or the tool find.synology.com). I have a Dell XPS 13 2 in 1 that absolutely refuses to connect to it. The NAS was setup in a different facility (we moved due to lack of space), and I was able to connect to it just fine, but on the new network my computer will not connect to it. I have tried just about every trick I found online, and I have not been able to find someone with a problem like mine.

When I try to connect using the path (which has not changed, and others can use without a problem), I get the error "the mapped network drive could not be created because the following error has occurred: An unexpected error occurred". (see attached screenshot)

If I try to use the find.synology.com tool, then it sort of finds it, but gives no information aside from the IP address (see second screenshot, note the little information bubble...it makes no difference if I disable extensions/use a different browser). if I try to connect to the IP address, then it doesn't work, and I can't even ping the IP (times out). Keep in mind that everyone else on the network can see and connect to it without any issues.

It is not incredibly important, but I really need to be able to access it. Please help...I am totally perplexed.

Hello and welcome.

At the command line, could you see what you get when you do:

net view (enter)

This is what I got.

Also, I thought that because some are able to connect to it, everyone was able to connect without any problem...that is not the case. There are some computers that are able to connect to it without any issue, but others exhibit much the same symptoms that mine is showing, the only difference is that instead of giving the unexpected error, they just outright say they cant connect.

The only commonality between the computers that are able to connect is that both are desktops (one is a mac mini, the other is a PC on Windows 11) connected to ethernet. however, when I connect my computer to ethernet, I still have the same issue.

Sorry, but view was misspelled.

OAT said:

Hello and welcome.

At the command line, could you see what you get when you do:

net view (enter)

Click to expand...

With that command as Admin I get System error 1231 on my old WD NAS drive and a new Buffalo I just set up as additional storage. I created a Public folder on the Buffalo, just like I have on the WD and things went well on Win11 Pro and Win10 Pro. Tried the same on Linux Mint 21 and just opening Files then clicking on Network got it populated and accessible, appeared to be auto-Mapped.

I think I figured it out...and it was pretty stupid. the problem is that there is a "staff" subnet, and it is only visible/able to be reached on the "staff" subnet. The computers that are able to connect without issue are already connected to the staff subnet. The company that manages our network will change it within the next couple days, and I will post back here to confirm, but I am 99% sure, as I had a 3rd person try to connect, and they had the same problem, but when they switched over to the staff network there was no issue.

I am pretty sure that is what it is. Glad it will be taken care of.

Just out of curiosity, you aren't running an education or enterprise version of Windows 11, are you?

Never mind, you seemed to have figured it out

Dru2 said:

Just out of curiosity, you aren't running an education or enterprise version of Windows 11, are you?

Click to expand...

No, it is my personal computer running Windows 11 Pro. It is just the way the network is configured.

OAT said:

@Dru2
I think the OP specs mention a Windows 11 Pro set-up.

Click to expand...

Yep, I saw the same, but never hurts to confirm as I've seen people post issues on systems different from what system specs say

At any rate I see the OP figured it out.

The company that manages the network changed some things, and now I am able to see/and access it though the web interface.

I still can't add it to windows as a mapped network drive, as I get the error "Windows could not access \\___. Check the spelling of the name". I tried all the basic stuff I could find online, but I know it is not my computer, as others have the same issue. I also get the same strange result when using find.synology.com

In any case, it is not the end of the world, as people are able to access it through the web interface, which allows them to do everything they need, so I can figure out the issue later. Thank you to all who gave suggestions.