Closed hangookfreak closed 1 year ago
I need the following information to help you:
it does work without it as we have some computers that run it where we havent put HK on yet. 22h2 client side i have tried manually mounting as well as a batch file
As CIS, Microsoft Security Baseline and 0x6d69636b Windows 10 are lists for 22H2, please be more specific
finding_list_msft_security_baseline_windows_10_22h2_user.csv
sorry the machine one
the weird thing is that one other network drives that we map is able to connect. we are able to ping the drive that doesnt connect as well but it wont connect. nothing within event viewer.
Okay, let's see. You only did the hardening on the client, not on the server. How is the authentication done, local user or domain users, over Kerberos or NTLM? Is the server also Windows or an older system? Do you relay on stored passwords?
nothing is done server side. authentication is done by using a local account on the server. no domain.server is also windows. most likely an older system.
It may be NTLM related, try Microsoft network client: Digitally sign communications (always), Network security: LAN Manager authentication level, and/or Network security: Minimum session security for NTLM SSP based (including secure RPC)
let me check those.
none of those worked additionally SMB 1 was turned on as well
Did you check Configure SMB v1 client driver as well?
yup. ive checked all SMB settings All Lanman settings all RPC settings
any other ideas on what it can be? does this HK script also change anything in group policy or security policies?
do you think it would have to do anything with like account impersonation or anything account related rather than network?
No, HardeningKitty does not/cannot change group policies. If a policy is applied, any changes made by HardeningKitty will be overwritten. The account settings are for the local system and should not change the behaviour of the remote system. Sorry, I ran out of ideas what could be causing this problem
no worries. Thank you
I have this setup on a multitude of computers but we are running issues with certain smb network drives connecting.