Thank you for being a valued part of the CNET community. As of December 1, 2020, the forums are in read-only format. In early 2021, CNET Forums will no longer be available. We are grateful for the participation and advice you have provided to one another over the years.

Thanks,

CNET Support

Resolved Question

Access denied on administrative shares

Aug 1, 2011 4:45AM PDT

Hi all.

I'm stumped - spent an hour searching for a topic like this - and I know the answer is out there - but I cannot find it. Can anyone point me to the right answer?

I have 2 Windows 7 PCs on a switch. I can see the "Users" folder on the other PC over the network from both sides. But trying to open the administrative share (SHCPC\C$) Windows throws me "Access denied".

From another computer I can get my hands on - no problem. I can access the admin share without hassle.

Why is one computer allowed, another not? I cannot figure out a difference between the systems. Small maybe - the user names I'm trying from, is the same on both computers. But I even try using login account "SHCPC\SirHC" from SH2PC, and vice versa, "SH2PC\SirHC" from SHCPC, passwords are the same. Nothing, just "Access denied", as if the passwords were wrong. And I know I have it right, because I log in from another PC with those credentials.

Ideas?

Discussion is locked

cfbosch_ has chosen the best answer to their question. View answer

Best Answer

- Collapse -
By default that's supposed to happen.
Aug 1, 2011 6:48AM PDT

But is the administrator account using the same password on both machines?

Some lose months on this thinking you can type in the password. There's also your firewalls but time and time again it's the old mismatched account name or password and the new networker that thinks they can type in the password.
Bob

- Collapse -
Checked - very sure that's not it yet.
Aug 1, 2011 7:55AM PDT

The accounts on the machines have the same name and the same password. Both have administrative privilages. I can log into SHCPC\C$ using the same account name and password from a different machine, but not from SH2PC.

I am losing months on this because I think I can type in the password. But I verified that I can type in the password because I can get it working from a third system.

I have checked, I have disabled the firewalls completely on both systems.

Thanks so far Bob - at least I have two heads breaking over this. I hope you're starting to see why I've gotten desperate enough to start thrashing forums on it.

- Collapse -
Then why not skip that and move to sharing C?
Aug 1, 2011 8:06AM PDT
- Collapse -
At least the share works
Aug 1, 2011 8:27AM PDT

I do have access to the machine's shares - and, at that, because the passwords are the same, I think I'm getting in with my plain windows credentials, not even credentials from the vault.

Sooooooo.... some things work. The administrative share (which, as you say, tar pit), does not work - to the point where like again today, trying it just results in a big load of wasted time.

And yes. Sharing C did the trick. But the frustration at not getting the quick shortcut to work - agonising.

Happy

- Collapse -
Good to read.
Aug 1, 2011 8:33AM PDT

At least I didn't get tar on me or sucked under.

- Collapse -
PS - tested the suggestion in the link - it works.
Aug 3, 2011 9:40PM PDT

I tested the suggestion in the link

http://answers.microsoft.com/en-us/windows/forum/windows_7-networking/cannot-network-access-windows-7-shared-c-drive/0bf04264-3336-4db6-a98c-b4c1aca35aaf

Good solution.

Registry entry near some of the last posts in the thread - LocalAccountTokenFilterPolicy - Works like a charm. Pretty sure it worked on plain straight windows credentials as well, not the Vault.

Mystery is still: I could access the administrative shares from the third machine - before the registry fix, plain straight Windows 7 install. How?

Not to break heads over it. Just wanted to post that the registry key is a good solution to the problem.

Happy

- Collapse -
I can answer that.
Aug 4, 2011 2:58AM PDT

One Windows install is not like the next.

This means that we are never sure that one machine will behave like the next.

Keeps a lot of folk tinkering and a lot more paying at the service counters.
Bob