by Gusac |
Filed in: Articles, Troubleshoot
This article is to compile and suggest some of the common troubleshooting steps for the error while accessing the Samba shares on Unix or Linux based systems from Windows 7. They may or may not apply to your scenario. There could be some more steps which are not included in this post. The aim here is to help who are slogging through forums for solution like me.
While connecting to Unix or Linux based samba shares from Windows 7 client network error stating: Windows cannot access \\SERVER and throws error code: 0x80070035.
Whereas the Windows XP systems do not exhibit the same behavior.
1. Basic IP
Though this is a basic step but worth mentioning. If the error occurs with the server name, try connecting with IP address. If it works, it could be DNS issue.
2. Check Firewall
TCP/IP NetBIOS Helper service should be set to Automatic and Started.
Try starting Computer Browser service, if its not.
Try to stop and disable the Routing and Remote Access service, if its started
4. Network Card Binding Order
A. Check the binding order. Go to network connections, go to Advanced menu then select Advanced Settings…
B. Select the network connection you are using and move it to the top
C. Click OK and exit.
5. Enable ‘Client for Microsoft Networks’
In network connections, go to the properties of network connection which you are using to connect to the server. Ensure that the ‘Client for Microsoft Networks’ is checked.
6. Enable NetBIOS over TCP/IP
A. Open the properties of the network connection, select Internet Protocol version 4 (TCP/IPv4) and click on Properties button.
B. On the new page, click on Advanced… button at the bottom.
C. Click on WINS tab and under NetBIOS setting , select Enable NetBIOS over TCP/IP and click OK to exit.
7. Select Authentication level
Check the below mentioned policy on Windows 7: Group policy editor:
Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options\ Network security: LAN Manager authentication level
Ensure that it is not set to refuse LM & NTLM authentication or set to use NTLMv2 only. To be safe, you can select the following setting which enables LM, NTLM and NTLMv2 authentication: Send LM & NTLM - use NTLMv2 session security if negotiated
Note: Ensure that this policy is not coming from Domain level group policy.
And, if you are using Home or Home premium edition and do not have Group Policy editor then do it in registry:
Value Name: LmCompatibilityLevel [DWORD]
Set the value to: 1
Reboot your system.
8. SMB Signing
Disable SMB signing and try:
Value Name: EnableSecuritySignature [DWORD]. Set the value to 1.
Value Name: RequireSecuritySignature [DWORD]. Set the value to 0.
9. Disable SMB 2.0
Disable SMB 2.0 on Windows 7 and try again. Disable SMB 2.0 at client end:
- Open the command prompt (cmd.exe) and type the following two commands:
sc config lanmanworkstation depend= bowser/mrxsmb10/nsi
sc config mrxsmb20 start= disabled
Click here for reference on this
I hope it helps!