Windows 7 Network File Sharing Fix
“Base-Ops this is Buzz Light Year. I seem to have been stranded on some strange planet. No sign of any working Windows Seven file sharing here.”
Microsoft Windows Seven Ultimate Edition
So you’ve manage to get Windows Seven installed, no problems. Everything’s great, the new quick launch bar is actually useful, the OS loads up fast, and the cool new grouped roll over window preview pane is actually letting you get some work done now. You’re ready to go to the next lan party and sport your new slick OS, get some compliments and “Ooohhs” and “Awws”, and swap a few files…. but wait, what happened to the Windows Networking? Why isn’t it working anymore? How are you going to trade the latest season of Red Vs. Blue if you can’t even connect to another Windows file sharing enabled computer?
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.
So are you SOL? If you don’t continue to read this guide you will be. I’ve made a quick walk through with screen shots guiding you on how to 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.
Chicken Noodle Soup for the Windows 7 User’s Soul
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
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
From here, 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.
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.
Now, right 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.
With those settings set, we are two thirds done. Back 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.
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."
That wasn’t so bad, was it?
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.
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. I was able to access my SMB share on my Linux file server after modifying these settings on Windows 7.
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).
Post Revisions
- 2009-10-01:Changed the recommended configuration option for setting authentication level of the LAN manager from “Send LM and NTLM responses.” to “Send LM and NTLM. – Use NTLMv2 session security if negotiated.” This was changed for better compatibility of devices which use NTLMv2.
You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.
Hey, thanks for these tips about Windows 7 network file sharing. I just downloaded Windows 7 few days back.
@Gigasize, You’re welcome. If you have any issues, feel free to bring them here and we’ll see what we can dig up for a solution. :-)
How about connecting to Windows 7 Shares from Linux Mint 7. I can not. I can see my Windows 7 in the Network Browser on Linux, but can not enumerate the share or connect to them manually.
Thanks in advance.
@JenkTJ27, I will be sure to add that to my upcoming posts as something to look into. Thanks for the suggestion!
Great Job! With Windows Vista I encountered problems trying to use a simple NAS / LAN-disk and installed new drivers ( R2882_v48) for the small server on this disk.
Now however with the official Windows Seven trial from Microsoft installed, I was not able to connect to my LAN-disk again.
Thanks to your clear solution and description, my LAN-disk is found in the network and I am now able to use it again as a NAS / LAN-disk (I am no longer stuck using it on USB anymore).
Many Thanks!
@Paul Wansink, You’re welcome. I’m glad that this was helpful for you. That is one situation I had not yet thought of or encountered, with regards to a SMB enabled Lan Disk (aka NAS or Network Area Storage). Feel free to bring any further issues or problems here we’ll see if we can’t learn the solution together.
I tried your solution attempting to connect to a Unisys Clearpath mainframe. Typically for XP we have to set PlainTextPassword and send both LM & NTLM responses. We added the additional settings in your article on our test Win7 PC. It did not work. We are still getting invalid password error messages. Also, I see RESET SENT DUE TO SYN RECEIVED FOR UNKNOWN PORT error messages on the mainframe. The port is 445. Additionally I see “SLM:Unexpected extension: 8″ error messages on the mainframe. I am guessing that Win7 is forcing NTLM2? Any ideas on how to further “dummy-down” Win7 to act more like XP in this case?
@R.Helwig,
Try removing the stored credentials for the Samba share. From your Control Panel, select Credential manager. Locate the user name and password in there. It is possible that the credentials are being called and passed over the network, and that Windows is getting stuck in a loop attempting to authenticate using the credentials over a protocol you’ve since changed while modifying your networking configuration.
Also, Port 445 is a commonly used port for Samba (SMB) service with Windows Networking. You may want to find out which version of the samba server your Unisys Clearpath mainframe has installed. Reading a bit into this at Unisys’s website, it seems to be hinted at that the Unisys Clearpath us using a modified client authentication scheme for all services, including Samba, for security purposes.
From Unisys’s website: “Other system products leverage this secure platform to provide secure services. CIFS-based
file systems (found on Microsoft Windows and Linux systems through the SAMBA service)
are simulated on the system through Client Access Services. Even though they provide
commodity services, they are secure from attack since they are running on the ClearPath
MCP environment.”
This may be working against you with Windows 7 and it’s pre-configuration for networking services. By chance does your Unisys Clearpath mainframe support NTLMv2?
I am putting together a “Part Two” of this guide, which will expound on the solution already presented. The upcoming guide will specifically address multiple angles on troubleshooting and resolving this issue with specific instructions for each of the potential fixes.
In the mean time, let us know if you learn anything about a specific situation and the found resolution which may benefit the community as a whole.
Sadly this has not fixed the Network Error (1208) message I get trying to browse my NAS (Freecom SMB Disk) using the Network browser (appears as device name FND).
I can gain access to the box by simply typing ‘net use g: \\fnd\public’. No credentials asked for – it just connects, and away you go, access as mapped drive G:
Why won’t the browser do this?
Has part 2 of this post been released yet? I am still unable to connect to my iOmega NAS through Windows Explorer after following the steps of this post. I can open Windows Media Player and it will connect with no issues. Windows Explorer won’t accept the correct username and password to connect to my NAS and once I enter the credentials it will not let me relogin without restarting my computer. So far my Win 7 experience has been good, however, this is very frustrating. Any help is greatly appreciated!
Can you tell me where these two boxes are?
Un-check the box “require minimum security” for clients.
Set the lan manager authentication level to “Send LM and NTLM responses.”
I see those lines in your instructions but I don’t see them on my screen.
@Craig
The image you are requesting for “require minimum security” for clients would be here as Minimum session security level for clients.
The two boxes I believe you are referring to can be found in this image detailing opening the minimum session security requirement configurations for connecting to a legacy samba share in Windows 7.
Hopefully I understand you correctly. If not, please reply and specify exactly the Version of Windows 7 you are using, plus the operating system you are trying to connect to with samba or windows file sharing.
Thanks for the fix! It worked as advertised in Windows 7 Ultimate Edition. Will the same fix work in Windows 7 Home Premium?
Cliff Cooley
@Cliff Cooley,
Yes, I can confirm I used the above stated fix on my previous Windows 7 Home Premium laptop, without any trouble.
EDIT: I mistakenly confused in my recalling my experiences Windows 7 with Windows Vista. I have only used Windows 7 Ultimate Edition, and have not used Windows 7 Home Premium, so I cannot confirm this. I would be curious to know if someone else can answer this from experience.
Tanner;
Spent hours on phone and chat with MS support, they wanted $250 for pro support when I read a post that said Win 7 premium would not support mapping over VPN; Called MS Pre-Purchase to ask if Win 7 pro would support mapping over vpn the said no,I needed Ultimate. I ordered Ultimate upgrade for $139.00! I’ll be upgrading my XP Laptop to Win-7 Home Premium. Will let you know how things go.
Cliff
Cliff,
I have to apologize. I realized after my previous response that when I got it working on my laptop, it was Win 7 Ultimate Edition. Prior to this, I had Windows Vista Home Premium on there, and I believe I got them confused. I’m sorry for my mistake in mis-identifying Windows 7 Home Premium with Windows Vista Home Premium.
I’m glad to hear you’re going to be getting Windows 7 Ultimate. I hope that you didn’t pay too much for the version you had prior to this. Newegg sells a full blown OEM license to Windows 7 Ultimate Edition for $175, so I hope that you’re paying $140 to upgrade was an upgrade from XP, and that you didn’t already lose any money in buying a lesser version of Windows 7. Have you decided that, with the “Upgrade” license, if you’re going to be doing a clean fresh installation, or if you are going to Upgrade and let the OS install over your existing OS (trying to migrate all programs and installations)? As most people would recommend a fresh installation, if you chose to do an upgrade, I’d be curious to hear how it goes; what works, what didn’t work so well, etc.
I have to say I’m a fan of Microsoft’s Windows 7 Ultimate Edition, and it’s what I’ve been waiting for from Microsoft. So far, it has yet to disappoint me. I understand peoples hesitation after what they’ve heard from Windows Vista, and what they may have experienced, but I can honestly say Windows 7 feels like going from Windows 98 SE to Windows XP. That’s how good of an experience I have had with Windows 7 Ultimate Edition for the past 5 months.
Regarding your VPN setup, what type of VPN are you using? Device based (ie Cisco VPN Router), or Software based (ie Cisco VPN client, Hamachi.
Discovered before I read your last post, that win 7 Home Priemum was a no go. The VPN is a device based, with a Cisco wrvs4400 at both ends. Is there any hope for Home Preimum and the drive mapping? I use a free version of realvnp to run computers at my client’s office but it does not allow me to transfer files from here to there. I use my laptop sometimes when I am in another part of the houes, not in my office.
I did a clean install first with the family pack upgrade, which made me reinstall as an upgrage so my key would work; then when I discovered the proplem with Home Premium I did an anytime upgrade, so the Ultimate caist $139.00 works great so far.
The laptop was a clean install form XP, it to went well.
I am fairly proficiant with windows and computers in general. but your help has been invaluable for a network newbe like me. Is there an online course I can take on line to learn more about networking?
Cliff
I seem to have the problem you discussed (being unable to log on to a server share, even though I can click the server share icon) where the username and/or password is rejected.
I am running Windows 7 Home Premium, trying to connect to a Mac OS X(10.3.9) Server with Windows file sharing turned on (Workgroup). It works great from all other Windows computers from W95 to Vista, but Win 7 can not connect to the share, always rejecting the user name and/or password. I am unable to perform the steps in your article (Windows 7 Network File Sharing Fix) since I can not locate a “Local Security Policy” in this version of Win 7.
Thanks,
Dan
SFXP.Technology@gmail.com <–Preferred contact. Thanks.
Thank you for the quick fix, we are just starting to do our corporate windows 7 rollout. We have Windows 2000, 2003, 2008, Linux, Solaris, and other OS’s that require connections from Windows.
I know MS wants to have the most secure OS but trying to keep up with the Linux’s is a bit silly.
@Cliff Cooley
If you feel you are up to it, you may want to see if you can find someone who teaches the CompTIA Network+ Course. This is a good entry level networking course in general, though you will want to most likely have gone through their A+ Hardware and Software courses first.
Will this work for Windows 7 Home Premium? I’m having a problem tying to map a drive from Windows Server 2000, however with Windows Server 2003 is ok, no problem there.
And the question has still not been answered as to how you do this in Windows 7 Home Premium. This is ridiculous that it is so hard to find out how to set network settings. I shouldn’t be surprised as nothing in Windows works properly. How people can pay hundreds of dollars for this piece of crud software is beyond me.
The above solution seems to be working for most, but what if (like me) you have the Home Premium edition of Windows 7. I can ping my LAN drive and connect to individual folders on it but cannot connect via the icon on the network page (the one that shows the drive as a computer on the network). I have no other network issues but I would really like to be able to connect the top level drive so I don’t have to add folders on my desktop for every single location on the network drive. When I try to access the drive in this way, a window pops up stating the drive (\STORAGE-7635) “is not accessible. You might not have permission to use this network resource, Network error (1208).” Occasionally, this error is replaced with “A remote procedure call (RPC) protocol error occurred.”
I have been trying to resolve this for hours now! Tried all other suggestions to no avail. PLEASE, PLEASE can you help? Thank you.
Steve P.
I’ve now gotten Windows 7 Home Premium to work and thought I’d share the solution.
Open Control panel > Network Settings and Tasks > Change Advanced Sharing Settings
Click the radio button for: “Enable file sharing for devices that us 40-56 bit encryption”
Click the radio button for: “Use user accounts and passwords to connect to other computers”
Add to this the reg edit I found at http://tinyurl.com/y8ld63u
The solution: Registry editing for LAN manager authentication level (in Home edition this can be configured through registry).
How to do it:
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…
Once I completed this I was able to login to a share using DOMAIN\Username Password
Windows 7 Ultimate, connecting to Thecus N4100PRO. I had tried everything with the network drivers etc… for hours/days. Explorer kept hanging up and the computer would not shut down. Thank you for the solution! Your Skill level is much appreciated, and more so is your willingness to share it.
SIMPLE SOLUTION TO CONNECTING NETWORK DISK in WINDOWS 7
I have a Network attached disk which worked under XP but I could not attach to it with my new Windows 7 Home Premium PC. I tried James’ idea above but it did not work for me. I did not back out the changes and I continued as below. I am including each step in detail to help.
1 Logon to the Network Attached Disk and find out the name of the shared folder, the Workgroup name and the IP address (the IP address should be something like 192.168.0.n).
For me the shared folder was LAN_DISK, although the underscore was not displaying – I found it by trying to Rename the folder and I could then see the underscore. The Workgroup was XXX.
2 Ping the disk to prove that you can actually see it.
Start > All Programs > Accessories > Command Prompt. Type in ping 192.168.0.n and press enter (obviously use your own IP Address)
The response showed that ping was talking to the disk OK, so Windows 7 could see the disk.
3 Set the Windows7 PC to the same Workgroup as the Network Disk.
Right click Computer, choose Properties, choose Computer Name, Domain and Workgroup settings, choose Change Settinmgs and set the Workgroup to the same as the Network Disk Workgroup. My Domain is greyed out.
4 Map the drive
Right-Click My Computer (or Start > R-Click Computer) and choose Map Network Drive
I tried to BROWSE for the disk but I got network errors – typically 1208. However, when I typed \\STORAGE\LAN_DISK in the FOLDER box, and ticked RECONNECT AT LOGON, it all worked fine.
Previously I had tried typing in \\STORAGE\LAN DISK without the underscore and it had not recognised it.
5 I then backed out the changes suggested by James above, and it all still worked OK.
There are two peculiarities I haven’t yet solved (but only two – I guess I am a lucky guy :-))
a) I get a message when I boot saying W7 could not reconnect to the network drive. This is wrong, as I am connected to it. When I click Computer I can see the disk and the files on it.
b) I have a NETWORK icon down by the clock on the Taskbar. When I open it, choose Open Network and Sharing Center, and click NETWORK, and double click STORAGE, I still get Error 1208 and it cannot see the disk.
I hope this helps – Google tells me that there have been nearly 70 million searches on map network drive windows 7 so it looks like there is a problem somewhere.
John_Ha
Thank you! Your solution helped!
I’m having the same problem accessing to my network storage. I have tried all your suggestions above but still no luck! :-(
Thanks though.
But as for now, I go “map network drive” and map the drive manually, i.e. enter \NAS_NameFolder_Name.
I can now access to my Network Drive. :-)
I just wanted to say thanks. This got me connected to my Windows 2000 machine which has my PagePro 1350W on it. After using another workaround for the printer driver (which doesn’t exist), I am finally printing. Kudos!
I came back to this site just to say thank you for providing the fix to this long standing problem I have had accessing my Synology NAS with Windows 7 x64 Home Premium (and Vista before that). You know that feeling of relief you get when a long stuck splinter is finally removed!
For your information, Windows 7 Home Premium requires different tweaks. I edited the registry with
[HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlLsa]
“LmCompatibilityLevel”=dword:00000002
For the non 128bit encryption setting, I used:
‘Control PanelNetwork and InternetNetwork and Sharing CenterAdvanced sharing settings’ then (*)enable file sharing for devices that use 40 or 56 bit encryption.
Problem solved!
I was struggling to connect Microsoft Windows 7 Professional x86_64 to Microsoft Windows 2000 Professional. I could only access Microsoft Windows 7 files from Microsoft Windows 2000, but not the other way around, where as I have no problem communicating with Microsoft Windows XP Professional at all. Your guide is wonderful, and now all my Microsoft Windows 2000, Windows XP, and Windows 7 networking is working flawlessly. Thank you.
Ditto Farid Latif above. Exactly my situation described, word for word. Thank you, thank you.
Thanks! worked perfectly!
Enjoyed reading your article regarding networking with Windows 7, but I have a similar problem between Vista and XP. More specifically with printers. I haven’t even gotten into files and folders yet.
I can get from XP to Vista printer okay but I cannot get anything from Vista to XP without it asking for a password. We have tried everything one can think of and to no avail. Ironically, I do not have one single password anywhere on either system, since I despise passwords unless forced to use them. Why would Vista think it needs a password when none exists?
I would appreciate any light you can shed on this.
Thanks,
R.F. Wunder
Mableton, GA
@John_ha,
Many thanks, after much grumbling at Microsoft’s ineptness your solution has finally allowed me to access my NAS.
@R. Wunder,
I would suggest that if possible, you physically connect all printers to the computer using the newer operating system. In Windows, the host operating system or computer sharing the printer, allows you to store for network sharing, additional drivers for client computers using this shared printer over the network. If possible, install the printer to a computer using Windows 7, (or Vista if you don’t yet have Windows 7), and then go to the configuration properties of the printer under the network sharing settings for the printer. Download from the printer manufacturers website, all operating system specific versions of the drivers for that printer. Specify the driver files for each operating system version, as presented inside of Windows’ printer sharing configuration settings for that printer. Now, when client machines go to connect in, as long as the client operating system is equal to or earlier than the host machine operating system, they will be able to auto negotiate and download the driver off the network from the host operating system, so that the client computers can install the driver, and configure the remote printer for access all in one step.
Just remember you may spend more time trying to find a bandaid fix for your issue, then it may be worth. If it is an option in your situation, consider upgrading the guest operating system, and or switching which computer is being the host machine vs. client in the scenario as well.
Hello,
I have similar problems when using Windows File Sharing in Windows 7. I own an Archos 705 and used to connect it to shares under Microsoft Windows XP.
Now with Microsoft Windows 7 I can parse the network and find my computer, but I can’t see the shares (imagine trying to access it).
I tried several parameters in local security policy / security settings (thanks to you for the idea Tanner) but still have not been successful yet.
Any idea or possible solution or lead?
This suggested fix does not work for me, nor others suggestions I have found on the web. I am trying to fix Windows 7 SMB Access to our Apple 10.5.8 OSX Server SMB system, unfortunately for me and the 3 Users here who must use SCP to access the share on our File Server.
Does anyone have any advanced information or experience accessing an Apple 10.5.* SMB based shares through Windows 7 64-Bit?
I have tried many things.
And I am very surprised there is no solution on the web for this.
Thanks so much for this valuable fix. I have struggled with this and would never have found the fix on my own. You made my day!
Thanks for writing this guide. However I’m having trouble with the first step. When I search for Local Security Services it doesn’t find anything like in the screen shot. Am I doing something else wrong? Sorry for my Ignorance :(
After digging a little deeper I realized the reason I can’t find the Local Security Policy is because I’m using Windows 7 Home. Is there a fix for my version?
I just saw James’s post and it worked perfectly! Should have read all the replies before opening my mouth :) Thanks for sharing!