This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
a specified logon session does not exist. it may already have been terminated - after i joined the device to azure active directory
-i cannot access our shared folder in our server after i joined the device to azure AD and use office 365 account (Please see click the link below to see the error image for your reference), but if i use local administrator of the device i can access the file server using the credentials with no problem, please note that we dont have an premises active directory or GPO, kindly help me.
I had this problem with a mapped drive to a NAS for a user. I added the name of the NAS as the domain name before his logon name "NASNAME\LOGONNAME" that appears to disconnect it from the AZURE directory and the drive mapped.
I had same problem issue , and I've read many article , but the last solution is easy and solved the problem . To reach a network storage just you need to write NASNAME\LOGONNAME , if you write only LOGONNAME you cannot reach.
Thanks for the solution providers.
Mehmet ERMAN
Hi MehmetErman,
Yes it is working as you said. Thank you very much. Haveto enter NASNAME\LogonName in Username then will enter to the password. Advance Happy New Year 2021.
Hey just wanted to come in here to say that I had this exact same issue with some new Windows 10 computers I bought for my organization. This fixed the problem easily.
Thanks! John, this worked like a charm.
I believe this fix will work for me but I'm not sure where to put it into the system/logon
Until I can I can't upgrade the lunch software because the pc can't see the server which is a NAS and needs access to it to save the daily data and backup the data.
Any suggestions would be greatly appreciated.
Absolutely correct. I enabled SMB, disabled firewalls to test connection and nothing. Used 10.50.40.x\USERNAME and it went straight through. Thanks heaps
Thank you John, this works great!
I just came here to say I've been chasing this bug down for MONTHS since we Azure AD joined all our laptops to the network... and yet this simple solution solved the problem. THANK YOU!!!!!
In my case, I added credentials to the credential manager, using the following information:
Network address: IP-address of the server
Username: IP\Username
Password: Password
When connecting for the first time using \IP, I had to click more options and select the new credential. Then I re-typed the password, and I gained access. Optionally, you can click the checkbox to remember the credentials, so you don't have to log in over again.
This worked for me
Fabulous, thank you so much
@@@@@@@@@
Honestly, I am very frustrated with the way Microsoft keeps breaking basic interoperability that has worked for ever. That being said, I have found that using '.' in front of the account will tell Windows this is a local user. i.e. '.\useraccount' will allow you to connect where 'useraccount' won't. That worked for me on my Azure AD joined workstation connecting to SMB shares on local NAS and Linux boxes.
I can't believe it, but this worked and solved my problem today. Thanks for posting it!
double post
Awesome, Gary. This is a slick and super easy solution. I can't believe I spent 1 1/2 days banging my head against the wall. Great thanks.
This worked for me. Thanks
Did it for me on a Asustor NAS. thanks ! this has been a painpoint for a long time.
I have the exact same issue on all new desktop builds where I connect with an office 365 account. Instead of asking for a login it's asking for a pin. I've added credentials through the credential manager and disabled the hello pin feature. Still getting the same error message.
I was able to solve this issue by simply starting my windows desktop with my 'administrator' account. I had done all the suggestions given and nothing worked. I even had to uninstall the last update I did for Windows 11 and it still didn't resolve it. But when the idea to try logging in with my 'Administrator' account hit, I was surprised it worked and angry (lol) at the amount of time wasted reading up so much diverse suggestions and none mentioning a login as Admin! I hope this works for others like me! :)
Add share path in web credentials in the windows PC . before adding the username add the share path url removing the two \ . it works for me