Path: csiph.com!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail From: Fokke Nauta Newsgroups: alt.comp.os.windows-11 Subject: Re: Can't connect to laptop Date: Sun, 27 Apr 2025 19:31:22 +0200 Lines: 155 Message-ID: References: <19dpvj20hqpzx$.dlg@v.nguard.lh> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Trace: individual.net sxNJ3qKEl1DJ54ZXe7IlUAHI9PPEBOp/qvA9JNiMFJUkquH4UB Cancel-Lock: sha1:LXu/trPeA8BCjR9cQ44+RH2E3Xs= sha256:K5Zc1y1O7yrymNm7262u9h/mGMchzUAI4wn9DreP9AI= User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101 Thunderbird/102.15.1 Content-Language: nl In-Reply-To: Xref: csiph.com alt.comp.os.windows-11:18744 On 27/04/2025 13:11, knuttle wrote: > On 04/27/2025 6:50 AM, VanguardLH wrote: >> Fokke Nauta wrote: >> >>> My wife has a W11 Pro laptop. It is visable in the network but I can't >>> open it. Her network detection is on, just as file and printer sharing. >>> It is on a private network. >>> When I try to open it from my pc, I get the message "Windows cannot >>> access" the name of her laptop. Error code 0x80070035. >>> This code says how to Enable NetBIOS over TCP / IP. I did and restarted >>> the laptop. >>> I still can't open it from my pc. All other pc's I can open, so this is >>> a problem with her laptop. >>> What else can I do to open it and access the folders and files? >>> Thanks in advance for your help. >> >> Is your wife's computer assigned to the same workgroup as the remote >> host to which she tries to connect? >> >> https://www.pcworld.com/article/2191054/windows-11-how-to-set-up-a-network.html >> >> That mentions the step where you decide in which workgroup your host is >> assigned.  Hosts in the same workgroup can work with each other.  For >> example, you might have SOHO hosts for work-use only that you don't want >> your wife, kids, or anyone else on your intranet to access.  The default >> workgroup name is "WORKGROUP" (I don't think it needs to be uppercase). >> >> The PCworld article fails to mention just how you get directly into the >> System Properties config tool without having to walk through some setup >> wizard.  Run: >> >> sysdm.cpl >> >> Under the General tab, click Change (your computer name).  The next >> dialog lets you specify the workgroup name.  Your wife needs to use the >> same workgroup name as your other intranet hosts to which she wants to >> connect. >> >> In Control Panel (control.exe), select "Network and Sharing Center", is >> your wife's computer in a private or public network.  Intranet sharing >> requires using a private network.  Public is, well, when you're on a >> public network, and don't want anyone accessing your host. >> >> https://support.microsoft.com/en-us/windows/essential-network-settings-and-tasks-in-windows-f21a9bbc-c582-55cd-35e0-73431160a1b9 >> which says: >> - Public network (Recommended). Use this for networks you connect to at >>    home, work, or in a public place. You should use this in most cases. >>    Your PC will be hidden from other devices on the network. Therefore, >>    you can’t use your PC for file and printer sharing. >> - Private network. Your PC is discoverable to other devices on the >>    network, and you can use your PC for file and printer sharing. You >>    should know and trust the people and devices on the network. >> >> >> I can't tell from: >> >> https://learn.microsoft.com/en-us/windows-server/storage/file-server/troubleshoot/detect-enable-and-disable-smbv1-v2-v3?tabs=server >> >> if SMBv2 and SMBv3 are enabled by default in Windows 11.  I've seen >> other posters mentioning having to enable SMB to get home networking to >> function, but I'm not sure if that is between Windows hosts using >> auto-discovery, or between Windows hosts to Mac, Linux, or NAS hosts. >> >> Another problem I've seen discussed is that you need to have a login >> that permits access.  Do the following: >> >> - Open the run dialog (Win+R). >> - Run: control /name Microsoft.CredentialManager >> - Select Windows credentials. >> - Click Add Windows credential. >> - Enter your remote path with your Windows credentials. >> >> This is where I'm unsure about what to enter here. >> >> https://support.microsoft.com/en-us/windows/credential-manager-in-windows-1b5c916a-6a16-889f-8581-fc16e8165ac0 >> >> That was incomplete, and unhelpful in knowing on which host you define >> Windows credentials for the other host. >> >> My guess is that you run this on the host where you want to connect to >> your remote host.  Supply the IP address of your remote host, and the >> login credentials for a Windows account defined on the remote host. >> Using the IP address of the remote host should work.  You might be able >> to specify the hostname assigned to the remote host. >> >> https://buffaloamericas.com/knowledge-base/adding-windows-credentials-of-your-nas-on-windows-10-or-windows-server-2019 >> >> That has you use the Credentials Manager on your Windows host to add >> credentials for the NAS device (remote host). >> >> https://www.1kosmos.com/identity-management/windows-credential-manager/ >> >> pretty much says the same: define the credentials on your host for the >> remote host to which you want to connect.  I'm also guessing that you >> need to specify the login credentials for an admin-level account.  Do >> you have an admin account in Windows 11?  No, not the Administrator >> account, but a user account you created that is in the Administrators >> security group.  You can see to which security group a Windows account >> is assigned by running: >> >> net users >> >> where is the Windows account you want to check its info.  At >> the bottom is the list of local [security] groups to which that account >> is associated.  To get a list of accounts, and to which security group >> they are assigned, run: >> >> wmic useraccount list brief >> >> To see which accounts (users) are in a specific security group, run: >> >> net localgroup administrators >> >> That will list who is in the Administrators security group.  If you run: >> >> net localgroup >> >> you can see which security groups are in your instance of Windows (to >> know which to specify to find out which users are under a specific >> security group). > > This information was found after a struggle of over a week, and hours of > online research while setting up my new computer to be able to connect > to my LAN's resources > > From a recent experience with the same symptoms I suspect there are two > possible reasons, assuming you owned the folder you were sharing. > > > 1.   Make sure that the groups mentioned in the Share tab of the folder > Properties contains EVERYONE as a user with the appropriate rights. > > > 2.  In recent HP and probably other brands, the local area LANs are > consider insecure, and by default the computer is prevented from > connecting to them. > > These lines when run as one string in the Terminal Admin, set the > parameters to allow the connection and use of LAN folders. > > reg add > HKLM\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters\ /f > /v RequireSecuritySignature /t REG_DWORD /d 0 > > reg add HKLM\SOFTWARE\Policies\Microsoft\Windows\LanmanWorkstation /f /v > AllowInsecureGuestAuth /t REG_DWORD /d 1 > > reg add > HKLM\SOFTWARE\WOW6432Node\Policies\Microsoft\Windows\LanmanWorkstation > /f /v AllowInsecureGuestAuth /t REG_DWORD /d 1 Sorry, But I wasn't able to add this to the registry on the laptop. Fokke