(I've removed aforementioned signing/encrypt lines after last time I post since they're of no help.) They are here, alongside my smb.conf, which has these additional lines compared to default Ubuntu smb.conf: security = user I couldn't find a guide about what value log level should be set to, so I've set it to 10, which produced enormous logs. I did this procedure twice, with the first time the aforementioned Windows policy was set, and the second time it wasn't (and therefore this time Windows successfully connected to Samba). I stopped smbd service, deleted all existing log files, started smbd service, tried to connect from Windows, again stopped smbd service, and then grabbed the log files. And the Samba server is not in AD domain ( server role = standalone server). With or without these three lines lead to same results ( sudo service smbd restart in between). I've tried several combinations of server signing, client signing and smb encrypt in smb.conf and still cannot make it work, and I can't find a HOWTO/manual about this.Ĭurrently smb.conf includes server signing = mandatory Due to a recent change of security policies where I work, users' Windows 7 PCs are now configured with Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options\Microsoft network client: Digitally sign communications (always) enabled, and no longer able to access Samba share at my Ubuntu 18.04 server.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |