W10 not discovering SAMBA devices starting in 10049 and Other Tips

I registered to let everyone know how I solved my problem with connecting to my NAS by NETBIOS name.

Starting with build 10049, my NAS would not appear when I go to "Network" in explorer. All of my Windows based PC's showed up but my NAS wouldn't.

Even when I try to connect to the share by UNC name "\WIFIHDD", Windows was unable to resolve the name.

I'm now on 10074 and was able to resolve this issue by forceably enabling NETBIOS over TCP/IP.

For those who don't know where this is:

1. Control PanelNetwork and InternetNetwork Connections
2. Right-Click on your network adapter and click on "Properties"
3. Double Click on "Internet Protocol Version 4"
4. Click on "Advanced..."
5. Click on the "WINS" tab
6. Select "Enable NetBios over TCP/IP"

The default option says it will fall back to NetBIOS over TCP/IP if the DHCP server doesn't provide it, but I think that logic might not be working right (or my router provides NetBIOS settings that I don't know about).


Other tips I've found working with 10049 and 10074:

• Setting Metered Connections:
  I tether to my phone so I need to make sure Windows Update won't try to download while I'm mobile.
  
  • 10049: The setting is in the "Show Available Connections" slide out. Right click on your wifi connection and select metered connection. "Show Available Connections" is available when you go to the "Metro" style wifi settings.
  • 10074: In the "Metro" style wifi settings, click on "Properties".
  
  
• Public/Private network:
  The only way I've found to set a network connection as private is to join a wifi network, then open "Explorer" and click on the Network link in the left hand column. The yellow warning bar on top will tell you that you are in a public network. Click on that, then click NO in the next dialog.
• Drivers not installing since 9926:
  I'm running Win10 on a WinBook TW801 which has very bad driver support. All of the drivers I have were backed up and contain only INF files, not setup files. Since the upgrade to 9926, after the first reboot, all the drivers failed to load correctly and I could not install them correctly. It would either complain about "File not found" or "Driver not made for this OS".
  
  My only solution for this problem was to prepare an Install.wim that already contains all my drivers by injecting them using DISM, then I performed a full install. Even then, the Intel video drivers would not install, but fortunately, Win10 will automatically install it when you connect to the Internet.

I registered to let everyone know how I solved my problem with connecting to my NAS by NETBIOS name.

Starting with build 10049, my NAS would not appear when I go to "Network" in explorer. All of my Windows based PC's showed up but my NAS wouldn't.

Even when I try to connect to the share by UNC name "\WIFIHDD", Windows was unable to resolve the name.

I'm now on 10074 and was able to resolve this issue by forceably enabling NETBIOS over TCP/IP.

For those who don't know where this is:

1. Control PanelNetwork and InternetNetwork Connections
2. Right-Click on your network adapter and click on "Properties"
3. Double Click on "Internet Protocol Version 4"
4. Click on "Advanced..."
5. Click on the "WINS" tab
6. Select "Enable NetBios over TCP/IP"

The default option says it will fall back to NetBIOS over TCP/IP if the DHCP server doesn't provide it, but I think that logic might not be working right (or my router provides NetBIOS settings that I don't know about).

I think someone posted that here around somewhere but thanks for sharing.

And Welcome to windowssh blog!