DIY: Server 2022 to workstation post install settings

Discussion in 'Windows Server' started by damianfox, Nov 15, 2021.

  1. acer-5100

    acer-5100 MDL Guru

    Dec 8, 2018
    3,692
    2,658
    120
    Yeah in theory it should be enough (why not set it to smb3 anyway?)

    But what about the sevices in your PC

    Is the browser service installed / running?

    Are the fdphost and FDResPub enabled /running?

    The former should be enough to browse your LAN in SMB1 mode, the latter in SMB2/3

    Nothing prevents to have all of them running, they aren't mutually exclusive, the only reasons to disable them are security related, but usually this is not a problem in HOME/SOHO usage.
     
  2. adric

    adric MDL Expert

    Jul 30, 2009
    1,249
    1,324
    60
    What bothers me is that none of the suggested solutions were previously necessary for connecting to the NAS shares. The only good work-around without making possible security related changes to the affected systems seems to be to add the NAS name entry to the hosts file. That addition also brings back the NAS icon in the Network display along with a functioning Net view cmd using the NAS name. This is the only change I have now made. I guess I'll never know at what point what changed to cause the shares to fail.:(
     
  3. acer-5100

    acer-5100 MDL Guru

    Dec 8, 2018
    3,692
    2,658
    120
    #323 acer-5100, Mar 7, 2024
    Last edited: Mar 7, 2024

    The point is that SMB and all its variations are one of the most complicate matters of the whole windows OS.

    There are literally thousands of combinations since the introduction of SMB.

    And since the day one SMB was a source of vulnerabilities (in the early days very serious ones) and consequently MS kept changing the protocol making it stronger and more complicate. Add SAMBA (which was reverse engineered) to the mix, and you have an endless list of combinations of dialects, generations, bugs and so on.

    In short having a setup perfectly working that stops working after a CU isn't an unheard scenario
     
  4. RogerUK

    RogerUK MDL Novice

    Jan 16, 2010
    31
    10
    0
    Private vs Public networks maybe ?
     
  5. adric

    adric MDL Expert

    Jul 30, 2009
    1,249
    1,324
    60
    #325 adric, Mar 13, 2024
    Last edited: Mar 13, 2024
    Online March Server 2022 Update
    Code:
    ====================== W10UI v10.38 =======================
    [1] Target (x64): Current OS
    
    [2] Updates: "u:\$W0\$0_WUI\x64\_Srvr_21H2\Repo-Dir\Base"
    
    [3] DISM: "Host OS"
    
    [4] Enable .NET 3.5: NO
    
    [5] Cleanup System Image: YES      [6] Reset Image Base: YES
    
    [E] Extraction Directory: "d:\cab_30123"
    
    ============================================================
    Change a menu option, press 0 to start the process, or 9 to exit: 0
    
    ============================================================
    Running W10UI v10.38
    ============================================================
    02:16 AM
    
    ============================================================
    Extracting .cab files from .msu files...
    ============================================================
    
    02:16 AM
    1/1: windows10.0-kb5035857-x64-LCU-03.msu
    
    ============================================================
    Extracting files from update cabinets (.cab)...
    *** This will require some disk space, please be patient ***
    ============================================================
    
    1/3: Windows10.0-KB5011048-x64-Net481_Base9195.cab [NetFx]
    2/3: Windows10.0-KB5034611-x64-NDP481_CU-02.cab [NetFx]
    3/3: Windows10.0-KB5035857-x64.cab [Combined]
    4/5: Windows10.0-KB5035857-x64_inout.cab [LCU]
    5/5: Windows10.0-KB5035970-x64_inout.cab [SSU]
    
    ============================================================
    Checking Updates...
    ============================================================
    
    ============================================================
    Installing servicing stack update...
    ============================================================
    
    Deployment Image Servicing and Management tool
    Version: 10.0.20348.1
    
    Image Version: 10.0.20348.1
    
    Processing 1 of 1 - Adding package Package_for_ServicingStack_2334~31bf3856ad364e35~amd64~~20348.2334.1.1
    [==========================100.0%==========================]
    The operation completed successfully.
    
    ============================================================
    Installing updates...
    ============================================================
    02:21 AM
    
    Deployment Image Servicing and Management tool
    Version: 10.0.20348.1
    
    Image Version: 10.0.20348.1
    
    Processing 1 of 2 - Adding package Package_for_KB5011048~31bf3856ad364e35~amd64~~10.0.9195.7
    [==========================100.0%==========================]
    Processing 2 of 2 - Adding package Package_for_DotNetRollup_481~31bf3856ad364e35~amd64~~10.0.9224.1
    [==========================100.0%==========================]
    The operation completed successfully.
    
    Deployment Image Servicing and Management tool
    Version: 10.0.20348.1
    
    Image Version: 10.0.20348.1
    
    Processing 1 of 1 - Adding package Package_for_RollupFix~31bf3856ad364e35~amd64~~20348.2340.1.8
    [==========================100.0%==========================]
    The operation completed successfully.
    
    ============================================================
    Removing temporary extracted files...
    ============================================================
    
    
    ============================================================
       Finished
    ============================================================
    
    02:47 AM
    
    ============================================================
    System restart is required to complete installation
    ============================================================
    
    
    Press 9 or q to exit.
     
  6. atgpud2003

    atgpud2003 MDL Addicted

    Apr 30, 2015
    522
    85
    30
    You need to Server Manger, then next step go to Manage (right up corner.) , then go to Add Roles and Features , then click Next 3 times til' Features Scroll down until you see SMB 1.0/CIFS File Sharing Support Click check mark then click Next, then Install..

    This will allow access to any of your QNAP, ASUSTOR and other NAS devices.. It works for me..

    ATGPUD2003
     
  7. adric

    adric MDL Expert

    Jul 30, 2009
    1,249
    1,324
    60
    As I stated. I did not need SMB1 before on any of my systems including Server 2022 client. Something changed in recent LCU updates on my side to cause the shares to no longer work. Everything is fine again using the hosts file without enabling SMB1 which I want to avoid