Super User is a question and answer site for computer enthusiasts and power users. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

We just installed a suite of Windows 7 Pro 64 bit machines with a Server 2003 Domain Controller.

For some reason the W7 machine cannot connect to the User shares on our DC.


admin account: root

If I log onto the server or a Windows XP client with the admin account I can type \server\usershares$ and it will open up the content

If I login in with the same account on a windows 7 client and type that in \server\usershares$ it gives me an error message that the drive may not exist and to contact the network administrator.

share|improve this question
Can you ping the server from a w7 machine (is it all machines or just one?) – Dave Sep 10 '12 at 12:29
I can ping the server, the firewall is disabled. The even wierder thing is that I exactly the same machines with the same build image but only some of them will not see the drive. The exact message is "You do not have permission to access \\server\usershare$ please contact the system administrator". if i just access the \\Server it will show all open shares and allow me to access them. Surely it cannot be permissions because i am using exactly the same account only the hardware is different. – Arturski Sep 11 '12 at 12:36
Sorry to ask: Are you on the same domain, using the same DNS and on the same subnet? Can you also disable any internet security/anti virus as well. – Dave Sep 11 '12 at 12:46
Exactly the same domain subnet gateways and dns. Both machines can get the list of shared folders on the server if you run \\servername in the Run command, However one PC can access SpecificShare$ but the other one cant while using the same user account. – Arturski Sep 11 '12 at 12:49
And is this regardless of which user logs onto this PC? – Dave Sep 11 '12 at 12:51

I have experienced recently this problem and the issue was with the time on the server. The server has a problem with the intrnal battery, so, when you shut it down and then up again, it starts with the production date and time (sometime in 2007).

That's ok to the Windows XP clients but not with the Windows 7 ones. Setting the date and time of both server and client right solved the problem for me.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.