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: Mon, 28 Apr 2025 13:02:01 +0200 Lines: 83 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Trace: individual.net Ikq+1iXKhpWLkmu4DoMlvgJJWkb1zWJb/BT/BtbkdY/RXoFsO7 Cancel-Lock: sha1:zvKz6mxBTlFAloGkPqNoyR/u+b8= sha256:aKQ7REE7E68TouB2ju7KQ/xAZO8/123x4uq+f9RfhwI= 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:18758 On 27/04/2025 19:46, Graham J wrote: > Fokke Nauta wrote: >> Hi all, >> >> 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. > > I've come to this rather late, but you might work through this checklist: > > 1.  Do all the computers and other devices on the LAN get their IP > addresses by DHCP from a router?  If not, why not? Yes, they all get a fixed IP address from the router, depending on their ID. > 2.  All Windows machines should have the same "Workgroup" name. Yes, they have. > 3.  Ensure all 3rd party antivirus has any firewall disabled - at least > until you get the network to function. I can't find a way how to enable the firewall of Bitdefender. > 4.  The windows network type should be "Work", not "Private" or > "Public".  You may be able to get "Private" to work later, once you have > everything set up correctly.  Note: "Work" is only available on "Pro" > and higher versions of windows.  For home versions you must choose > "Private". It is pro. But all pc's and laptops are connected with Private. Where inbound connections are allowed. > 5.  All windows machines should - at the very least - have the same > username and password for their "Administrator" account.  Ideally they > should have a separate "User" account with limited permissions for > everyday use.  The folder(s) that you wish to have available over the > LAN should have their sharing permissions set correctly. No, they have not. Each pc or laptop has it's own username and password. > 6.  Test initially using ping from the command line.  Ping by IP address > until you can confirm that name resolution is working correctly. Windows > often fails to get this right so you may find it easier to stick with IP > addresses.  If your router supports "binding" then use it.ipconfig This works well. > 7.  Windows explorer should be able to find your networked devices in > its "Network" setting.  You may be prompted to enable this feature. > Initially look for shares by IP address, thus: \\\sharename - you > should be prompted for the username and password to give access to that > share.  You may be prompted to save these credentials.  Don't try to get > device letter mapping working until you can see the network share easily > and repeatably. This doesn't work. Nothing appears. > 8.  There are different versions of the SMB protocol that Windows uses > for file sharing.  Make sure you have the same (most modern) version on > all your machines. It's the same version as on another laptop with the same OS. And that is accessable. > 9.  Once you think you have it working, shut down everything.  Then > restart the router first, and other computers once the router has its > internet connection properly established.  Confirm that the networking > behaves properly.  Be aware that if a machine "sleeps" its networking > may not behave properly when it is "woken up". I see no reason to restart the router. It works well. Fokke