Windows 7 can't access Share in a workgroup
Hi, I'm having a problem with windows 7 & connecting to a share on a workgroup.The domain has 3 windows xp machines & 1 windows server 2000 all on the same workgroup.The computer is on the same workgroup as all the others.The server has some shared folder, with sharing permissions set to "Everyone". Problem is, when I try to connect to the share, he requests a username and password, when I enter: \\w2kserver\admin + password, or w2kserver\admin + passowrd he keeps saying I do not have permisson to access the share??Can someone please help me with this? Username & password are correct, it always worked fine on XP....I've recorded the problem as well: http://users.pandora.be/Desteny-/share.zipThanks in advance,Filip Wilms
December 21st, 2009 3:22pm

Hi, First, I would like to confirm whether the Windows 7 machine is in the domain. Is the domain name "MIA-PC"? And the domain user profile is Supervisor? Please type the domain and user credentials by following format: User Name: Domain name\user name Password: If the error persists, I suggest you add the Windows 7 machine to the domain and map the drive for a test. Thanks, Novak
Free Windows Admin Tool Kit Click here and download it now
December 22nd, 2009 11:42am

Hi Novak, The windows 7 machine is on the same Workgroup, no domain installed. I can see the WK2Server fine, but I can't login, it keeps telling me the username is wrong, but it is in fact supervisor...I've tried about everything, but without any luck.Filip
December 22nd, 2009 12:45pm

does no one here search for answers??? answered here many times...click the start button and type secpol.msc in the search function. Browse to "Local Policies" -> "Security Options". Now look for the entry "Network Security: LAN Manager authentication level" and open it. Click on the dropdown menu and select "Send LM & NTLM - use NTLMv2 session security if negotiated". Apply the settings. In the Advanced sharing settings page of Network and sharing center, you need to have it set as Work/Home profile. Try -Enable network discovery-Turn on file and print sharing-Turn off password protected sharing-Use user accounts and passwords to connect to other computers The other settings such as encryption I have set as use 128 bit encryption. Please check related policies. 1. Enter “gpedit.msc” in the Start Search box. 2. Open “Computer Configuration”/Windows Settings/Security Settings/Local Policies/Security Settings.3. In the right pane, enable the following policies: Network access: Allow anonymous SID/name translationNetwork access: Let Everyone permissions apply to anonymous users Also please disable the following policies. Network access: Restrict anonymous access to Named Pipes and SharesNetwork access: Do not allow anonymous enumeration of SAM accountsNetwork access: Do not allow anonymous enumeration of SAM accounts and shares
Free Windows Admin Tool Kit Click here and download it now
December 22nd, 2009 5:40pm

And If I am an unlucky user of Windows 7 Home, how do I proceed to apply these settings to access the win2k computer? (I'm having the exact same problem)Thank you!
December 31st, 2009 9:44am

The solution may be simpler then you think. I just spent days banging my head against the wall trying to figure it out and here what I found:Make sure the clocks are in sync on Win 7 and Win2K boxes. Thats all it is. My Win2K clock was 2 hours two fast. Once I changed the time I was able to connect with no problems. I actually validated that by changing the clock again I had re-introduced the problem.Happy sharing!
Free Windows Admin Tool Kit Click here and download it now
January 8th, 2010 11:43pm

Wow your rock man. I have had Win 7 since it first came out and I have never found and answer to this I can't access network password protected shares on my local network. I did what you mentioned to the letter and it worked like a charm in just seconds. Super thanks Just a follow-up programming note this only works on the Pro and up versions of Win7 I had no luck with Win7 Home Premium.
January 14th, 2010 7:08pm

Bought a new HP quad core machine with Windows Home pre-installed. Windows 7 Home was working until I did a clean install of Windows 7 Professional with Virtual PC and the XP emulator. (I have some expensive CAD and other 32 bit software that I didn't wish to replace). At that point my other computers (Win 2000, Win XP, Win Vista) could all grab files from and share folders on my new 64bit Windows 7 Pro machine) but my Windows 7 pro machine couldn't access the files on my Windows 2000 machine. My network user name and password was not being accepted when prompted to do so. Interestingly, My Windows 7 pro machine could see and access files on all my other computers. I can't believe it was this easy. My time clocks were set to the same hour BUT set to PM rather than AM (oops!). This also set the date 12 hours off so it was wrong, too, half the time. I was dumb enough to spend days on this issue without noting the clock settings... Thank you big_nk
Free Windows Admin Tool Kit Click here and download it now
March 9th, 2010 7:18pm

still no answer for Home users? if anything give a list of the registry lines to edit.
March 15th, 2010 8:52pm

Same here. Interesting if I change the time on the w2k server to 1 hour behind (2:30 -> 1:30) I can connect. I was good until time changed. Tried everything. I also run a mail sever on w2k and the mail that I recieve in the 'Live Mail' is always one hour ahead of the correct delivery time
Free Windows Admin Tool Kit Click here and download it now
April 1st, 2010 12:33am

Kerberos strikes again.
April 17th, 2010 10:04pm

Hi everyone, I just solved a similar problem with my Windows 7 laptop connecting via wireless. I discovered that there were over 200 Microsoft 6to4 adapters that had been created in the Device Manager. After uninstalling each one, I was able to browse my home network and see my shares as well as reconnect to them. Prior to uninstalling these devices, I could ping and tracert both the machine name and the IP of the machine hosting the network shares, but I wasn't able to browse the workgroup and see anything other than the Windows 7 laptop. This is a known issue with Vista and Windows 7, Microsoft has admitted this problem in a KB article and their suggestion of running a commandline statement to start/stop the homenetwork before logging off and after rebooting does not work. Just FYI, hope this helps someone. Tass23-The Man With The Plan.
Free Windows Admin Tool Kit Click here and download it now
April 20th, 2010 7:20pm

I fixed this probleme - windows 7 can not connect to share on server 2003, by this single step: Browse to "Local Policies" -> "Security Options". Now look for the entry "Network Security: LAN Manager authentication level" and open it. Click on the dropdown menu and select "Send LM & NTLM - use NTLMv2 session security if negotiated". Apply the settings. -------------- Jonathan Ravzin MCT - Microsoft Certified Trainer MCSE since NT4 up to MCITP 2008
May 24th, 2010 11:56am

You, sir, are a genius. After mucking around with the super-prop-top answers/solutions, which were quite misleading, I tried your trick. I had changed the BIOS in my Windows 2000 PC and the time settings were way off. Once I put the Windows 2000 PC back to the correct time, my problems went away. Thanks.
Free Windows Admin Tool Kit Click here and download it now
July 3rd, 2010 7:22pm

This has been so frustrating for me. We have a Win2k server, no domain, shared folder all full control- and 3 other W7HP 64bit machines that access the share without issue. I have the W7 account exact same as others and exists as user on Win2k server. I tried the registry edits suggested. I am able to access the public folder on the W7 machine from the Win2k machine and copy files there. I tried setting the clocks as suggested. (reboots required?) It would be nice if there were a policy editor or group of .reg files I could use. In any event I am very flustered by this issue. O
July 15th, 2010 3:47am

How in the world could this be the solution? Real quick back story. Built 2 workstations, identical everything. Put Windows 7 Pro on machine A with no license (30 day trial or whatever). Installed all of our apps and set it up to our liking. Cloned the hard drive to machine B and changed only the computer's name and IP address. Computer A has no issues accessing Windows servers, computer B would NOT. Finally I found big_nk's post about the time. Computer B was TEN minutes behind the current time. We updated the time, and presto! All network shares are accessible. Why?! Don't get me wrong, I love that we found a solution. And maybe I could see an issue with big_nk's being off by 2 hours. But 10 minutes? Anyone know? Thanks for the solution and also any additional input anyone has.
Free Windows Admin Tool Kit Click here and download it now
July 30th, 2010 3:33am

If what happened to me is similar, then read this: Generally before putting on a new system, I backup all the old files - included those from the user files. Seems pretty logical to me to have a backup of them. My next step, following the setup was to reference those backups and move them into my new User file folder... pst files, no problem, point to them from Outlook and bingo... files on the desktop, just copy them over. My issue was a bit more complicated when it came to hidden folders. For example, I could not gain access to my SendTo folder. I tried over and over until I noticed the folder itself is not a folder at all but a shortcut to another folder. The other folder was in a desktop folder called "Old Desktop" which is where I imported my backup. Worse, the username is the same from the old machine backup to the new machine backup so there was nothing to tell me it was a sid problem - meaning, the shared shortcut is blocked by default - different sid's different folders. That's a good thing. So, after hours and hours of figuring it out and then noticing it was a shortcut and not a folder, I just deleted the shortuct, went to the backup, copied the folder itself, and dropped it into my ..\Users\mylogin folder. Wow, can't believe it would be that complicated.
August 1st, 2010 6:29pm

The solution may be simpler then you think. I just spent days banging my head against the wall trying to figure it out and here what I found: Make sure the clocks are in sync on Win 7 and Win2K boxes. Thats all it is. My Win2K clock was 2 hours two fast. Once I changed the time I was able to connect with no problems. I actually validated that by changing the clock again I had re-introduced the problem. Happy sharing! That fixed it for me. Thanks!
Free Windows Admin Tool Kit Click here and download it now
August 26th, 2010 12:35am

The solution may be simpler then you think. I just spent days banging my head against the wall trying to figure it out and here what I found: Make sure the clocks are in sync on Win 7 and Win2K boxes. Thats all it is. My Win2K clock was 2 hours two fast. Once I changed the time I was able to connect with no problems. I actually validated that by changing the clock again I had re-introduced the problem. Happy sharing! This works Change Regional settings Date Time & seconds to be the same as the Y2K server and all networking works perfect now. What time & Date has to do with networking beats me!!!! WINDOWS 7 NOT MY IDEA
September 17th, 2010 3:24pm

OMG I can not believe that was the solution! how silly of us not to realise all computers should be connected to the same time server (note: I was in the same time zone, but that's not good enough for windows) makes me wonder if this was something popped in to make us poor users tear our hair out in frustration...
Free Windows Admin Tool Kit Click here and download it now
September 23rd, 2010 12:26am

The solution may be simpler then you think. I just spent days banging my head against the wall trying to figure it out and here what I found: Make sure the clocks are in sync on Win 7 and Win2K boxes. Thats all it is. My Win2K clock was 2 hours two fast. Once I changed the time I was able to connect with no problems. I actually validated that by changing the clock again I had re-introduced the problem. Happy sharing! big_nk. I had already started banging my head against the wall just as i'm sure you did. All the network sharing parameters seemed to be in order, but it still was not accepting my usual administrator credentials over the network. Then i realized that the timezone for this laptop is different than where i am because the user is going to be using it in Hawaii, not Pacific time. I changed the timezone and now our shared resource takes the password! It would have been nice if stupid windows 7 would report there is a time discrepancy, and not just a bad username / password combination. Another useless error message. Thanks for the great post!
October 13th, 2010 10:37pm

Although this may be a work around, this is NOT a solution. I have a stand alone server, off my domain, specifically for the purpose of changing the time to test our code. The only purpose of this server is so that we can make the date months in advance to test software that is time sensitive. I still need to access shares on this box from my Windows 7 machine. It was never a problem with XP, why is it now a problem with Windows 7? There's got to be a policy or registry setting to allow this to happen, don't you think?
Free Windows Admin Tool Kit Click here and download it now
October 14th, 2010 9:45pm

u r really big :D 10x man it works :D
October 18th, 2010 2:32pm

This isn't helpful - the search terms do not bring up any programs, and I can't find all the settings mentioned.
Free Windows Admin Tool Kit Click here and download it now
October 31st, 2010 1:19am

Kerberos uses a ~5 minute window.
November 15th, 2010 8:07am

Great Answer, worked perfect- thanks just wondering why they made it so elaborate. Rundavo
Free Windows Admin Tool Kit Click here and download it now
December 21st, 2010 2:15am

I am having a similar issue. I can not connect from the Windows 7 machine to an XP allow I can see them. I can access the 7 from the xp's. I followed your instructions typing secpol.msc into the search bar. Nothing found
December 23rd, 2010 4:07pm

This worked for me!!
Free Windows Admin Tool Kit Click here and download it now
January 14th, 2011 10:47pm

The solution may be simpler then you think. I just spent days banging my head against the wall trying to figure it out and here what I found: Make sure the clocks are in sync on Win 7 and Win2K boxes. Thats all it is. My Win2K clock was 2 hours two fast. Once I changed the time I was able to connect with no problems. I actually validated that by changing the clock again I had re-introduced the problem. Happy sharing! I spent hours to solve this problem until I read this helpful answer. Thanks a lot, you save my life.
January 31st, 2011 7:04am

Hi all, Just found this forum, and try to follow all the suggestions above. But unfortunately, I didn't find the solutions, IMHO maybe because win 2003 has been updated into new patch. editing secpol.msc, gpedit.msc, do a time synchronization between win 7 and win 2003. But still..got a zero result. anyone can sharing another method? FYI, When I try to open my server (\\server\) it's appear an error message : \\server\ is not accessible. You might not have permission to use this network resource. Contact the administrator of this server to find out if you have access permissions. Logon failure: user account restriction. Possible reasons are blank passwords not allowed, logon hour restrictions, or a policy restriction has been enforced.
Free Windows Admin Tool Kit Click here and download it now
January 31st, 2011 9:05am

hello, I have windows 7 Ultimate and I'm having the same problem cannot connect to my shared folders on my Windows Home server. I tried entering secpol.msc and gpedit.msc and there are no matches. Any help this is a problem I cannot figure out. Thanks in Advance On my Windows Home Server, under computer>properties> it says Power pack 2, but under WHS console it shows Power pack 3, not sure why. The remote desktop works fine GDipsgary w dipple
February 1st, 2011 5:51am

The solution may be simpler then you think. I just spent days banging my head against the wall trying to figure it out and here what I found: Make sure the clocks are in sync on Win 7 and Win2K boxes. Thats all it is. My Win2K clock was 2 hours two fast. Once I changed the time I was able to connect with no problems. I actually validated that by changing the clock again I had re-introduced the problem. Happy sharing! Hahahahaha amazing !!! That fixed it for me! Thanks for your help! Diego.
Free Windows Admin Tool Kit Click here and download it now
February 11th, 2011 4:32pm

Hi All!! I just tested your recommendation settings/Policies (from Bubbapcguy) but the problem is still there. I can access the Windows 2000 Computer from a machine with Windows Xp, but no with computers with Windows 7. Date and Time are the same and correct. I also tried this: http://www.sevenforums.com/network-sharing/152566-windows-7-can-t-access-windows-2000-share.html Any help or guide would be really appreciate it. Thanks!abasilis
March 29th, 2011 8:45pm

Checked server clock vs. client clock. They were about 5 minutes off so we trued them up. That did not solve the problem. Tried the following step and it immediately solved the problem: Browse to "Local Policies" -> "Security Options". Now look for the entry "Network Security: LAN Manager authentication level" and open it. Click on the dropdown menu and select "Send LM & NTLM - use NTLMv2 session security if negotiated". Apply the settings. The weird thing is, this computer has been working on the network for a few months and the problem just appeared this morning.
Free Windows Admin Tool Kit Click here and download it now
March 31st, 2011 7:45pm

Ok I don’t know if this is the same problem or not but I can see my windows 2000 server and access it or maybe not. I can’t see the shared folders that are on the server, when I click on the server thru the network it opens up but that’s it….. I don’t get error or anything asking for passwords I just can’t see folders. Now we are in the same workgroup. I also changed the clocks too mine was five minutes off. I even followed the steps "Bubbapcguy" suggested. I did change my network security levels on both server and pc too, is there anything I’m missing?
April 7th, 2011 5:50pm

what computer do i chk local polices on the windows 7 home or the server 2003
Free Windows Admin Tool Kit Click here and download it now
May 5th, 2011 8:40am

The solution may be simpler then you think. I just spent days banging my head against the wall trying to figure it out and here what I found: Make sure the clocks are in sync on Win 7 and Win2K boxes. Thats all it is. My Win2K clock was 2 hours two fast. Once I changed the time I was able to connect with no problems. I actually validated that by changing the clock again I had re-introduced the problem. Happy sharing! This worked when everything else did not !!!!!!
May 17th, 2011 5:14pm

Everyone: the bubapcguy-suggested steps are not needed. I have several workgroup servers (windows 2008 and 2008r2) that I connect to without any problems, from windows 2003, 7, or OS X. This morning I could not connect to the share of the new server, kept getting access denied messages from all client systems (even tho I could connect via remote desktop). When I tried to connect via NET USE command line, got an incredibly useful "System error 5 has occurred." message. Knowledge base on this error gives completely random responses, shooting in the dark. Finally, realized that I forgot to turn off (the laughably useless) "User Account Control;" as soon as I did that and rebooted, I could connect to shares normally. Comparison with other servers shows that was the only difference that prevented access. So, to cut a long story short, turn off UAC if the time sync suggestion doesn't work. Hope it helps someone. (if you can't get a mac, which I highly recommend).
Free Windows Admin Tool Kit Click here and download it now
May 20th, 2011 1:03pm

Still not work for my computer. I follow every step above.
July 1st, 2011 12:18pm

Windows 7 Home Premium does not have secpol.msc or gpedit.msc modules available. You have to have the Windows 7 Ultimate or Professional versions. Can you formulate an answer that will help Windows 7 Home Premium users? I think Microsoft missed the mark when they assumed that home users would not want or should not be able to network with other computers at their homes that are running XP or Vista. I'm getting this Microsoft is a bully to the home user feeling.
Free Windows Admin Tool Kit Click here and download it now
July 23rd, 2011 1:12pm

Try disabling UAC and check what happens (you need a reboot) or explicitely allow acces for the 'admin'-user (not its group but the user-account). Frits van Drie MCT
July 27th, 2011 8:10am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics