From: this@ddress.is.invalid
Fokke Nauta wrote:
> On 18/12/2025 17:12, Frank Slootweg wrote:
> > Fokke Nauta wrote:
> >> On 12/12/2025 20:11, Fokke Nauta wrote:
> >>> Hi all,
> >>>
> >>> I have a W10 Pro PC. In our network we have two W11 Pro Laptops. From my
> >>> PC I can see the laptops, but I can't open them and can't see their
> >>> files. On the laptops they can see a private network, and in the
> >>> settings on a private network all is shared.
> >>> But from my pc I can't see their shares. What can I do to see the shares
> >>> on the laptops? What else can I do on the laptops to open them?
> >>>
> >> When I try to open de laptops on my PC, I get the message Windows cannot
> >> access \\laptop. The error code is 0x80070035. I searched the code on
> >> the internet and followed the instructions. There was no result.
> >> Other instructions on the laptops:
> >> Network discovery = on.
> >> Setup network connected devices automatically.
> >> File- and printersharing = on.
> >> Network profile type = private network.
> >
> > New wild guess: When you try to access the Windows 11 laptops from the
> > Windows 10 PC, could it be that the laptops are *sleeping*?
>
> No, ofcourse not. They are awake anyway, and before trying to connect, I
> logged in on the laptops again. If you don't use them for a short while,
> you need to log in again.
Well, both for 'Plugged in' and 'On battery' the 'Recommended' screen
off and sleep settings are the same and *only 5 and 3 minutes*, so uou
have only very little time to test, before they go to sleep again.
> > After all, they are laptops and are probably set to sleep after some
> > time, even if they are connected to power.
>
> Yes. But no problem.
Says you, without checking.
> > If they *are* sleeping, you will get the exact error you're getting!
>
> They didn't sleep.
Says you, without checking.
> > I just tried that on my network and a sleeping remote host will cause
> > this exact same error [1].
> >
> > You said "From my PC I can see the laptops," and that is quite
> > possible, even if the laptops are sleeping, because the Network
> > information is locally cached (see the nbtstat command). So in this
> > scenario, you would *see* the laptops, but because they are sleeping,
> > they are *not accessible*.
> >
> > So test this scenario. Set the laptops to never sleep or not sleep for
> > several hours and try again.
>
> No, that doesn't make any sence. The laptops were alive and working when
> I tried to contact them.
Did you *see* the laptop screen still on when you tested or did you
just *assumed* it was still alive?
Why don't you just *test* it (by making the timeouts longer)? What do
you have to lose? :-(
> > [1]
> > "Windows cannot access \\
> >
> > Check the spelling of the name.
>
> The names and passwords are correct. But when I try to contact them, I
> don't even get the screen where you can fill in the user name and password.
That is, because, as Paul said *and* the actual error message says,
there is a *network* problem which *precedes* the authentication (name
and password) phase. See the next two lines of the error message:
> > Otherwise, there might be a problem with
> > your network. To try to identify and resolve network problems, click
> > Diagnose.
So even if there was no sleep problem, you should check for a network
problem, which apparently gives the exact same error message and code as
when the remote is sleeping.
I think the 'nbtstat' command which I mentioned, can probably help
with that, but given your uncooperative attitude, I'm not going to hold
your hand.
[About clicking on '[Diagnose']:
> I did. It didn't answer, diagnose was not possible. In Details I found
> the error code.
>
> > /\ Hide details [Diagnose] [Cancel]
> >
> > Error code: 0x80070035
> > The network path was not found."
--- SoupGate-Win32 v1.05
* Origin: you cannot sedate... all the things you hate (1:229/2)
|
