Results 1 to 4 of 4

Thread: SMB v2

  1. #1
    Join Date
    Jun 2017
    Posts
    6

    Unhappy SMB v2

    Following wanacry we disabled SMBv1 via group policy on our network.
    This stopped Command Workstation from working on our Fiery (FS100 Pro on windows 7 pro) - turns out SMBv2 was disabled in the windows registry on the Fiery itself - enabling that fixed the issue for Command Workstation on the Fiery itself - but not over the network - Command Workstation on other desktops can no longer connect to our Fiery over the network.
    (This issue persisted over the update to Fiery Command WorkStation Package : 6.0.0.372
    Fiery Command WorkStation: 6.0.0.46)
    Does Command WorkStation depend on SMBv1 for communication? (even if you don't want/need Windows XP clients?)
    Is this a known issue and is there anything I can do to make it work?

  2. #2
    Join Date
    Jul 2009
    Location
    Amsterdam
    Posts
    963

    Default

    Can you give us more info on the exact change made to disable SMB?

    We tried to disable smb1 on a Fiery server via this powershell command and CWS6 on a Win10 client can still connect to it:

    Set-ItemProperty -Path "HKLM:\SYSTEM\CurrentControlSet\Services\LanmanSer ver\Parameters" SMB1 -Type DWORD -Value 0 -Force
    Last edited by Greta_C; 06-30-2017 at 05:57 PM.

  3. #3
    Join Date
    Jun 2017
    Posts
    6

    Question Steps taken to disable SMBv1 and check result

    Thank you
    Can you check which SMB version is running from your windows 10 client by connecting to a network share on the fiery and running this PowerShell command 'gsmbc'?

    our result:
    PS C:\WINDOWS\system32> gsmbc

    ServerName_____ShareName_____Dialect_NumOpens
    KM-1____________PC_User_SW____ 2.1_____2

    The steps we've taken to disable SMBv1 are from Microsoft here:
    https://blogs.technet.microsoft.com/...-group-policy/

    One of the three settings they suggest changes the registry here:
    HKLM:\SYSTEM\CurrentControlSet\Services\LanmanServ er\Parameters <- no spaces forum seems to add one in LanmanServer
    setting key SMB1 to DWORD 0
    On our Fiery's registry the key SMB2 there was already also set to DWORD 0
    I changed the SMB2 key to DWORD 1 to enable SMB2 as command workstation was not working after the group policy update - enabling SMB2 fixed CWS on the Fiery but not from the network.

    I would really like to know if your win 10 command workstation client is working over SMBv2

    Thanks again
    Paul
    Last edited by PaulP; 07-03-2017 at 01:21 AM. Reason: format

  4. #4
    Join Date
    Jun 2017
    Posts
    6

    Default

    This was possibly a windows firewall issue - problem went away after opening and closing the two command workstation rules in windows firewall on the server

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts