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: Wed, 7 May 2025 10:57:15 +0200
Lines: 62
Message-ID: <m80ljaFm0ceU1@mid.individual.net>
References: <m76dejFfqtkU1@mid.individual.net> <vuq7c6$1gueo$1@dont-email.me> <m7h095F68jtU9@mid.individual.net> <vv081j$33f1u$1@dont-email.me> <m7jjboFiuinU5@mid.individual.net> <m7jst4FkdshU2@mid.individual.net> <vv2inm$1840g$1@dont-email.me> <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>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
X-Trace: individual.net LrQomkKBpXrRyobFVyv91g37uSua90WXaVDF1fMPBoI6DjVTx0
Cancel-Lock: sha1:Yi8EfC5rTHu8Lb8mXb2I2PL9SQo= sha256:HnuttnNJ6lPBtimQRUr9Azjlj0/kti0QheFYdfpqbMo=
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: <vva4is$9ih8$1@dont-email.me>
Xref: csiph.com alt.comp.os.windows-11:19119

On 05/05/2025 12:40, Java Jive wrote:
> On 2025-05-05 11:00, Fokke Nauta wrote:
>> On 02/05/2025 22:49, Java Jive wrote:
>>> On 2025-05-02 19:15, Fokke Nauta wrote:
>>>> On 02/05/2025 19:41, Java Jive wrote:
>>>>> On 2025-05-02 18:06, Fokke Nauta wrote:
>>>>>>
>>>>>> On 02/05/2025 15:52, Java Jive wrote:
>>>>>>>
>>>>>>> On 2025-05-02 13:42, Fokke Nauta wrote:
>>>>>>>>
>>>>>>>> On 02/05/2025 11:59, Fokke Nauta wrote:
>>>>>>>>>
>>>>>>>>> On 01/05/2025 18:38, Java Jive wrote:
>>>>>>>>>>
>>>>>>>>>> Also, on a non-problem PC, select Network in Explorer, in the 
>>>>>>>>>> right-hand windows pane ...
>>>>>>>>>>
>>>>>>>>>>      <rt-click> 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.
>>>>>>>
>>>>>>> Did you get around to trying this?  As other possibilities fall 
>>>>>>> by the wayside, this one assumes greater importance.
>>>>>
>>>>> Still no answer to this?
>>>>>
>>>>
>>>> Yes, I did.
>>>> Didn't make any difference.
>>>
>>> I wasn't expecting it to make a difference, I was hoping it might 
>>> show useful information which you would then relay on to us.  What 
>>> method is discovering ...
>>>      The non-problem PCs;
>>>      The problem PC?
>>>
>> What do you mean by that?
> 
> Follow the instructions still quoted above to display the column for the 
> discovery method used to find each PC listed in Network, and then tell 
> us what method is listed in that column for both a non-problem PC and 
> the problem PC.  What are they in each case, and, in particular, are 
> they different?
> 

Yes, they are different. On my wife's laptop I enabled 64, on my own pc 
it's 80, and on the server pc it is 240. I didn't check the 3rd pc and 
my laptop.

Fokke