2 Win 10 PCs can't network properly - What am I overlooking?

Page 2 of 2 FirstFirst 12
  1.    #11

    master list


    Let me echo the request of the person who started this thread for a master list of all settings.

    I have wasted incalculable hours over the past years since windows 10 arrived trying to get my home LAN up and running with mixed success. About a year ago I seemed to have succeeded and generated my own master list. But at some point, without making any changes to these settings, it has reverted to a chaotic some PCs cab see some but with no consistency.

    If I was not so invested in other Microsoft software I would have abandoned Windows long ago!
      My ComputerSystem Spec

  2.    #12

    Danield said: View Post
    You are describing a situation that is exactly the same as mine, both D and L on 1903. To make the situation worse, from day to day, the situation will go from good to bad to good again, and you'll never know what you're going to get. None of the tutorials on 10 Forums on this subject apply any longer.
    Danield,

    All my systems are still on 1809. But these "it works, how come it doesn't work now, it works again but who knows why" cycles have been true for me since at least Win 7. That's why I find Windows networking so frustrating.

    One thing I have noticed is that there are so many "hidden" settings that can block your ability to see all the other systems in your home LAN in the networking icon window, even if you can successfully ping those other systems. Now add in the firewall, and it's a hot mess. I don't know if all these settings are documented in one place.

    FWIW, I started networking my PCs with LANTastic, back in the DOS 5/6 days, then Win for Networks 3.11. My kids grew up thinking that everyone's PCs were networking, and that was back in the 1980s.
    x509
      My ComputersSystem Spec

  3.    #13

    Looking for the same tutorial.
    I agree that the 10Forums pinned tutorial is not up-to-date!
      My ComputerSystem Spec

  4.    #14

    settings that work for me


    Shortly after my rant above, a "quality" update installed itself on my PCs which are now on version 1903, build 18362.175. You might think I have better things to do, but I decided to give fixing my network one more go and, what do you know, I succeeded (at least until the next update!). Recognizing that everyone's setup had differences, I thought it still might be useful for some to list the settings that worked for me this time.

    My network consists of six PCs (two of which are laptops), all running Win 10 together with two Synology NASs. I still have to access the latter as mapped network drives, but that is because of the first set of changes I made (see below). I am hoping to fix that be setting them up to connect using NFS, but that is going to have to wait for now

    Here are what I think are the relevant settings I either checked or changed

    1. Disabled NetBios on the network adapters on all PCs. This has the effect of forcing WSD as the network discovery message. Nothing else seems to be complaining about the lack of NetBios.


    2. In Windows features:
    • disabled SMB 1.0/CIFS file support and all three sub-options (I understand this is recommended for security reasons rather than for network functioning, unless you have any older SMB 1 relieant devices on your network)
    • left SMB direct enabled.


    3. In Windows services checked or set the following to auto and running (there are scads more but these are the ones that I remember from previous attempts that did have some degree of success:
    • function discovery provider
    • function discovery resource
    • internet connection sharing
    • Ipsec policy agent
    • network location awareness
    • workstation
    • SSDP discovery
      My ComputerSystem Spec

  5.    #15

    Have you tried running Network Reset on the affected PCs? This works for me at least for a while until something breaks the configuration.
      My ComputersSystem Spec

  6.    #16

    in reply to Steve C on network reset


    I have tried network reset in the past but it didn't fix my network issues then, which is why I started trying various, more specific system changes that were recommended. As far as I know, it would not by itself have made the changes that I reported above that did fix things so all my PCs could see each other and share files on the network without having to use mapping as a workaround. And my memory may be wrong on this, but I think it would have restored NetBios, which is one of the key changes that did fix things.

    But others might want to try it and see if it works now as a much simpler fix than digging into the system.
      My ComputerSystem Spec


  7.    #17

    .......it's almost like MS like to mess with us with their network setting........Sometimes my computers connect, most of the time it's a hit and miss affair....sometimes the computers are besties and play nice. It's the random fickle relationships that makes the Windows Network protocol so charming.......:)
      My ComputerSystem Spec

  8.    #18

    WalterG said: View Post
    Shortly after my rant above, a "quality" update installed itself on my PCs which are now on version 1903, build 18362.175. You might think I have better things to do, but I decided to give fixing my network one more go and, what do you know, I succeeded (at least until the next update!). Recognizing that everyone's setup had differences, I thought it still might be useful for some to list the settings that worked for me this time.

    My network consists of six PCs (two of which are laptops), all running Win 10 together with two Synology NASs. I still have to access the latter as mapped network drives, but that is because of the first set of changes I made (see below). I am hoping to fix that be setting them up to connect using NFS, but that is going to have to wait for now

    Here are what I think are the relevant settings I either checked or changed

    1. Disabled NetBios on the network adapters on all PCs. This has the effect of forcing WSD as the network discovery message. Nothing else seems to be complaining about the lack of NetBios.


    2. In Windows features:
    • disabled SMB 1.0/CIFS file support and all three sub-options (I understand this is recommended for security reasons rather than for network functioning, unless you have any older SMB 1 relieant devices on your network)
    • left SMB direct enabled.


    3. In Windows services checked or set the following to auto and running (there are scads more but these are the ones that I remember from previous attempts that did have some degree of success:
    • function discovery provider
    • function discovery resource
    • internet connection sharing
    • Ipsec policy agent
    • network location awareness
    • workstation
    • SSDP discovery
    Great starting point. I wonder if the moderators can make this point into a stickie.

    x509
      My ComputersSystem Spec


  9. Posts : 5
    Windows 10 V1803
       #19

    What about Windows HOME


    All my systems are running HOME edition. Windows only offers me SMB1/CIFS, not any of SMB, SMB2 or SMB3. If I kill SMB1 what then? Also my NAS interfaces on SMB/CIFS, though Windows discovery is Netbios. The article referenced from "iX Community" is interesting, but if I could make that work, I'm not sure about my NAS.
      My ComputerSystem Spec


 
Page 2 of 2 FirstFirst 12

Related Threads
Hello. So I completely replaced Windows 10 Home with Ubuntu. Ubuntu was not working well on my computer {Acer Aspire 2 in 1 convertible with 32 Gb SSD} so I decided to go back and install again Windows 10. After successful new clean...
Hello, I'm running a Windows 10 Pro 64bit desktop PC and I'm trying to map network drives. I have always been able to map them correctly using the IP Address of the drive and browsing. But for some reason recently (I realized I forgot to map a...
Long story short. I have a Asus Crosshair iv formula motherboard which has has Windows 7/8/10 installed on it before. I have used W10 preview since it first came out and I've been using the final version now. Internet has worked fine until today....
Since upgrading to Windows 10 Pro, I remain perplexed about this one issue that is plaguing my system: Almost every shut down is reported in the Windows 10 Reliability Monitor as the computer was not shut down properly. This happens on both shut...
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd
All times are GMT -5. The time now is 19:59.
Find Us