AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |
Back to Blog
Qfinder mac cant find nas11/16/2023 The failure to "discover" other computers on your network might be related to confusion about the status of the local network.If the NAS devices were deemed to be "private" then even a ConnectedAccountSSO value of 0 should not prevent SSO to the NAS devices.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: Deny SSO if the resource is unspecified). Allow if the resource is private or enterprise. 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. Once again, a test and a new trace in the event of failure would be helpful. A reboot might be needed before this takes effect. 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). 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? It should also be possible to make the Microsoft account work too. So, although the final proof is still missing (successful connections to HOMENETSERVER and Homenet-Qnap), I think that using a "local" account will work. 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. 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). The connections to HOMENETSERVER fail, but this is probably because of a mix-up in the credentials. the new laptop, looped back) and that is authenticated "implicitly" (since both client and server are the same device). There is no data in the trace about Homenet-Qnap but there is a lot of SMB data to FRED-ASUS (i.e. That last trace "why2.etl" seems not to correspond with your description. Why is something so simple as networking on your home network so difficult in Windows 11? I have spent hours scouring solutions on the Internet to no avail. It states: A specified logon session does not exist. The NAS Credentials are obviously there, but do not work. I enter the password, and it just goes into a loop asking for the password over and over. If I choose More Choices on the Network Login screen popup, I can see the Username for the NAS, and I click on it. 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? I have Mac's, Windows 7, and Windows 10 computers that have no problem. No luck on simply seeing the folders on my NAS just like I can on the other computers on my network. 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. I can never connect to the NAS nor do I get a chance to enter the username and password to the NAS. 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 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. I have a new Windows 11 Pro laptop (ASUS Zenbook) and joined to my home network.
0 Comments
Read More
Leave a Reply. |