After reinstalling Windows 11 cannot connect to NAS from more than 1 account

Anonymous
2024-12-13T08:34:15+00:00

This is very odd. A few days ago, I had to reinstall Windows 11 on my laptop. I downloaded the Media Creation Tool and performed a clean installation, a procedure I have execute hundreds of times. The installation required a Microsoft account, which I entered. After completing it and making my home network a private network, my Synology NAS turned up in Explorer.

However, for the first time in my life, after double clicking it, it said can't find it showing error code 0x80070035. It was accessible through a browser, but not in the network neighbourhood, not even entering \NAS (not the real name) in a command prompt. Only after creating a separate local account I was able to connect from there. So I made a network connection there using a drive letter, and could access all files. But only in that account! Returning to the other account and also a third, newly created account, the drive was no longer visible.

To be clear, I have done this many times and up until a couple of months ago this posed no problem whatsoever. What has changed? Should I reinstall Windows 11 from an earlier build? Is that even possible?

***Move from Windows / Windows 11 / Internet and connectivity***

Windows for business | Windows Client for IT Pros | Networking | Network connectivity and file sharing

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question. To protect privacy, user profiles for migrated questions are anonymized.

0 comments No comments
{count} votes

3 answers

Sort by: Most helpful
  1. Anonymous
    2024-12-17T13:35:31+00:00

    Hello

    You can try enabling the option to connect to other credentials while pairing your NAS.

    Image

    Map a network drive in Windows - Microsoft Support

    Best regards

    Zunhui

    0 comments No comments
  2. Anonymous
    2024-12-31T12:31:51+00:00

    I reinstalled once more but now downgraded tot 22H2. That solved the problem, at least sufficiently. Case closed

    0 comments No comments