Path: csiph.com!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail
From: Fokke Nauta <fnauta@solfon.nl>
Newsgroups: alt.comp.os.windows-11
Subject: Re: Can't connect to laptop
Date: Mon, 12 May 2025 14:03:40 +0200
Lines: 97
Message-ID: <m8e6csFqrbdU1@mid.individual.net>
References: <m76dejFfqtkU1@mid.individual.net> <m7kccmFn1a4U4@mid.individual.net> <vv304n$1jfgf$2@dont-email.me> <m7kgd6FnqcsU1@mid.individual.net> <vv3b4g$1tvrf$1@dont-email.me> <m7rgh7Frbb7U1@mid.individual.net> <vva4is$9ih8$1@dont-email.me> <m80ljaFm0ceU1@mid.individual.net> <vvfja1$10ogs$1@dont-email.me> <m8157aFoa6vU2@mid.individual.net> <vvfp2q$126fa$1@dont-email.me> <m81gjlFq6t7U2@mid.individual.net> <vvivph$22jq7$1@dont-email.me> <m868gsFipppU1@mid.individual.net> <vvkt5m$2q38r$1@dont-email.me> <vvl876.tmg.1@ID-201911.user.individual.net> <m86osvFlb4eU1@mid.individual.net> <vvlft7$2uube$1@dont-email.me>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
X-Trace: individual.net A8smPI6etTHobPe0R90NKABCXo7nYbdgiSKiqOCWZyupOm+SUL
Cancel-Lock: sha1:iP0Vsw0KsGe7CAiJ/rDJ1BRhKY0= sha256:ALforuh7Wg6I3VDIMwR8Jejvwnd6JwuYq3uxcTWWcFE=
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: <vvlft7$2uube$1@dont-email.me>
Xref: csiph.com alt.comp.os.windows-11:19225

On 09/05/2025 20:01, Paul wrote:
> On Fri, 5/9/2025 12:30 PM, Fokke Nauta wrote:
>> On 09/05/2025 15:50, Frank Slootweg wrote:
>>> Paul <nospam@needed.invalid> wrote:
>>>> On Fri, 5/9/2025 7:50 AM, Fokke Nauta wrote:
>>>>> On 08/05/2025 21:13, Paul wrote:
>>> [...]
>>>>>> Start : Run : services.msc
>>>>>>
>>>>>> Check "Function Discovery Provider Host"
>>>>>>
>>>>>> Mine is Running, but the status in services.msc is
>>>>>> not displayed properly. You can check the status
>>>>>> of it using the tiny dialog shown on the right.
>>>>>>
>>>>>> [Picture]
>>>>>>
>>>>>> https://i.postimg.cc/0QDDCk27/Function-Discovery-Provider-Host-W11.gif
>>>>>>
>>>>>> Paul
>>>>>
>>>>> Checked it on my W10 pc. It's running, startup type is manual.
>>>>>
>>>>> Fokke
>>>>
>>>> Yet your discovery screen does not render in File Explorer.
>>>>
>>>> Mine works here, even if the account is a Limited User.
>>>>
>>>>      [Picture]
>>>>
>>>>       https://i.postimg.cc/pTctmN38/discovery-limited-user.gif
>>>
>>>     FWIW, also on my systems (Windows 11 and 10) network discovery is
>>> flaky, while 'Function Discovery Provider Host' is (manual and) running.
>>>
>>>     For example on my Windows 11 system, I only see my own system (with
>>> WSD), but not my wife's Windows 10 system. And if I do a 'Refresh
>>> "Network" (F5)', it doesn't even show my own system anymore.
>>>
>>>     BUT, *Network Shares* work just fine. That's why I think there is (and
>>> was) too much emphasis on Fokke's network discovery 'problem' and too
>>> little on why \\<computer>\<share> apparently *silently* [1] fails when
>>> he tries to access a share on his wife's Windows 11 laptop.
>>>
>>> [1] I find that very hard to believe, but Fokke is adamant that that's
>>> the case.
>>
>> What would you think that is the case, then?
>>
>> Fokke
> 
> I gave a suggestion, to debug at the network level and see the error
> code that is being sent back.
> 
> As a group, we can give a summary of the "visible" levers in
> the scheme. It will always be possible for us to miss something.
> There are seven services that have to be enabled for file sharing
> to work.
> 
> In a better era, I might have said to do a Repair Install, to
> reset the services to their defaults and so on. But these days,
> with the problems the OS has (my crashes are back), I don't feel
> confident in that, to even suggest it. A Repair Install is
> done by running "Setup.exe" on the DVD you used to install the
> current version of the OS. Use "winver" to determine which
> version of OS that is (22H2 likely 19045 on a Win10). It is even
> possible that a recent Patch Tuesday update has broken it. The
> following examples would be for the repair of the Win10 on
> my daily driver (this) machine.
> 
> Example:
> 
> 1) I locate the version of Windows used for all Win10 Repair.
> 
>     S:\DVD\Win10_22H2_English_x64v1.iso
> 
> 2) I right-click that and select Mount. If running Imgburn, the Mount
>     option is removed and replaced by Imgburn, so you need to "Open with Explorer"
>     and then File Explorer will mount it.
> 
> 3) From the new drive letter (which is the mounted DVD), locate Setup.exe and
>     run it. It would likely help if the user belongs to the Administrator group,
>     but I suppose an elevation dialog for the Administrators Group account would
>     appear if it does not want to run.
> 
> 4) After the install, certain advertising settings will be reset to their
>     normal irritating levels. You will need to correct the advertising settings.
>     Other settings will mostly be kept. Your files and programs will be preserved.
> 
>     Paul
> 
Thanks, Paul.
But I'm not going to do a repair install.

Fokke