This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(144, 27%, 23%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EFM%3C/text%3E%3C/svg%3E)
I have a new Windows 11 Pro laptop (ASUS Zenbook) and joined to my home network. I have several NAS Servers that I can access with all my other computers on the network via Username and Password login, as the NAS Servers just show up as visible. On Windows 11, when I click on the NAS that shows up in the Network -> Computer file explorer view I get "Enter network Credentials" which defaults to my computer login credentials, and then I get a "\ServerName is not accessible." popup attached pic. I can never connect to the NAS nor do I get a chance to enter the username and password to the NAS.
Now, I have entered the credentials for the NAS into the Credential Manager, I have set my network to Private, I have set the Workgroup to my network workgroup name, I have enabled SMB 1.0 (even though the NAS uses SMB 2&3), I have Public folder sharing ON, Private Network Discovery is ON, File and Printer Sharing is ON, I have enabled insecure guest logons, I have restarted the laptop more times than I can count. No luck on simply seeing the folders on my NAS just like I can on the other computers on my network. I have Mac's, Windows 7, and Windows 10 computers that have no problem.
How can I just click on the NAS Server I want and get the Username and Password login prompt to access my server, and not the default Microsoft credentials login that pops up?
If I choose More Choices on the Network Login screen popup, I can see the Username for the NAS, and I click on it. I enter the password, and it just goes into a loop asking for the password over and over. The NAS Credentials are obviously there, but do not work. It states: A specified logon session does not exist. It may have already been terminated.
I have spent hours scouring solutions on the Internet to no avail . Why is something so simple as networking on your home network so difficult in Windows 11?
Hello Fred,
You could consider trying this: create a trace of the attempt to access the NAS and then share the trace data here for analysis. One command that you could start with is logman start gary -ets -p Microsoft-Windows-SMBClient -bs 64 -o why.etl; this starts a trace that is stopped with the command logman stop gary -ets. The file why.etl contains the trace data.
This trace data focuses on the SMB protocol; there are other things that could be traced, but it is probably best to keep things simple to start with.
Share the trace data here (probably via a link to OneDrive, Google Drive, etc.) and I will see if it contains any hints about what is going wrong.
Gary
Here is a link to the file in Onedrive: https://fredmercado-my.sharepoint.com/:u:/p/fred/EbySZPpT-zxMgGR5wmFQaCQBbvVKBk21VcPpbJer7cbcIw?e=cnQzR2
Hello Fred,
Trace data received, but I am still puzzling over it. This is what a trace of a similar scenario looks like on my PC:
And this is what it looks like on your PC:
The messages highlighted in yellow are a retry of the connection establishment.
The reported error messages are:
Status 0xC000005F is STATUS_NO_SUCH_LOGON_SESSION.
At the point that the problem occurs, the newest version of SMB has been negotiated and your username/password have not been used yet (they are used in the second SessionSetup request/response pair, visible in the trace of my PC).
There are some minor differences between the trace of my system and that of yours, but nothing that immediately seems like a cause of the problem. I'll get back to you when I have done a bit more research.
Gary
That is the error I get when trying to log onto the server using the NAS Credentials. See below:
Hello Fred,
The problem is proving difficult to crack. There are some more things that we could trace, but I have not yet found the ideal combination.
One simple thing that would be helpful to know is whether the Windows 11 PC can access shares on other Windows systems that you have?
Gary
They do not show up either. But Media devices, multifunction devices, and Printers do show up on the Network pane. No other Computer's show up. Just my two NAS Servers and the Win 11 Laptop own shared folders. I have turned Network Discovery ON and OFF many times to see if something would trigger a full list, but it has not.
Hello Fred,
Various protocols are used to discover devices on the network; SSDP (Simple Service Discovery Protocol) normally finds printers, scanners, displays, etc. and WSD (WS-Discovery) normally finds computers.
The failure to find other computers on the network might be related to the inability to connect to network shares, but that is not necessarily the case.
Can you connect to a Windows system share by using the name or address of another Windows system? For example:
> net use \\ray\c$ /user:gary
Enter the password for 'gary' to connect to 'ray':
The command completed successfully.
Gary
I get an error:
system error 67 has occurred
The network name cannot be found
Hello Fred,
What happens when you try the command net use \\localhost\ipc$?
I guess that some non-Microsoft security software (anti-virus, anti-malware, etc.) software is installed on the PC. It is possible that this type of software could cause the problem. What, if any, software of this type is installed?
Gary
When I run this command I get a "The command completed successfully". I do Have Bitdefender Antivirus Plus installed, and I did turn it off to run many of the tests in troubleshooting this issue, so that it can be taken out of the equation. Doing so had no impact on the results.
Hello Fred,
Tackling problems like this is my hobby - I mention that because it indicates that I keep trying to solve a problem until all hope is lost. Your patience might not be so extensible.
My suggestion would be to repeat the style of the first trace with an extended list of event sources. The (long) command to start the trace is: pktmon start --trace --provider Microsoft-Windows-SMBClient --keywords 0xFFFFFFFFFFFF --provider "Security: NTLM Authentication" --keywords 0x1FFFF --level 5 --provider {E4AD554C-63B2-441B-9F86-FE66D8084963} --keywords 0xFFFFFFFF --level 5 --provider {ac69ae5b-5b21-405f-8266-4424944a43e9} --keywords 0xFFFFFFFF --level 5 --provider {d0b639e0-e650-4d1d-8f39-1580ade72784} --keywords 0xFFFFFFFF --level 5 --file-name why.etl and the command to stop the trace is pktmon stop.
If
Gary
I ran the long command. I shut off Bitdefender first, and then tried to log into both of my NAS devices twice. Here is the link to the file: https://1drv.ms/u/s!Au-jv6zGZTolgiTmpSjhc2aLtT07?e=Sthb3b
Hello Fred,
A new day, a new "answer" started :-)
That last trace "why2.etl" seems not to correspond with your description. There is no data in the trace about Homenet-Qnap but there is a lot of SMB data to FRED-ASUS (i.e. the new laptop, looped back) and that is authenticated "implicitly" (since both client and server are the same device).
The connections to HOMENETSERVER fail, but this is probably because of a mix-up in the credentials. The usernames being sent to HOMENETSERVER include "fred", "freddy" and a 10 letter word starting with "M" (possibly a password being entered in a username field). All of the connection attempts failed authentication but the "process" (exchange of messages) looked good - I think that there is a good chance that the connection would work with the correct credentials.
So, although the final proof is still missing (successful connections to HOMENETSERVER and Homenet-Qnap), I think that using a "local" account will work.
It should also be possible to make the Microsoft account work too.
The first thing to try would be the tip from the Synology KB - specify the NAS usernames in the style "HOMENETSERVER\fred"; if this works then great (no need for a new trace) but, if not, could you send a new trace?
If the above fails, the next step would be to create a REG_DWORD value named "ConnectedAccountSSO" under the key HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Lsa\MSV1_0 and set its value to 2 (Always allow SSO). A reboot might be needed before this takes effect. Once again, a test and a new trace in the event of failure would be helpful.
The current "default" value for ConnectedAccountSSO (when it is not present in the registry) appears to be 0 (Deny SSO if the resource is public. Allow if the resource is private or enterprise. Deny SSO if the resource is unspecified). You mentioned in your very first message that the local network is set to Private, but this is something that we might need to check for two reasons:
Gary
So I made the change in the Registry to a 2 as instructed. I started the trace and tried to log into both NAS. The HomenetServer failed using my regular username and password and using the HomenetServer\fred username. However, with the QNap NAS it failed with my regular Username and Password, but it did work when using the HomeNet-Qnap\murcielago as the username and with the correct password. So there is some progress. Not sure why the Synology did not work, so maybe something there. All of this was done using my Main login on my laptop and not the local account. Here is the trace file: https://1drv.ms/u/s!Au-jv6zGZTolgipoPsiSqmiu535p?e=Mjjf6b
So I added the Homenet-Qnap\murcielago to my Credential Manager and rebooted my computer. When I click on the Homenet-Qnap server in the Network view ,it automatically works and I can see all the folder there. No luck with the Synology. I disabled the Auto-Block feature on the Synology in case it was blocking due to too many failed attempts, but still get the same failed results. I will continue to look into the Synology to see if I can find something that can be causing the login failures.
Hello Fred,
A quick look at the trace indicates that the ConnectedAccountSSO setting had no effect; I have been doing some more research about that since my last post and I now think that this was a "red herring". I would suggest deleting the value again, for tidiness sake.
Adding the server name as a prefix to the username (HomeNet-Qnap\murcielago) seemed to work perfectly at the trace level. I am now examining the HomenetServer failures for any hints about the cause of those failures.
Gary
Hello Fred,
In all of the "problem" failures, no username is specified in the SMB authenticate requests because something is blocking use of the Microsoft account.
In the most recent trace, there was one authenticate request to HomenetServer that did contain a username (HomenetServer\fred). This connection attempt failed after the Synology device checked the challenge response for that username. From the point of view of the trace on the Windows side, that connection attempt failed because either the password was incorrect or the Synology is "locking out" correct authentications.
In case there is any doubt about the password, one could try pasting exactly the same command into two PCs (the new one and another): net use \\HomenetServer\IPC$ /user:HomenetServer\fred plaintextpassword. Obviously
Gary
Ok tried that and it did not work. I went into the Synology and created a new account and password tried using the cmd line and also the GUI on the Network pane, but still no luck. I stopped all security on the Synology NAS with regards to blocking failed Login attempts to eliminate that as a culprit.
The login on my Windows 10 computer to Synology works fine.
Login to the Synology nAS form my Windows 10 computer works fine.
Hello Fred,
Could you try the following: using the simpler trace command (logman start gary -ets -p Microsoft-Windows-SMBClient -bs 64 -o why.etl) could you trace the command "net use \HomenetServer\IPC$ /user:HomenetServer\fred plaintextpassword" on both the new and Windows 10 computers? I could then try to compare the traces side-by-side.
Gary
Ok. Tried this on both computers for both NAS Servers to compare, since Qnap works on the Win 10 laptop. Curiously trying the CMD line to log in did not work on the Win 10 Laptop but using the GUI did work.
Why1 and why 2 are from the Win 11 Laptop. Why 3 and whay 4 are from the win 10 laptop.
https://1drv.ms/u/s!Au-jv6zGZTolglJQ9l92_qiMFRsw?e=blUohA
https://1drv.ms/u/s!Au-jv6zGZTolglMVzfyIH2HbklD_?e=sgAbz3
Hello Fred,
Something went wrong when creating why 2 and why 4. Below is an image of the full contents of why 2 (why 4 is similar):
That just shows that the trace has been started, but no events were recorded.
Why 1 and why 3 both show successful connections to Homenet-Qnap, but there is a difference: why 1 (Windows 11) uses NTLM v1 and why 3 (Windows 10) uses NTLM v2. I don't immediately know why that should be the case - more research is needed.
Gary
So the traces trying to connect to HomenetServer did not produce any results from either computer. Very Odd. I willtry again with only trying to connect to HomenetServer (Synology).
Here are the new traces for HomenetServer from both Win 11 and Win 10 using the cmd line. Both did not let me in and gave me errors: System error 67 has occurred.
The network name cannot be found.
New Why 2 & 4 here:
Ok. I think I found something...
Going on with your finding of NTLM V1 vs V2, I found an article where you can force V2 and this seems to work. I can now log into my Synology using the the HomenetServer\fred username and then the password. I also put this into the Credentail Manager, rebooted my laptop and worked right away. Here is what I found to make the change:
regedt32. Click OK or Enter.5. Click OK.
Hello Fred,
That is good progress. One odd thing is that I don't make many changes to settings like that on my (Windows 11) PC, but it always seems to use NTLM v2 by default.
>reg query HKLM\SYSTEM\CurrentControlSet\Control\Lsa /v LMCompatibilityLevel
ERROR: The system was unable to find the specified registry key or value
Would it be fair to say that ensuring NTLM v2 is used and that the username information includes a domain/server name prefix solves most or all of the problems?
Gary
Looks like this did the trick. I have rebooted several times to make sure it was not a fluke. Now that I added the SeverName/username and then password in theCredentials Manager, it works every time. I would never have found that without your invaluable help. Thank you so much!!!
This laptop is brand new, so I am not sure why ver 1 was a default and not V2. Maybe with all the changes I made trying to figure this out it was changed at some point. I do not know...
Hello Fred,
I enjoyed the challenge and learnt some things along the way (particularly about using Microsoft accounts for Windows logon - something that I have avoided in the past). I even feel a little bit embarrassed that it took so many traces, messages exchanges and time to reach this point. When I first read the problem description, I thought that it could be resolved in just a few minutes :-)
Gary
I think if I had just tried the ServerName/Username plus password from the beginning it may have worked. But that did not occur to me as I have mostly Mac computers, that the networking just works with not much to do.
Thanks agin for all your help. You are obviously and expert with Windows. I will mark this as solved by you.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(179.20000000000002, 99%, 27%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ET%3C/text%3E%3C/svg%3E)
I had the same issue on a laptop running Win 11 Pro setup for my small business and trying to connect to my home NAS. Your suggestion to logon using the "NASNAME\nasusername" in the username field with appropriate NAS password worked for me. My NAS username has no relationship to the win 11 login I use. Without that extra login info Win 11 must have been trying to login using the default domain of my microsoft account that I was logged-in on Win 11 which is why it kept failing. Thanks for this tip!
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(316.8, 50%, 40%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EP%3C/text%3E%3C/svg%3E)
Lost connection to my connected NAS drive after a Windows11 update. Sounds like this is a recurring problem that has happened to others here. I don't see an answer to this problem.