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: Fri, 2 May 2025 14:42:12 +0200 Lines: 177 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Trace: individual.net XEaR6t+inC85+32x3u3VsQm5iKKtSVKVz1sVyyW4jUP6qc4xGG Cancel-Lock: sha1:/FCiF60bvwH5oE68hd8nTucD+X4= sha256:Y5O/gYcoCLFb72/hqOgCsDJkK0uBp5RonbxyZjXDE8U= 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:18964 On 02/05/2025 11:59, Fokke Nauta wrote: > On 01/05/2025 18:38, Java Jive wrote: >> On 2025-05-01 11:21, Fokke Nauta wrote: >>> On 29/04/2025 11:49, Java Jive wrote: >>>> On 2025-04-27 10:58, 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. >> >> Meant to add previously that the correct interpretation of this error >> is (or at least was, and, in principle at least, should still be the >> same or correspondingly similar, even today) ... >> >>    Error Lookup tool from ancient XP version of VS: >>      The network path was not found >> >>    WinError.h documentation from same era (text version same as above): >>      8    Warning >>      7    Facility = Win32 >>      35   ERROR_BAD_NETPATH >> >> ... so that seems something of a contradiction in itself, you can see >> it in the network section of Explorer, but the error given is more >> appropriate to a situation where you wouldn't be able to see it. >> >> When in a command prompt you do ... >> >>      IPConfig /all >> >> ... on a non-problem PC and the problem PC, is the IP4 subnet the same >> in each case.  For example ... >> >>      2:30:39 D:\Temp>ipconfig /all >> >>      Ethernet adapter Local Area Connection: >>      ... >>      IPv4 Address. . . . . . . . . . . : 192.168.1.106 >> >> ... is the third quartile of the address, the 1 in my example, the >> same for both machines? > > Yes, ofcourse. For all machines. >> >> Previously VanguardLH suggested that you run the Event Viewer >> (eventvwr.msc) and look in the 'Application and Services Logs' >> section, whereas it rather surprised me that he didn't suggest to look >> in the section: >> >>      Windows Logs >>      System >> >> What can you see in there that looks relevant? Actually nothing >> Pay particular >> attention to entries with a yellow triangle containing an exclamation >> mark, which are warnings, and especially entries with a red circle >> containing an exclamation mark, which are errors. > > I'll check this out. >> >> Also, on a non-problem PC, select Network in Explorer, in the >> right-hand windows pane ... >> >>      in a blank area >>      Group by >>      More ... >>      Select 'Discovery Method' and give it a width of, say, 64 >>      Click OK >> >> Does the problem PC show the same discovery method as the other >> non-problem PCs? > > I'll check this out as well. >> >> I think it would be worth repeating this on the problem PC, even >> though I'm not sure how interesting the result would be, given that it >> can't see much, if anything. >> >>>>> This code says how to Enable NetBIOS over TCP / IP. I did and >>>>> restarted the laptop. >> >> I'm somewhat concerned by this, because historically this was enabled >> by default  - > > Yes, it was. > >> so I'm wondering if you've done something in there that has hindered >> rather than helped  -  but I don't have a Windows 11 build >> conveniently to hand  -  I would have to restore an image, and am in >> the middle of another job ATM  -  so I can't check on the default >> status of NetBIOS over TCP/IP in W11, but this is what I see in >> Windows 7, and I would expect W11 to be pretty much the same ... >> >>      Control Panel >>      Network and Internet >>      Network Connections >>          >>          Properties >>          Internet Protocol Version 4 (TCP/IPv4) >>              Properties >>                  Obtain an IP address automatically >>                  Obtain DNS server address automatically >>              Advanced >>                  WINS tab >>                  NetBIOS setting (in bottom section) >>                      Default: Use NetBIOS setting from DHCP server (etc) >> >>>> Follow-up questions roughly in decreasing order of likely relevance ... >> >> [snip] >> >>>> WiFi: >>>> >>>> Do you have more than one AP? >>> >>> No >> >> However, you do have a router and an AP, so does the router have WiFi >> as most do, and is it still enabled, in which case effectively you >> have two APs, and the question below still applies. > > The router doesn't have wifi. It has a cable connection to all pc's, the > AP and switches, exept to the laptops. They have wifi with the SP. >> >>>> If so, is the problem PC connecting to a different AP than the >>>> others?  If so, what happens when you move it to connect to the same >>>> AP as the others? >> >> [snip] >> >>>> Ping (included for trouble-shooting completeness, but, although >>>> normally it would be among the first things to do, here listed last, >>>> because given what is known, it's not likely to be relevant): >>>> >>>> Any difference between pinging from a non-problem PC to the problem >>>> PC, and from the problem PC to a non-problem PC? >>> >>> No >>>> >>>> Any difference between 'ping -4 ' & 'ping -6 ', again in >>>> each direction? >>> >>> I don't understand this. >> >> I'm trying to understand if your local network is having a problem >> with IPv6.  On the problem PC, what happens when you do ... >> >>      ping -4 >> >> ... and ... >> >>      ping -6 To my pc (192.168.1.141) it didn't work. Request timed out. To the server (192.168.1.140) it worked well. >> >> ... and similarly, on a non-problem PC, what happens when you do ... >> >>      ping -4 >> >> ... and ... >> >>      ping -6 This worked well. > Fokke >> >