Edit: scroll down to the section about disabling SMB signing in the document @ncpl shared above.
I’ll share a couple tips I found by doing a web search.
* Windows 11 requires SMB signing by default for all connections to increase security by validating communications between client computer and Samba server.
*Potential workarounds described at
@Jose_de_la_Cerda I don’t mean to offend, but is it worth this level of effort to get Early Access when the next stable/production release is likely coming in the near future?
Jose can’t even connect to the Nucleus from the Windows computer, so the user manual link is not applicable. His struggles are with the Windows computer and network connections to a Samba share.
Perhaps if all of this is such a challenge, you may be happier staying on Production and waiting 2-3 weeks for the updates, rather than dealing with the inevitable occasional problems in Early Access.
That’s why he shared the help article that contains the steps necessary to connect
Ahh I didn’t read this part of the documentation. Thanks for repeating the message @Geoff_Coupe
Windows 11 (24H2 and later)
- Open Start Menu and search/open “gpedit” (Edit group policy). Alternatively, press Win + R, type gpedit.msc, and press Enter.
- Navigate to: Computer Configuration > Administrative Templates > Network > Lanman Workstation.
- Locate Enable insecure guest logons. Double-click → set to Enabled → OK.
Disable SMB Signing:
- Navigate to: Computer Configuration > Windows Settings > Security Settings > Local Policies > Security Options.
- Locate Microsoft network client: Digitally sign communications (always).
- Double-click → set to Disabled → OK.
Do we know which Nucleus it is?
Thank you ncpl. I tried to follow those steps, but the process is too difficult for my week knowledge, so I think I’m gonna follow Dadoo wise advice and wait for the production release.
I fully agree with you, Dadoo. I’ll wait. Thank you for your help and comments.
Suedkiez, I agree. I’ll wait. Thank you for your help.