No edit summary |
No edit summary |
||
| Line 20: | Line 20: | ||
== SMB protocol enable / disable == | == SMB protocol enable / disable == | ||
[https://learn.microsoft.com/en-us/windows-server/storage/file-server/troubleshoot/detect-enable-and-disable-smbv1-v2-v3?tabs=client MS Learn enable / disable SMB protocols and check status] | [https://learn.microsoft.com/en-us/windows-server/storage/file-server/troubleshoot/detect-enable-and-disable-smbv1-v2-v3?tabs=client MS Learn enable / disable SMB protocols and check status] | ||
== Unable to access file share due to host name mis-match == | |||
If there have been migrations from one domain to another domain file shares may be accessed on old DNS records that have been re-pointed. The Hostnames will then not match the new servers that the connections are pointing to. To fix this you can disable strict name checking. | |||
https://4sysops.com/archives/disable-strict-name-checking-with-powershell/ | |||
Or change/add the following reg key:<syntaxhighlight lang="powershell"> | |||
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters | |||
DWORD name: DisableStrictNameChecking | |||
DWORD value: 1 | |||
</syntaxhighlight> | |||
Revision as of 12:09, 30 January 2025
Check the following services are running and not disbaled:
- DNS Client
- Function Discovery Resource Publication
- SSDP Discovery
- UPnP Device Host
Allow network discovery in the windows firewall in the network security settings.
For Samba file shares install the feature SMB 1.0/CIFS Client if the share is on an older device such as a router
- Get-WindowsOptionalFeature -Online -FeatureName SMB1Protocol-Client
- Enable-WindowsOptionalFeature -Online -FeatureName SMB1Protocol-Client
Enable insecure guest logins via local group policy:
- Computer Configuration -> Administrative templates -> Network -> Lanman Workstation > Enable insecure guest logins - enable
SMB protocol enable / disable
If there have been migrations from one domain to another domain file shares may be accessed on old DNS records that have been re-pointed. The Hostnames will then not match the new servers that the connections are pointing to. To fix this you can disable strict name checking.
https://4sysops.com/archives/disable-strict-name-checking-with-powershell/
Or change/add the following reg key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters
DWORD name: DisableStrictNameChecking
DWORD value: 1