Share via

“a specified logon session does not exist. it may already have been terminated”

Eduard Paul 16 Reputation points
2020-06-01T09:48:49.39+00:00

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.

a specified logon session does not exist. it may already have been terminated

Microsoft Security | Microsoft Entra | Microsoft Entra ID
0 comments

6 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2020-09-20T19:15:52.36+00:00

    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.

    20+ people found this answer helpful.
  2. Gary Ford 115 Reputation points
    2023-02-22T01:26:24.63+00:00

    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.

    20+ people found this answer helpful.
  3. Paul Busch 35 Reputation points
    2023-05-29T16:26:29.5633333+00:00

    This issue happens after joining a system to Azure AD that was previously on a workgroup or local domain pointing to a local NAS. The correct way to solve this is to specify the local name or ip of the NAS in your user name. So username would be something like 192.168.x.x\username and then whatever password belongs to that username that would exist on the NAS. I tried using the .\username to force a local sign on, but that did not work.

    7 people found this answer helpful.
  4. rome njaka 1 Reputation point
    2022-11-15T23:46:06.58+00:00

    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! :)

  5. Patrick H 1 Reputation point
    2020-06-04T05:32:02.03+00:00

    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.

    0 comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.