Forum Discussion

Aspirant

Jul 28, 2020

Solved

windows connecting logon session does not exist

I cannot connect from my Windows machine (W10 pro for Workstations) to my NAS. I can see it, I can see volumes which on NAS admin page have SMB enabled but I cannot open the volumes. When I loggin with the admin credentials it says:

"A specified logon session does not exist. It may already have been terminated."

Any idea how to solve that?

BTW, I can without any problems connect to the NAS from my Mac.

Thank you

Krzys

Sandshark
Jul 29, 2020
Assuming you did use the proper password, I believe it also will not work if your NAS still has the drefault admin password. I'm not sure what error message Windows will give in that case, but it could be that one. Windows doesn't always map network errors on Linux boxes to the best message.

5 Replies

Replies have been turned off for this discussion

StephenB
Guru - Experienced User
Jul 29, 2020

What version of Windows 10 are you using?

Also, are you logging in to the PC with a local Windows account, or are you using a microsoft account?

There is a very old thread on technet here: https://social.technet.microsoft.com/Forums/en-US/076e47a6-5244-49fd-aaeb-dc2660974281/a-specified-logon-sessions-does-not-exist-it-may-already-have-been-termianted

Can you try this test?

Open CMD on the PC and enter

net use * /delete /y net use t: \\nas-ip-address\data /user:admin nas-admin-password

using the real IP address and NAS admin password of course. Be careful with the typing (both the spaces and the two different slash directions).

This will attempt to mount the NAS data volume to drive letter T.
- kwicher
  Aspirant
  Jul 29, 2020
  It does not work.
  
  I am getting info that the password is incorrect.
  I have also tried to include ip before the admin
  
  K
  - Sandshark
    Sensei - Experienced User
    Jul 29, 2020
    Assuming you did use the proper password, I believe it also will not work if your NAS still has the drefault admin password. I'm not sure what error message Windows will give in that case, but it could be that one. Windows doesn't always map network errors on Linux boxes to the best message.