Troubleshooting guide
How to fix the problem
Windows may reject an anonymous SMB connection from a guest. The safest path to repair is usually a NAS user with a password and the correct folder permissions. The same name on the PC and NAS does not automatically guarantee the same passwords.
Possible solutions
Choose the method that matches your situation. Start with the simplest suitable option and check the result. If the problem is fixed, you do not need to continue with the other methods.
Creating a named NAS account
Grant only the necessary rights.
Steps to follow
- In the NAS administration menu, create a separate user and a strong password according to the manufacturer's instructions.
- Give that user read or write access only to the required shared folder.
- Open the NAS share path in Windows File Explorer and choose to log in with a different account if offered.
- Enter the NAS username and password and try to open the allowed folder.
Removing a previous guest login
Remove only the old session of a specific NAS.
Steps to follow
- Close files and windows open from the NAS to avoid losing unsaved changes.
- Control Panel > Credential Manager > Windows Credentials, find only the name or IP of this NAS and remove the incorrect entry.
- If the old session persists, log out of your Windows account or reboot after saving your work, then log in with a named NAS account.
- If still rejected, check NAS log for user and SMB signing errors without changing global Windows security.
If the problem persists
If the NAS only allows anonymous legacy access, look for a manufacturer update or compatible secure method. Do not change the security policy on your work computer without an administrator, and do not open sharing to the entire Internet.
Request a repair