/bundles/itninjaweb/img/Breadcrumb_cap_w.png
Ever since I loaded the Fall Creators update on my laptop I am having issues connecting to \\K1000\clent and \\K2000\drivers... Anyone else having these issues?
2 Comments   [ - ] Hide Comments

Comments

  • Might be just cached connections?

    Open CMD , and type NET USE.

    Use NET USE to delete any existing connections to the appliances.

    i.e.

    net use /delete \\YourKBOXIP\Client
  • I tried it from several machines only ones that had the fall creators update build 1709 were affected...
Please log in to comment

Community Chosen Answer


Answers

5
  1. Run Registry Editor (REGEDIT).
  2. Navigate to the following registry key:

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters

  3. Right click on the Parameters key name, and select New -> DWORD (32-bit) Value.

    New DWORD (32-bit) Value

  4. Name the new value as AllowInsecureGuestAuth and set its value data to 1.

    AllowInsecureGuestAuth

  5. You should be able to access CIFS / SMB / Samba network shares instantly without login.
Answered 11/03/2017 by: ronfalkoff
Third Degree Blue Belt

  • Thanks. had the same issue. But sorted now.
Please log in to comment
Answer this question or Comment on this question for clarity

Answers

1
had this with W10 Enterprise 1709 only. (No Pro and any other 1709 versions)
The above way did not work for me (in- and outside of the domain, with a joined and a not joined appliance and different SAMBA servers with SMB1 activated) 
Had to enable SMB1 on the clients as Microsoft described here:
https://support.microsoft.com/en-us/help/2696547/how-to-detect-enable-and-disable-smbv1-smbv2-and-smbv3-in-windows-and

Then it worked.
Answered 11/06/2017 by: Nico_K
Red Belt

  • This content is currently hidden from public view.
    Reason: Removed by member request
    For more information, visit our FAQ's.
Please log in to comment
1

Nico_K,

I think it is the combo of both as SMB1 is not installed by default in the Creators Fall Update...

Ron

Answered 11/06/2017 by: ronfalkoff
Third Degree Blue Belt

  • I also found this to be true. First I had to enable the smb1protocol and then had to update the registry.
Please log in to comment
0
While this does work, it's not a great workaround.  Microsoft specifically disabled guest access in SMB2.  See here:


Microsoft states that "By enabling insecure guest logons, this setting reduces the security of Windows clients."
Answered 12/27/2017 by: dstarrisom
Senior White Belt

Please log in to comment
This content is currently hidden from public view.
Reason: Removed by member request
For more information, visit our FAQ's.