Hi all,

We have 4 W10 Pro pc's in our local network. They all have access to
eachothers shares. We have also 2 laptops with W11 pro. They have access
to the shares of the W10 pc's, but from the W10 pc's we can't access the
W11 laptops. Trying so we get an error message:
Just for one of the laptops: Windows cannot access \\HPFOKKE. Error code
0x80070035. The network path was not found. The other laptop gave the
same message (different hostname) and the same error code.
I searched on the internet and found
https://www.partitionwizard.com/partitionmanager/0x80070035.html
I tried all the tricks, but nothing helped.
One of you may have an idea?

Many thanks beforehand.
With regards,
Fokke Nauta

Fokke Nauta <usenet@solfon.nl> wrote:
> Hi all,
>
> We have 4 W10 Pro pc's in our local network. They all have access to
> eachothers shares. We have also 2 laptops with W11 pro. They have access
> to the shares of the W10 pc's, but from the W10 pc's we can't access the
> W11 laptops. Trying so we get an error message:
> Just for one of the laptops: Windows cannot access \\HPFOKKE. Error code
> 0x80070035. The network path was not found. The other laptop gave the
> same message (different hostname) and the same error code.
> I searched on the internet and found
> https://www.partitionwizard.com/partitionmanager/0x80070035.html
> I tried all the tricks, but nothing helped.
> One of you may have an idea?

Did you do the 'Turn on network discovery' and 'Turn on file and
printer sharing' on all computers, especially the target computers,
i.e. the laptops?

To me it seems that at least 'Turn on network discovery' has not been
done on both laptops.

BTW, did you click on the 'Diagnose' button of the 'Network Error'
popup? If so, what was the result? If not, why not?

Fokke Nauta wrote:

> We have 4 W10 Pro pc's in our local network. They all have access to
> eachothers shares. We have also 2 laptops with W11 pro. They have access
> to the shares of the W10 pc's, but from the W10 pc's we can't access the
> W11 laptops.

Try to determine if it's a name resolution issue, or a file serving
issue. Within a CMD.EXE window on one of the Win10 PCs, try the
following commands

nslookup HPFOKKE

ping HPFOKKE

Fokke Nauta wrote:
> Hi all,
>
> We have 4 W10 Pro pc's in our local network. They all have access to
> eachothers shares. We have also 2 laptops with W11 pro. They have access
> to the shares of the W10 pc's, but from the W10 pc's we can't access the
> W11 laptops. Trying so we get an error message:
> Just for one of the laptops: Windows cannot access \\HPFOKKE. Error code
> 0x80070035. The network path was not found. The other laptop gave the
> same message (different hostname) and the same error code.
> I searched on the internet and found
> https://www.partitionwizard.com/partitionmanager/0x80070035.html
> I tried all the tricks, but nothing helped.
> One of you may have an idea?

Your antivirus program on the W11 laptop might be preventing access,
particularly if it has a firewall component. Check its configuration.

--
Graham J

On 07/12/2023 16:29, Andy Burns wrote:
> Fokke Nauta wrote:
>
>> We have 4 W10 Pro pc's in our local network. They all have access to
>> eachothers shares. We have also 2 laptops with W11 pro. They have
>> access to the shares of the W10 pc's, but from the W10 pc's we can't
>> access the W11 laptops.
>
> Try to determine if it's a name resolution issue, or a file serving
> issue.  Within a CMD.EXE window on one of the Win10 PCs, try the
> following commands
>
> nslookup HPFOKKE

Server: fritz.box
Addresses: a lot
IP address: 192.168.1.150

>
> ping HPFOKKE

Request timed out.

Fokke

On 07/12/2023 18:41, Graham J wrote:
> Fokke Nauta wrote:
>> Hi all,
>>
>> We have 4 W10 Pro pc's in our local network. They all have access to
>> eachothers shares. We have also 2 laptops with W11 pro. They have
>> access to the shares of the W10 pc's, but from the W10 pc's we can't
>> access the W11 laptops. Trying so we get an error message:
>> Just for one of the laptops: Windows cannot access \\HPFOKKE. Error
>> code 0x80070035. The network path was not found. The other laptop gave
>> the same message (different hostname) and the same error code.
>> I searched on the internet and found
>> https://www.partitionwizard.com/partitionmanager/0x80070035.html
>> I tried all the tricks, but nothing helped.
>> One of you may have an idea?
>
> Your antivirus program on the W11 laptop might be preventing access,
> particularly if it has a firewall component.  Check its configuration.
>

Firewall has been cancelled. Antivirus has been switched off during the
test.

Fokke

On 07/12/2023 16:06, Frank Slootweg wrote:
> Fokke Nauta <usenet@solfon.nl> wrote:
>> Hi all,
>>
>> We have 4 W10 Pro pc's in our local network. They all have access to
>> eachothers shares. We have also 2 laptops with W11 pro. They have access
>> to the shares of the W10 pc's, but from the W10 pc's we can't access the
>> W11 laptops. Trying so we get an error message:
>> Just for one of the laptops: Windows cannot access \\HPFOKKE. Error code
>> 0x80070035. The network path was not found. The other laptop gave the
>> same message (different hostname) and the same error code.
>> I searched on the internet and found
>> https://www.partitionwizard.com/partitionmanager/0x80070035.html
>> I tried all the tricks, but nothing helped.
>> One of you may have an idea?
>
> Did you do the 'Turn on network discovery' and 'Turn on file and
> printer sharing' on all computers, especially the target computers,
> i.e. the laptops?

Yes, ofcourse on all pc's, and the laptops as well.

> To me it seems that at least 'Turn on network discovery' has not been
> done on both laptops.

Ofcourse it is on on both laptops.

> BTW, did you click on the 'Diagnose' button of the 'Network Error'
> popup? If so, what was the result? If not, why not?

Troubleshooting couldn't identify the problem.
Detailed information: No issues detected.

Fokke

Fokke Nauta wrote:

> Andy Burns wrote:
>
>> nslookup HPFOKKE
>
> IP address: 192.168.1.150

sounds likely, is that what ipconfig does say on that machine?

>> ping HPFOKKE
>
> Request timed out.

That's not unusual, default rule on incoming ping requests is to block them.

Fokke Nauta wrote:

> On 07/12/2023 18:41, Graham J wrote:
>> Fokke Nauta wrote:
>>> Hi all,
>>>
>>> We have 4 W10 Pro pc's in our local network. They all have access to
>>> eachothers shares. We have also 2 laptops with W11 pro. They have
>>> access to the shares of the W10 pc's, but from the W10 pc's we can't
>>> access the W11 laptops. Trying so we get an error message:
>>> Just for one of the laptops: Windows cannot access \\HPFOKKE. Error
>>> code 0x80070035. The network path was not found. The other laptop gave
>>> the same message (different hostname) and the same error code.
>>> I searched on the internet and found
>>> https://www.partitionwizard.com/partitionmanager/0x80070035.html
>>> I tried all the tricks, but nothing helped.
>>> One of you may have an idea?
>>
>> Your antivirus program on the W11 laptop might be preventing access,
>> particularly if it has a firewall component.  Check its configuration.
>>
>
> Firewall has been cancelled. Antivirus has been switched off during the
> test.
>
> Fokke

I have a similar problem where the laptop's setting to allow Windows
passwordless access will not stick and the desktop cannot connect. You can
select the setting, exit and then return and it has immediately become
unticked. As the setting sticks on my desktop, the laptop can access the
desktop. I have tried umpteen solutions from the web and nothing works.
Maybe it's something like that?

--
Bob
Tetbury, Gloucestershire, England

I'd give my right hand to be ambidextrous.

Fokke Nauta wrote:

> from the W10 pc's we can't access the W11 laptops

On a Win11 laptop, if you go to

start/settings/privacy & security/windows security/firewall & network
protection

which of the three network profiles (domain, private or public) says it
is active?

if you click on the one which is active, have you got the tickbox to
block all incoming connections (including those that would normally be
allowed) enabled?

On 07/12/2023 19:49, Bob Henson wrote:
> Fokke Nauta wrote:
>
>> On 07/12/2023 18:41, Graham J wrote:
>>> Fokke Nauta wrote:
>>>> Hi all,
>>>>
>>>> We have 4 W10 Pro pc's in our local network. They all have access to
>>>> eachothers shares. We have also 2 laptops with W11 pro. They have
>>>> access to the shares of the W10 pc's, but from the W10 pc's we can't
>>>> access the W11 laptops. Trying so we get an error message:
>>>> Just for one of the laptops: Windows cannot access \\HPFOKKE. Error
>>>> code 0x80070035. The network path was not found. The other laptop gave
>>>> the same message (different hostname) and the same error code.
>>>> I searched on the internet and found
>>>> https://www.partitionwizard.com/partitionmanager/0x80070035.html
>>>> I tried all the tricks, but nothing helped.
>>>> One of you may have an idea?
>>>
>>> Your antivirus program on the W11 laptop might be preventing access,
>>> particularly if it has a firewall component.  Check its configuration.
>>>
>>
>> Firewall has been cancelled. Antivirus has been switched off during the
>> test.
>>
>> Fokke
>
> I have a similar problem where the laptop's setting to allow Windows
> passwordless access will not stick and the desktop cannot connect. You can
> select the setting, exit and then return and it has immediately become
> unticked. As the setting sticks on my desktop, the laptop can access the
> desktop. I have tried umpteen solutions from the web and nothing works.
> Maybe it's something like that?
>

Yes, it looks like it's the same. Our laptops can access every pc, but
no pc can access the laptops.

Fokke

On 07/12/2023 19:56, Andy Burns wrote:
> Fokke Nauta wrote:
>
>> from the W10 pc's we can't access the W11 laptops
>
> On a Win11 laptop, if you go to
>
> start/settings/privacy & security/windows security/firewall & network
> protection
>
> which of the three network profiles (domain, private or public) says it
> is active?

Private

> if you click on the one which is active, have you got the tickbox to
> block all incoming connections (including those that would normally be
> allowed) enabled?

No, nothing is blocked. Incoming connections are enabled.

Fokke

Do you have one same user/password on every machine? Do you use this
users credentials to connect?

On 07/12/2023 19:35, Fokke Nauta wrote:
> On 07/12/2023 19:56, Andy Burns wrote:
>> which of the three network profiles (domain, private or public) says
>> it is active?
>
> Private
>
>> if you click on the one which is active, have you got the tickbox to
>> block all incoming connections (including those that would normally be
>> allowed) enabled?
>
> No, nothing is blocked. Incoming connections are enabled.

Are the laptops connected via Wi-Fi and the desktops connected with
cables? If so check that your Wi-Fi access point doesn't have "Guest
network", sometimes called "Internet-only access". "Guest mode",
"Isolated", "Restricted Access" or "Limited Access" enabled.

--
Brian Gregory (in England).

Fokke Nauta wrote:

> Andy Burns wrote:
>
>> On a Win11 laptop, if you go to
>>
>> start/settings/privacy & security/windows security/firewall & network
>> protection
>>
>> which of the three network profiles (domain, private or public) says
>> it is active?
>
> Private

And from that same page, if you go to advanced settings / inbound
rules, sort by name (if not already)

There are multiple "File and Printer sharing (..." rules, are they all
enabled (general tab) for private profile (advanced tab)?

Michael Logies wrote:
> Do you have one same user/password on every machine? Do you use this
> users credentials to connect?

And are all the PCs given the same workgroup name?

--
Graham J

On 12/7/2023 9:28 AM, Fokke Nauta wrote:
> Hi all,
>
> We have 4 W10 Pro pc's in our local network. They all have access to eachothers shares. We have also 2 laptops with W11 pro. They have access to the shares of the W10 pc's, but from the W10 pc's we can't access the W11 laptops. Trying so we get an error message:
> Just for one of the laptops: Windows cannot access \\HPFOKKE. Error code 0x80070035. The network path was not found. The other laptop gave the same message (different hostname) and the same error code.
> I searched on the internet and found https://www.partitionwizard.com/partitionmanager/0x80070035.html
> I tried all the tricks, but nothing helped.
> One of you may have an idea?
>
> Many thanks beforehand.
> With regards,
> Fokke Nauta

There are a couple suggestions here, if you're logged
into the W11 machines with an MSA.

https://superuser.com/questions/1768525/file-sharing-doesnt-work-both-ways-windows-10-and-11

But the condition of my subnet, is not good enough
to be used as a "demo of goodness". Stuff is still
slightly busted on it. Mine does not throw error codes,
but on a given day, something may go missing, and
there seems to be a dependency on which era of OS
you boot first, on a LAN where none of the clients
are running yet.

For best results, boot Win7 first, then Win10, then W11 machines.
This allows the Win7 machine to become Browse Master, and it may make
it slightly harder for Windows 11 to "elbow the other machines out of the way".
Windows 11 tries to shame the other machines, by showing all
the network icons. Yet, it does not necessarily offer up good
information, when a Windows 7 machine asks "Hey, Browse Master,
who is nearby?". It's unclear whether Browse Master elections
on the subnet, are carried out with the original unbiased
design intent. Originally, the elections were fair ones.

[Picture]

https://i.postimg.cc/fTYtKLF4/windows7-network-map.gif

In services.msc, the two services beginning with the word "Function"
should be running, for best file sharing name serving results. However,
my experience here is, the things are always running, so they hardly
offer an excuse for something to be broken. For HomeGroups to work, not
only did the two Function ones have to be running, there were a total
of around seven services total required, plus you needed IPV6 to make
the HomeGroups work. I don't think there are any (defunct) homegroups
on my LAN.

We could really use a Diagnostic utility, that could be started on all
PCs on the subnet, so that the Diagnostics could communicate with one
another, and gather "scenario" information to figure out what things
are working and what ones are busted. There was a commercial application
for the purpose, but I've searched and searched for this in the past,
and can find no evidence of it now. Don't even have a hint of a name
to work with. But I've caught a couple threads on forums, claiming
the thing was some sorta miracle worker. Whether it could tame a
newer OS like Windows 11, who knows. That might have been back in
WinXP era.

When it is just nameserving which is broken, you use IPaddresses
to reach shares. This requires (at minimum) executing something like
this, so you know your own IP address (perhaps obtained via DHCP from
your router).

ipconfig

Then when you go over to the other machine, you can use that numeric address, to
contact the ipconfig machine. Here are two Windows invocations, and two Linux
invocations.

explorer.exe \\192.168.2.100\shared
explorer.exe \\wallace\shared

nautilus smb://192.168.2.100/shared # This usually works, from Linux
# Other distros use nemo or thunar

nautilus , then Other Locations, Connect, //wallace/shared # And it may work. Symbolic may work
# from the Connect box.

Then, even if the damn icons don't play nicely, you
can still achieve a result. I plead guilty to using
this approach, much of the time here (IP addresses).

You can still run into conditions where those approaches
do not work. On a macintosh running early MacOSX, the
dialog box had a "race condition", where the attempt to
log to a Windows PC machine ended, before you even had time
to type in the password. There's no way to get around
a problem like that. If you then clicked the button to connect,
the PC machine had no idea what the hell you were trying to do,
because the state machine was now out of sync with the activity.

If you are absolutely desperate (and who isn't), you can use
Bluetooth "Send To" which uses fsquirt.exe and you can send
files between two PCs at 75KB/sec. Roughly the speed of a
floppy diskette :-) That even works with Linux. When I'm sending
config files between PCs, I have actually used that. You can't
send a Hollywood movie file that way, it would take too long.

Paul

Paul wrote:

> For best results, boot Win7 first, then Win10, then W11 machines.
> This allows the Win7 machine to become Browse Master, and it may make
> it slightly harder for Windows 11 to "elbow the other machines out of the way".

I thought newer O/S versions got more weight in elections?

On 07/12/2023 21:09, Brian Gregory wrote:
> On 07/12/2023 19:35, Fokke Nauta wrote:
>> On 07/12/2023 19:56, Andy Burns wrote:
>>> which of the three network profiles (domain, private or public) says
>>> it is active?
>>
>> Private
>>
>>> if you click on the one which is active, have you got the tickbox to
>>> block all incoming connections (including those that would normally
>>> be allowed) enabled?
>>
>> No, nothing is blocked. Incoming connections are enabled.
>
> Are the laptops connected via Wi-Fi and the desktops connected with
> cables?

Yes.

> If so check that your Wi-Fi access point doesn't have "Guest
> network", sometimes called "Internet-only access". "Guest mode",
> "Isolated", "Restricted Access" or "Limited Access" enabled.
>

No, that's OK. With an older Linux laptop it worked well.

Fokke

On 07/12/2023 21:09, Andy Burns wrote:
> Fokke Nauta wrote:
>
>> Andy Burns wrote:
>>
>>> On a Win11 laptop, if you go to
>>>
>>> start/settings/privacy & security/windows security/firewall & network
>>> protection
>>>
>>> which of the three network profiles (domain, private or public) says
>>> it is active?
>>
>> Private
>
> And from that same page, if you go to advanced settings  / inbound
> rules, sort by name (if not already)
>
> There are multiple "File and Printer sharing (..." rules, are they all
> enabled (general tab) for private profile (advanced tab)?
>
>

Yes, indeed they are.

Fokke

On 07/12/2023 20:54, Michael Logies wrote:
> Do you have one same user/password on every machine? Do you use this
> users credentials to connect?

No, on some pc's there are different usernames and passwords. The
laptops are also different.

Fokke

On 07/12/2023 21:44, Graham J wrote:
> Michael Logies wrote:
>> Do you have one same user/password on every machine? Do you use this
>> users credentials to connect?
>
> And are all the PCs given the same workgroup name?
>
>

Yes, sure.

Fokke

On 08/12/2023 11:46, Fokke Nauta wrote:
> On 08/12/2023 08:28, Paul wrote:
>> On 12/7/2023 9:28 AM, Fokke Nauta wrote:
>>> Hi all,
>>>
>>> We have 4 W10 Pro pc's in our local network. They all have access to
>>> eachothers shares. We have also 2 laptops with W11 pro. They have
>>> access to the shares of the W10 pc's, but from the W10 pc's we can't
>>> access the W11 laptops. Trying so we get an error message:
>>> Just for one of the laptops: Windows cannot access \\HPFOKKE. Error
>>> code 0x80070035. The network path was not found. The other laptop
>>> gave the same message (different hostname) and the same error code.
>>> I searched on the internet and found
>>> https://www.partitionwizard.com/partitionmanager/0x80070035.html
>>> I tried all the tricks, but nothing helped.
>>> One of you may have an idea?
>>>
>>> Many thanks beforehand.
>>> With regards,
>>> Fokke Nauta
>>
>> There are a couple suggestions here, if you're logged
>> into the W11 machines with an MSA.
>>
>> https://superuser.com/questions/1768525/file-sharing-doesnt-work-both-ways-windows-10-and-11
>>
>
> None of the answers is suitable in my situation.
>
>>
>> But the condition of my subnet, is not good enough
>> to be used as a "demo of goodness". Stuff is still
>> slightly busted on it. Mine does not throw error codes,
>> but on a given day, something may go missing, and
>> there seems to be a dependency on which era of OS
>> you boot first, on a LAN where none of the clients
>> are running yet.
>>
>> For best results, boot Win7 first,
>
> We don't have a W7 pc. All w10 pc's are running all day. The W11
> laptops are only powered on when we are going to use them.
>
> then Win10, then W11 machines.
>> This allows the Win7 machine to become Browse Master, and it may make
>> it slightly harder for Windows 11 to "elbow the other machines out of
>> the way".
>> Windows 11 tries to shame the other machines, by showing all
>> the network icons. Yet, it does not necessarily offer up good
>> information, when a Windows 7 machine asks "Hey, Browse Master,
>> who is nearby?". It's unclear whether Browse Master elections
>> on the subnet, are carried out with the original unbiased
>> design intent. Originally, the elections were fair ones.
>>
>>     [Picture]
>>
>>      https://i.postimg.cc/fTYtKLF4/windows7-network-map.gif
>>
>> In services.msc, the two services beginning with the word "Function"
>> should be running, for best file sharing name serving results. However,
>> my experience here is, the things are always running, so they hardly
>> offer an excuse for something to be broken. For HomeGroups to work, not
>> only did the two Function ones have to be running, there were a total
>> of around seven services total required, plus you needed IPV6 to make
>> the HomeGroups work. I don't think there are any (defunct) homegroups
>> on my LAN.
>>
>> We could really use a Diagnostic utility, that could be started on all
>> PCs on the subnet, so that the Diagnostics could communicate with one
>> another, and gather "scenario" information to figure out what things
>> are working and what ones are busted. There was a commercial application
>> for the purpose, but I've searched and searched for this in the past,
>> and can find no evidence of it now. Don't even have a hint of a name
>> to work with. But I've caught a couple threads on forums, claiming
>> the thing was some sorta miracle worker. Whether it could tame a
>> newer OS like Windows 11, who knows. That might have been back in
>> WinXP era.
>>
>> When it is just nameserving which is broken, you use IPaddresses
>> to reach shares. This requires (at minimum) executing something like
>> this, so you know your own IP address (perhaps obtained via DHCP from
>> your router).
>
> All pc's and the laptops are given a fixed IP address from the DGCP in
> the router, depending on their MAC addresses.
>
>>
>>     ipconfig
>>
>> Then when you go over to the other machine, you can use that numeric
>> address, to
>> contact the ipconfig machine. Here are two Windows invocations, and
>> two Linux
>> invocations.
>>
>>     explorer.exe  \\192.168.2.100\shared
>>     explorer.exe  \\wallace\shared
>>
>>     nautilus smb://192.168.2.100/shared                             
>> # This usually works, from Linux
>>                                                                      
>> # Other distros use nemo or thunar
>>
>>     nautilus , then Other Locations, Connect, //wallace/shared      
>> # And it may work. Symbolic may work
>>                                                                      
>> # from the Connect box.
>>
>> Then, even if the damn icons don't play nicely, you
>> can still achieve a result. I plead guilty to using
>> this approach, much of the time here (IP addresses).
>>
>> You can still run into conditions where those approaches
>> do not work. On a macintosh running early MacOSX, the
>> dialog box had a "race condition", where the attempt to
>> log to a Windows PC machine ended, before you even had time
>> to type in the password. There's no way to get around
>> a problem like that. If you then clicked the button to connect,
>> the PC machine had no idea what the hell you were trying to do,
>> because the state machine was now out of sync with the activity.
>>
>> If you are absolutely desperate (and who isn't), you can use
>> Bluetooth "Send To" which uses fsquirt.exe and you can send
>> files between two PCs at 75KB/sec. Roughly the speed of a
>> floppy diskette :-) That even works with Linux. When I'm sending
>> config files between PCs, I have actually used that. You can't
>> send a Hollywood movie file that way, it would take too long.
>>
>>     Paul
>>
>
> With regards,
> Fokke
>

Fokke Nauta wrote:

[snip]

From W10 PC to W11 laptop:

Can you ping the laptop by IP address? e.g. ping 192.168.1.100

Can you ping the laptop by name? e.g. ping HPFOKKE

Tell us if either of these works.

--
Graham J

On 08/12/2023 13:39, Graham J wrote:
> Fokke Nauta wrote:
>
> [snip]
>
> From W10 PC to W11 laptop:
>
> Can you ping the laptop by IP address?  e.g. ping 192.168.1.100

Yes, sure (192.168.1.158)

> Can you ping the laptop by name?  e.g. ping HPFOKKE

Also shure. But it says HPFOKKE.fritz.box. Mentioning the router.

> Tell us if either of these works.
>
>
>

Fokke