I recently setup a new PC with Windows 11 Pro. I have a NAS and mapped network shares using the my NAS credentials without an issue. The problem is that Windows 11 insists on trying to login to the NAS on startup using my Microsoft credentials which, of course, fails. Any idea how I can stop this behavior? I have hundreds of failed logins. From my NAS: I disconnected the network shares and executed Net Use /Delete * which returned no entries in the list but the failed logins continue. When I create the shares and look at System info, it shows the correct account but on restart it show the Microsoft account. Why? After setting up the shares: After restarting:

Hi Kevin, Thanks for your post. Please try the following method to manually import the credentials and see if it works. Open File Explorer from the taskbar or the Start menu, or press the Windows logo key + E . Select This PC from the left pane. Then, on the File Explorer ribbon, select More > Map network drive . Note: If you don't see Map network drive on the More menu, you can right-click the This PC node in the folder pane and you'll see the command there. 3. In the Drive list, select a drive letter. (Any available letter will do.) 4. In the Folder box, type the path of the folder or computer, or select Browse to find the folder or computer. In the Folder box, type the path of the folder or computer, or select Browse to find the folder or computer. To connect every time you log on to your PC, select the Reconnect at sign-in check box. ** This is the point where you should also choose "Connect using different credentials". Upon clicking Finish in the next step, it will ask you for the username and password to use. 5. Select Finish . Best Regards, Ian Xue If the Answer is helpful, please click " Accept Answer " and upvote it. Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

windows 11 failed samba login

Kevin Roberts 5

I recently setup a new PC with Windows 11 Pro. I have a NAS and mapped network shares using the my NAS credentials without an issue. The problem is that Windows 11 insists on trying to login to the NAS on startup using my Microsoft credentials which, of course, fails. Any idea how I can stop this behavior? I have hundreds of failed logins. From my NAS: 2024-02-14

I disconnected the network shares and executed Net Use /Delete * which returned no entries in the list but the failed logins continue. When I create the shares and look at System info, it shows the correct account but on restart it show the Microsoft account. Why? After setting up the shares: 2024-02-14 (1)

After restarting: 2024-02-14 (2)

Andy Funnell 0 Reputation points

2024-03-18T13:04:37.5833333+00:00

Did you work out how to fix this?

I am having the same problem although I often get the same errors when my PCs wake up from sleep.
Kevin Roberts 5 Reputation points

2024-03-18T13:09:20.91+00:00

Unfortunately, the issue has not been resolved. Enabling the NAS guest account with a password and no access to anything reduced the login attempts from dozens to two or three.

1 answer

Ian Xue (Shanghai Wicresoft Co., Ltd.) 31,751 Reputation points Microsoft Vendor

2024-02-20T06:59:37.4966667+00:00
Hi Kevin,

Thanks for your post. Please try the following method to manually import the credentials and see if it works.

Open File Explorer from the taskbar or the Start menu, or press the Windows logo key + E.

Select This PC from the left pane. Then, on the File Explorer ribbon, select More > Map network drive.

Note: If you don't see Map network drive on the More menu, you can right-click the This PC node in the folder pane and you'll see the command there. 3. In the Drive list, select a drive letter. (Any available letter will do.) 4. In the Folder box, type the path of the folder or computer, or select Browse to find the folder or computer. In the Folder box, type the path of the folder or computer, or select Browse to find the folder or computer. To connect every time you log on to your PC, select the Reconnect at sign-in check box. ** This is the point where you should also choose "Connect using different credentials". Upon clicking Finish in the next step, it will ask you for the username and password to use. 5. Select Finish. Best Regards,

Ian Xue

If the Answer is helpful, please click "Accept Answer" and upvote it. Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
Please sign in to rate this answer.
Kevin Roberts 5 Reputation points

2024-02-27T06:41:01.8166667+00:00

Thanks for a response but this completely misses the problem. I have no problem creating a mapped network drive using my NAS credentials. The mapped drive works as expected and re-establishes on restart. Forget mapping the drive, that works. The problem is, when I start Windows 11, it tries to login to my NAS using my microsoft account credentials even though the mapped drives are setting up fine using the NAS credentials I provided. Even if I completely remove the mapped drives and my NAS credentials, Windows 11 still tries to login to my NAS using my microsoft account credentials. It doesn't appear to have anything to do with the mapped drives but something else entirely.

Ian Xue (Shanghai Wicresoft Co., Ltd.) 31,751 Reputation points Microsoft Vendor

2024-02-29T06:12:45.1766667+00:00

Hi Kevin, Sorry for the miundertsanding. How about update login credentials for mapped network drives?

Open run command by pressing Windows + R and type control and hit enter, this will open the control panel.

Set view by to large icons from the top right corner. Click on Credential Manager

Click on Windows Credentials and choose the Mapped Network drive folder name.

Expand that credentials and choose edit, and from the next windows under Edit Generic Credentials, Enter your username and recently changed password. And save it.

Kevin Roberts 5 Reputation points

2024-02-29T07:49:15.6266667+00:00

Thanks for the suggestion. There was no change. You can see in the attached image of the NAS connection log that the first sign-in on restarting is the re-establishment of the NAS mapped drives (highlighted) followed by numerous attempts to login using the Microsoft credentials (the system automatically tries the guest account if a login fails but that is disabled and guest logins are not allowed so sign-in fails). For the record, the NAS credentials have been added, edited and removed numerous times. Even with no NAS credentials, the attempts to login to the NAS using the Microsoft credentials continue. For this reason, I don't think it's related to the mapped drives. Is there any other reason Windows 11 would try to login to my NAS, a service or some automatic connection?

Ian Xue (Shanghai Wicresoft Co., Ltd.) 31,751 Reputation points Microsoft Vendor

2024-03-01T06:04:25.6633333+00:00

Hi Kevin,

Thanks for your reply. Please understand that I have done a lot of research but still don't find the solution. For such kind of issue, for deeper analysis, we should capture some performance monitor or other deeper traces. Due to limited resource in the community, it is recommended to contact Microsoft Phone Support. Support channel: Contact Us - Microsoft Support

Thanks a lot for your understanding and cooperation.

Kevin Roberts 5 Reputation points

2024-03-02T15:42:14.4933333+00:00

Thanks for your effort.

I'll install NetMon next and do a boot capture and see if I can get any more information on where this is coming from.

Got this repeating in the capture log AFTER the network shares have already been successfully connected:

5596 10:59:29 AM 3/2/2024 21.9150364 (4) FE80:0:0:0:A0C2:10F3:483D:4A57 FE80:0:0:0:12BF:48FF:FE8B:E29D SMB2 SMB2:C SESSION SETUP (0x1)

5597 10:59:29 AM 3/2/2024 21.9157831 (4) FE80:0:0:0:12BF:48FF:FE8B:E29D FE80:0:0:0:A0C2:10F3:483D:4A57 SMB2 SMB2:R - NT Status: System - Error, Code = (22) STATUS_MORE_PROCESSING_REQUIRED SESSION SETUP (0x1), SessionFlags=0x0

5598 10:59:29 AM 3/2/2024 21.9172504 (4) FE80:0:0:0:A0C2:10F3:483D:4A57 FE80:0:0:0:12BF:48FF:FE8B:E29D SMB2 SMB2:C SESSION SETUP (0x1)

5604 10:59:29 AM 3/2/2024 21.9360422 (4) FE80:0:0:0:12BF:48FF:FE8B:E29D FE80:0:0:0:A0C2:10F3:483D:4A57 SMB2 SMB2:R SESSION SETUP (0x1), SessionFlags=0x1

5605 10:59:29 AM 3/2/2024 21.9360891 (4) FE80:0:0:0:A0C2:10F3:483D:4A57 FE80:0:0:0:12BF:48FF:FE8B:E29D SMB2 SMB2:C TREE CONNECT (0x3), Path=\\AS6204T-E29D\IPC$

5606 10:59:29 AM 3/2/2024 21.9364394 (4) FE80:0:0:0:12BF:48FF:FE8B:E29D FE80:0:0:0:A0C2:10F3:483D:4A57 SMB2 SMB2:R - NT Status: System - Error, Code = (34) STATUS_ACCESS_DENIED TREE CONNECT (0x3)

5607 10:59:29 AM 3/2/2024 21.9364842 (4) FE80:0:0:0:A0C2:10F3:483D:4A57 FE80:0:0:0:12BF:48FF:FE8B:E29D SMB2 SMB2:C LOGOFF (0x2)

5608 10:59:29 AM 3/2/2024 21.9367719 (4) FE80:0:0:0:12BF:48FF:FE8B:E29D FE80:0:0:0:A0C2:10F3:483D:4A57 SMB2 SMB2:R LOGOFF (0x2)

Looking at the captured packets, I can see the Microsoft account being used for these generic IPC$ SMB connection attempts. Why it's doing this is the question?

Andy Funnell 0 Reputation points

2024-03-18T13:02:23.5333333+00:00

Did you work out how to fix this?

I am having exactly the same problem although I also get the errors when my PCs wake up from sleep.

Kevin Roberts 5 Reputation points

2024-05-15T13:03:05.7933333+00:00

For unknown reasons, the login attempts have ended and I've disabled the Guest account again.
Sign in to comment

Share via

windows 11 failed samba login

1 answer