forum.opsi.org

hi,
I finished installing the packages and configured the backend but I have a little problem here. I cannot access the samba shares opsi_repository, opsi_workbench, opsi_depot, etc. Any help would be very much appreciated.
I not much familiar of Linux that's why I'm still learning.

Hi,

how do you want to access the shares?
What exactly does not work there?
Is there an error message? If so what does it say?


Kind regards

Niko

Hi Nikko,
After I added this in smb.conf ntlm auth = yes, I was able to access but after I reinstalled OPSi sever, again I can't access. The error is access denied.

Thanks.

Hi

what is the rror code when you run the following command? Cheers
Mathias

hi rmtevesjr,

we are working on the best workaround for this problem.

Microsoft seemingly has changed the behavior of Windows10 since v1803, I reckon.
Along with disabling SMBv1, the builtin Windows-Explorer will not ask you for credentials upon smb connection attempt. Instead, it believes, you are trying to access something insecure (which is not the case). SMB shares on opsi servers are (and have always been) secured by password.

2 ways to resolve the issue:

1. provide at least a username in your connection attempt. Possible via 'Map network drive' in Windows Explorer (don't forget to specify 'alternate user-account') . Same thing as using the command line, saying 'net use z: \\server\share /user:<yourUserHere>'

2. call the Credentialmanager (or 'control.exe /name Microsoft.CredentialManager' ) . Within Windows-Credentialmanger, add FQDN of your opsi - Server (or *.your.domain), providing a valid username. Password can be left blank, and needs to be specified upon connection attempt. This way, windows will know early enough you are planning to authenticate, so that access to your opsi shares will be possible again.

cheers
andre

hi again,

there is an easy way to add your opsi-Server via CLI :

one more comment:

Windows-Credentialmanger seems to work User-based.

greetings!

Thanks Andre. I will try it.

Hi m.radtke, the error when I map using net use is "Access denied".

Hi Andre, I tried both 1 and 2 above, I got "access denied" error. Thanks.

i had something similiar after switching from ltsb 2016 to sac 1809.
although different from your case, windows told me that access to unsecure shares is blocked, which seems to be a new thing.

maybe it's still related to your issue, so have a look at this:
https://getadmx.com/?Category=Windows_1 ... uestLogons

if the registry value is set to disable, there is likely a GPO causing that, so make sure to sort that out before changing that registry value.
you can also run gpedit.msc on the client and change the GPO there, in case the GPO isn't set via AD.

something else comming to mind, try on your opsi server.