Path: csiph.com!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail From: Fokke Nauta Newsgroups: alt.comp.os.windows-11 Subject: Re: Can't connect to laptop Date: Fri, 2 May 2025 12:02:46 +0200 Lines: 101 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Trace: individual.net ZZ1mqDjLW4mxrmTf9P/lzACwaMRKbFnHYHNVO1ET+XUNFQqOGr Cancel-Lock: sha1:KA5nsXfiVy10kLbhJMNS+KQ8+bo= sha256:/fJ7fg7ZTst5gvrccI0TYSu+nomZpGMezS8X63Mbw2Y= 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: Xref: csiph.com alt.comp.os.windows-11:18949 On 01/05/2025 20:16, VanguardLH wrote: > Java Jive wrote: > >> On the problem PC, go into Services.msc, and examine the Computer >> Browser service: >> >> It should have Status=Running, Startup Type=Manual or possibly >> Automatic (Delayed Start). >> >> Is it running? > > Computer browser is a legacy service for SMB 1.0 which Microsoft does > not install, by default, since Windows 10. SMB 1.0 is vulnerable. My > Windows 10 services.msc doesn't even list the Computer Browser service. > As per below, it is shown deselected (not installed). > > To reenable SMB 1.0: > - Run: optionalfeatures.exe > - Enable "SMB 1.0/CIFS File Sharing Support". > - Reboot. > > The WS-Discovery protocol showed up in Windows Vista. > > https://learn.microsoft.com/en-us/windows/win32/wsdapi/ws-discovery-specification-compliancehttps://learn.microsoft.com/en-us/windows/win32/wsdapi/ws-discovery-specification-compliance > https://en.wikipedia.org/wiki/WS-Discovery > > WS-Discovery does not prevent Computer Browser from finding and > populating the Network Neighborhood folder. With both running, and each > doing its discovery, the resulting list of computers and network devices > is twice as many: one list from each protocol. > > The following 2 services must be available, too, and Running status: > - Function Discovery Provider Host (Manual startup) > - Function Discovery Resource Publication (Auto triggered startup) > > I just realized the UPnP Device Host service must be running. Not > available, and not Manual startup, but in Started status. Per the > service's description: > > Allows UPnP devices to be hosted on this computer. If this service is > stopped, any hosted UPnP devices will stop functioning and no > additional hosted devices can be added. If this service is disabled, > any services that explicitly depend on it will fail to start. > > https://en.wikipedia.org/wiki/Universal_Plug_and_Play > > In the Network and and Sharing Center under Advanced settings, both > network discovery and file and printer sharing are turned off, but that > is because I'm using the Public networking profile. Sharing doesn't > work under the Public profile. Need to use the Private profile. Fokke > said his computers are using the Private profile, but he needs to check > network discovery and sharing are both enabled under that networking > profile. Previously he said network discovery was enabled, but I forgot > to ask about sharing in his Private profile. > > Sharing doesn't work across subnets which are treated as separate > networks (a network within a network). Sharing works via broadcast > traffic, but broadcast traffic doesn't travel across subnets. Fokke > says his computers are configured with static IP addresses by MAC at the > DHCP server in his router/modem. That's one way to do it, but I go into > the adapter settings on my hosts to define which static IP address they > get, the subnet mask, and do so for *both* IPv4 and IPv6. I have the > hosts assigned their static IP address, not have the DHCP server assign > IP addresses that are fixed per MAC address. Just in case his static > setup is incorrect, I'd switch to dynamic addressing on hosts and in the > DHCP server, and retest sharing. Once that is working, switch the > hosts, one at a time, back to static addressing. > > With Fokke specifying static IP addresses for his hosts, but he might > have them on different subnets. Don't know what static IP addresses > Fokke is using on his hosts. If the hosts are on different subnets, I > believe sharing will still work if you use IP addresses instead of > hostnames, like: > > \\ipaddrs\\sharename > > instead of: > > \\hostname\sharename > > Fokke said he could ping his wife's host from his, so I'd try using her > IP address instead of her computer name. If the hosts are on different > subnets, use IP addresses. In the past, WINS was used to resolve > NetBIOS hostnames across subnets. If UNC pathing works with IP > addresses, I'd map a drive to each share using: > > net use h: \\ipaddress\sharename /persistent:yes > (Drive h: is an example. Use whatever drive letter is available.) > > If Fokke can't get any of this flaky Microsoft sharing, login > credentials, and permissions to all work together, I'd get rid of wifi > in the setup, and go with wired connections (Ethernet cable) between the > hosts. If sharing still doesn't work, maybe go with an FTP server (on > the best managed host) or a NAS device, and put the files there to > share. Or go really old-school with sneakernet. I don't use different subnets. We have only 1 LAN, with IP addresses as 102.168.1.xxx Every system has it's own xxx code, depening on their MAC address. Fokke