NW Doc

Windows 7 Ultimate users, READ THIS:

Microsoft has amped-up their new operating system with some new security standards, which notably fix their aging Samba (SMB) Windows File Sharing protocol. By default, Windows Seven comes pre-configured to only communicate with other file sharing clients and servers which are also using the new beefed-up and more secure version of the Samba file sharing protocol. Because of this, it will not properly communicate with computers running older versions of Samba (SMB) Windows File Sharing protocol.

Restore your file sharing capabilities with older Windows File Sharing computers including but not limited to Windows Vista, Windows XP, Windows 2000, Windows 95/98/ME, and even Linux distributions running the SMB service.

1. To start us out, you need to go to your Start Menu, and search for "Local Security Policy". When it comes up, don't click it straight away. Right click, and say "Run as Administrator".

"Start - Local Security Policies"

2. Select Local Security Policies from the Directory Tree on the left, and then beneath of that, select Security Options.

"Local Security Policies - Local Policies - Security Options"

3. Under the policy browser select and open "Network security:Minimum session security for NTLM SSP (including RPC based) Clients".

"Network Security - Minimum session security for client."

4. Uncheck both boxes so that neither "Require NTLMv2 session security" or "Require 128-bit encryption" are checked. Apply the settings and close that window.

"Un-check the box "require minimum security" for clients."

5. Below the currently selected policy in the policy browser, select and open "Network security:Minimum session security for NTLM SSP (including RPC based) Servers". Again, Uncheck both boxes so that neither "Require NTLMv2 session security" or "Require 128-bit encryption" are checked. Apply the settings and close that window.

"Uncheck the "require encryption" box for servers, and apply the changes."

6. In the Security Policies browser for Local Security Policies - Security Options, locate and open the policy "Network Security LAN Manager authentication level".

"Network Security - Lan manager authentication level."

7. In the drop down selector for the options of this policy, Locate and select the option "Send LM & NTLM - use NTLMv2 session security if negotiated". Click Apply, and close out of all policy management windows.

"Set the lan manager authentication level to "Send LM and NTLM responses."

After changing these settings, you should be able to access any SMB server, assuming that you've properly configured the server itself to allow you to connect to it.

Windows 7 Home Premium users, READ THIS:

Windows 7 Home premium users do not have the ability to follow the above instructions

FOR HOME EDITION
1 . Open registry editor ( Start search - regedit)
2 . Browse to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa
3. Create a new DWORD value with the following properties:
NAME: LmCompatibilityLevel
VALUE: 1
4. Restart your PC and try the connection again…

If you are still having trouble after doing this, double check that the machine you are connecting to has it's Samba file sharing configured properly as well, that your network connection on both computers is solid and configured properly, and that if you are running any firewalls on either machine, that you have set them up properly to allow for Windows Samba File Sharing on the network.

Note to Linux Users: The new NTLMv2 protocol in Windows Seven has been known to cause the Samba server process on a Linux operating system to hang and or crash when receiving attempted communication from a NTLMv2 enabled client. You may need to restart the samba service on your Linux server if you have previously attempted to connect from a NTLMv2 Client (such as Windows Seven).

Source