Take the 2-minute tour ×
Super User is a question and answer site for computer enthusiasts and power users. It's 100% free, no registration required.

It's ironic that I, software engineer with 12 years of experience, continue to have this problem from one version of Windows to another without being able to achive consistent result (sometimes it works).

Here it goes again.

I have a machine with Win8 Consumer Preview. It doesn't really matter that it's win8. I had same issue with win7 before. On given machine I created local admin user with same name and password I have on second PC (the machine I'm typing this from now).

I have two questions to you guys.

  • Why I'm not able to access C$ share of win8 machine from another Win7 machine? I get error that C$ doesn't exist even though it does.

  • Why I'm not able to access share named "test" in Win8 for which Permission set to Full for Everyone. When I attempt to access it from Win7 machine I'm asked to enter username and password. After entering local administrator credentials I get error "Windows cannot access \192.168.1.123\test. Error code: 0x80004005. Unspecified Error".

Windows Firewall is disabled on Win8 machine for both Private and Public networks. Guest account is disabled. Built-in admin account is enabled. Machine is pingable from other machines.

share|improve this question
add comment

2 Answers

up vote 3 down vote accepted

Use Regedit to Create LocalAccountTokenFilterPolicy Value

This is an extract from my account of the access denied problem

Type Regedit in the Search dialog box, best right-click the executable and 'Run as administrator'. Once Regedit launches navigate to this path: HKLM\SOFTWARE\Microsoft\Windows CurrentVersion\Policies\System 

The text book says create a new DWORD value called LocalAccountTokenFilterPolicy. What I did was create a QWORD (64-bit) called LocalAccountTokenFilterPolicy, that worked for me when the DWORD would not allow access to my 64-bit machine.

In either case, set the value to numeric 1 (meaning on), remember to click OK. Mostly, the LocalAccountTokenFilterPolicy value gets created before you have a chance to set the data value; no problem, just double-click and modify the data from 0 to 1.

share|improve this answer
    
It helped. Thanks a lot. –  ruslan Apr 4 '12 at 22:53
add comment

I think that all problems mentioned are connected with security.

Local administrator accounts on two different computers/systems even with same name and password are two different accounts.

"Everyone" must be an account known either locally on same computer if log on is on local computer OR account known on network if computer has joined network via network log on.

A network administrator and a local administrator are two different accounts with different rights.

Every account is unique being either local or a network account. A local account with name and password is different from the account with same name and password on the network.

Hope this helps.

share|improve this answer
    
Any suggestions how to fix it ? What's puzzling to me is that I provide correct credentials when it asks me. –  ruslan Mar 30 '12 at 1:24
add comment

Your Answer

 
discard

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.