![]() This is all still based on the old, old, old NetBIOS protocol. There is some arcane election process that happens whereby the machines on the network segment determine which one is going to be the Master Browser. If both of those options are on, then read on.Įven in Windows 10, for work group (not domain) networking, there stills exists a Master Browser, a machine that maintains the list of the other peers of the work group on the network segment. This happens if the “file and printer sharing” option is off. When I’ve clicked on “Network” in File Explorer, I sometimes get a warning that the machine won’t be discoverable if file sharing is disabled. ![]() I’m certain the network discovery option must be turned on, but not sure on the file and printer sharing. Networking isn’t my strong suit, so I’m not sure how much of this I really understand, but here goes.įirst, on the problem machine, if you open Settings -> Network and Internet -> Sharing options, are both the “Turn on network discovery” and “Turn on file and printer sharing” options selected. So my question is why won’t it just show up with out this extra step.Īdditional Info: all machines are configured for PowerShell Remoting and all canīe reached to execute PS commands remotely. Now all of the machines can access the DellXPS137000 by typing \\DellXPS137000 intoįile Explorer’s address line and once you do that it then shows up in the Network You’ll notice that none of the machines enumerated the DellXPS137000 including itself. Services: FunctionDiscoveryProviderHost (fdPHost) &įunctionDiscoveryResourcePublication (FDResPub) set to start Automatically on all machines. JanetsLaptop Laptop 18363.836 DellXPS8920,DellXPS8700,JanetsLaptopĪll machines connected via ethernet cable using giga-bit adapters over Cat5e cable. Machine Type WindowsVersion Enumerated in F-Explorer Network.ĭellXPS8920 Desktop 18363.836 DellXPS8920,DellXPS8700,JanetsLaptopĭellXPS8700 Desktop 18363.836 DellXPS8920,DellXPS8700,JanetsLaptopĭellXPS137000 Laptop 18363.836 DellXPS8920,DellXPS8700,JanetsLaptop The other three also do not enumerate it in File Explorer either. I’m stilled stumpped as to why when I disable SMBv1 on all my machines,ģ of them behave as they should but one refuses to enumerate itself and Admins out there if this is the Carry on with a large scale Corporate Deployment, thank goodness my role is way more mundane but at times equally frustrating lol □ Never used Home Groups Per Se only as a quick fix for networking problems then back out the errant Machines one at a time, same with enabling a whole Swath of Services as per link above, just enable them all then back out, 1 Service at a time until you get a minimal working Network, I would imagine there’s a few Hairless Sys. Not entirely enamoured with what I am reading about Win10 1903,4,5 whenever it shows up? As it seems to be a pattern of Network Woes since Home Group’s demise 1709? methinks. Yes young fella I feel your pain this is the “Song and Dance” I had to go through with Win10 1809 and partially with 1803 on a Home Network: Mercifully as of Win10 1809 Winver 17763.195 none of that seems to apply anymore, Home version doesnt seem to need the Create desktop Shutdown Button Dodge or the use of a shutdown Batch file with GPOL. ![]() Just though you’d all like to know…or not.įYI: I initiated this upgrade due to a problem I was having with 1803 and I am glad to report that at least that problem is fixed in 1809! Of course this kind of beggars the setting up of having a common userID/Password on all your machines and making your shares available to Authenticated Users as I like to do. You can put credentials to access the the computer in the Credential Manager and then it will show up in the list (SMB setting not important here).\DellXPS8700 and it will then show up on the list until the next reboot. You can access other computers via file explorer’s address bar, e.g.Now there are work arounds to this problem beside enabling SMBv1. Yep, Microsoft can’t seem to get their act together to support recognized security standards in their base software product, i.e. Note: a reboot is required every time you change the SMBv1 setting.Īlso the Dell1564 is running Insider Build 18309.rs_prerelease 181220-1256. I progressed to doing a little testing with another area where SMBv1 causes problems that being enumeration of network computers in file explorer. So what changed, I poked around for a while and discovered that the SMBv1 protocol was disabled, the new default as of 1803 I think. $x = (("WinNT://$((Get-WMIObject Win32_ComputerSystem).Domain)").Children.path) It errored out because this statement returned a NULL value: ![]() One of the first things I did was run a PowerShell program I wrote to add Trusted Hosts to my list (always cleaned out by a new install). Today I updated my production machine to 1809 and commenced to do a little testing.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |