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: Fri, 9 May 2025 18:30:24 +0200
Lines: 49
Message-ID: <m86osvFlb4eU1@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>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Trace: individual.net MvS1AUDCCs5pxM9JIh6P3QofNAa4zA7tW+5bZ3onOug344rIlE
Cancel-Lock: sha1:R0WlGpjWj+A+HjQ+Zsi950JQIKE= sha256:sBJ+ndybDkTwnmeizOiB21oBXvBO+rnkS8YlMxIwxbA=
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: <vvl876.tmg.1@ID-201911.user.individual.net>
Xref: csiph.com alt.comp.os.windows-11:19199

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