Networking issues since upgrading to Win 10 1903. Public settings.

Page 2 of 2 FirstFirst 12
  1. bro67's Avatar
    Posts : 7,349
    Mac OS Mojave
       #11

    Make sure that Guest account is enabled.
      My ComputersSystem Spec

  2. clam1952's Avatar
    Posts : 706
    Windows 10 Pro
       #12

    FuSchnickens said: View Post
    I found this when looking thru some stuff earlier. What do you think of this?

    Fix PCs no longer recognized in network after Windows 10 version 1803 upgrade - gHacks Tech News
    Done all that, ages ago, still didn't stop the problem from reoccurring though.
      My ComputersSystem Spec

  3. Caledon Ken's Avatar
    Posts : 15,670
    Windows 10 Pro x64 Build 1809
       #13

    Those fixes in ghack are listed in tutorial.

    Did you follow the tutorial I posted.
      My ComputerSystem Spec


  4. Posts : 22
    Win 10
    Thread Starter
       #14

    Yes I just managed to get them all working. All 3 PC's networked together visable and with full access. All I had to do was enable SMB1. So with Windows 10 1903 anyone whose running it won't be able to network shared folders at all unless then know to enable smb1? Shame on MS for doing this and breaking everyone's network who upgraded to 1903.
      My ComputerSystem Spec

  5. Caledon Ken's Avatar
    Posts : 15,670
    Windows 10 Pro x64 Build 1809
       #15

    They are doing it because of the risk associated with SMB1.

    This way they know the client turned it on and when the brown stuff hits the fan they can say not me.

    clam1952 said how he is working around it, I do backup to my NAS with specific IP addresses, others map.

    It would be nice if they could get explorer to work with a higher level of SMB that does not have the exposure.

    I'm glad it is working.
      My ComputerSystem Spec

  6. Pendaws's Avatar
    Posts : 324
    Windows 10 Pro 64bit 1809 (17763.55)
       #16

    My windows 10 Computer that has had no issues with this (version 1903, 18362.239) but, yesterday the onboard NIC died.
    Of course, it ruined my network and since then I have not been able to view either my NAS or 2 WD My book live units in the
    Network. I have done all the enable of SMB 1, I went into the options and enabled ALL the SMB 1 protocols and the SMB direct,
    made PowerShell changes and I even have a HOSTS file that has all the IP address for my network and STILL, NOTHING.

    Does anyone have an Idea please?
    Attached Thumbnails Attached Thumbnails Networking issues since upgrading to Win 10 1903. Public settings.-network.jpg  
      My ComputerSystem Spec


  7. jimbo45's Avatar
    Posts : 7,844
    Windows / Linux : Centos, Ubuntu, OpenSuse
       #17

    Hi there
    Presumably you either replaced the NIC or added a USB type device.

    I'd power the whole kybosh down including router and any phones / smart TV's etc. Wait 10 mins and then start things up again.

    If you have any LINUX type NAS systems then in the samba file for older Linux distros sill reliant on SMB1 you need to change in the smaba.conf file the line (or add it if it isn't there) to maxprotocol = Nt1 as shown below :


    [global]

    # ----------------------- Network-Related Options -------------------------

    #
    # hosts deny = the hosts not allowed to connect. This option can also be used on
    # a per-share basis.
    #
    workgroup = WORKGROUP <================Your network name
    server string = Samba Server Version %v
    smb ports = 139 445 <========== optional -- I set these as I have these enabled in Router firewall

    netbios name = REFUR <=============== Computer name
    max protocol = NT1 <================== This line

    ............

    This is assuming you have Samba v4 and above on your NAS

    For Non Linux type of NAS's that don't use SAMBA or pure Windows just ignore the above SAMBA adjustments required.

    Cheers
    jimbo
      My ComputerSystem Spec

  8. Pendaws's Avatar
    Posts : 324
    Windows 10 Pro 64bit 1809 (17763.55)
       #18

    Thanks for the reply. I did as you suggested but STILL no joy. As to the samba file, where do I find it?
    I did ask the people at Buffalo but I got nowhere with that. I asked how to make the NAS work with SMB2 or 3 but?
    Any more help you could give would be very much appreciated.
      My ComputerSystem Spec


  9. Posts : 1
    Ubuntu 18.04 LTS
       #19

    jimbo45 said: View Post
    Hi there

    If you have any LINUX type NAS systems then in the samba file for older Linux distros sill reliant on SMB1 you need to change in the smaba.conf file the line (or add it if it isn't there) to maxprotocol = Nt1 as shown below :


    [global]

    # ----------------------- Network-Related Options -------------------------

    #
    # hosts deny = the hosts not allowed to connect. This option can also be used on
    # a per-share basis.
    #
    workgroup = WORKGROUP <================Your network name
    server string = Samba Server Version %v
    smb ports = 139 445 <========== optional -- I set these as I have these enabled in Router firewall

    netbios name = REFUR <=============== Computer name
    max protocol = NT1 <================== This line

    ............

    This is assuming you have Samba v4 and above on your NAS

    For Non Linux type of NAS's that don't use SAMBA or pure Windows just ignore the above SAMBA adjustments required.

    Cheers
    jimbo
    I have a Linux PC with a Samba share that stopped being accessible by my Win10 box after the upgrade to 1903. I had to edit the /etc/samba/smb.conf file on that Linux box as per per above to make it visible again.
      My ComputerSystem Spec

  10. jimbo45's Avatar
    Posts : 7,844
    Windows / Linux : Centos, Ubuntu, OpenSuse
       #20

    Pendaws said: View Post
    Thanks for the reply. I did as you suggested but STILL no joy. As to the samba file, where do I find it?
    I did ask the people at Buffalo but I got nowhere with that. I asked how to make the NAS work with SMB2 or 3 but?
    Any more help you could give would be very much appreciated.
    Hi folks

    @Pendaws

    Note on Windows you said you enabled ALL the SMB1 stuff --you need to UNCHECK the automatic removal SMB1 box. Why that option is even there when dealing with SMB1 I don't know -- just causes extra obfuscation.
    That might fix your stuff without having to mess around with SAMBA but if you do have to fiddle with SAMBA :

    The samba file is usually found on Linux NAS type systems under /etc/samba and the file itself is /etc/samba.conf.
    Start searching with a file manager starting at top level root which is '/'

    if you have a graphical file manager ("explorer") on your box then you should see something like this - and the samba directory is easily "findable". I'm running the KDE plasma GUI on a Linux Arch distro on this box with Dolphin as the standard file explorer -- those running a GNOME (another popular desktop GUI on Linux systems like UBUNTU etc) then there's the almost identical Nautilus -- other GUI's will have very similar graphical file managers / browsers.

    Networking issues since upgrading to Win 10 1903. Public settings.-screenshot_20190910_090040.png


    If you don't have a graphical file manager then as root cd / then ls then cd to the /etc/samba and its a hideous pain but you'll have to use a command line editor such as vi or nano to edit the file --good luck with that one !!!!!!! It's hideous if in an emergency you ever have to use it !!!!.

    After editing it test the file for correctness with the testparm command.

    For getting SMB2/3 working - that depends on your hardware and the OS running in the NAS - some of the older network cards - especially if connecting to network via older wired cards won't support anything higher than the old SMB1 protocol (for some strange reason in later versions of samba you need to set to NT1). Ensure any Windows systems you have also have SMB1 enabled.

    editing the samba file you need to be root (su) or sudo.

    Cheers
    jimbo
    Last edited by jimbo45; 1 Week Ago at 06:48. Reason: Uncheck SMB1 automatic removal box too
      My ComputerSystem Spec


 
Page 2 of 2 FirstFirst 12

Related Threads
Windows 10 1903 (aka the May 2019 update) introduced a new networking tray icon, which gets shown when the PC is offline: 235633 However, I don't like this icon, because first, it also shows when the PC is connected to a network, but doesn't...
Local profile issue after upgrading to 1903 in User Accounts and Family Safety
I didn't have this issue on any of the test work computers that I upgraded so I thought hey might as well do my home computer as well. After the 1903 upgrade was finished and I logged on (username/password still worked so that's something) I...
Solved My saga of upgrading from Ver. 1809 to 1903 in Installation and Upgrade
This is how I managed to update my Win10/64 system from Ver. 1809 to 1903. My system has an Intel 17-8700 CPU with 16 GB RAM and a 128GB Samsung SSD boot drive installed on an ASUS P8Z77-M motherboard. Before attempting the update I made a complete...
Ok, just upgraded to Windows 10 this week and been bashing my head bloody for two days on networking issues. What on the green Earth are my networking credentials in Win10? I have a Microsoft account I'm logging into Win10 pc with (which I hate but...
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 00:12.
Find Us