Server Fault is a question and answer site for system and network administrators. 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


  • Windows 7 Pro client
  • Windows Server 2k3 Domain

    1. Client tries to access \\Machine\share and gets permission denied
    2. Client tries to access \\IP\share and is allowed access.
    3. Client CAN access \\SomeOtherMachine\share, this only fails with a specific Machine
    4. net use reports no other connections to Machine (or anywhere else for that matter)
    5. This behavior persists between reboots.

Causes? What further info is required to debug this?

share|improve this question
up vote 4 down vote accepted

Is it possible that Windows is using a cached set of credentials when using \Machine? Is there another share accessed on that machine using a different username, that doesn't have access to \share?

share|improve this answer
Edited the question with more info I thought about after reading your answer. But, how do I know if Windows is using a cached set of credentials? I've already tried rebooting. – Vinko Vrsalovic Apr 12 '11 at 10:04
Check in Run > control userpasswords2 > Advanced > Manage Passwords. – Bart De Vos Apr 12 '11 at 10:17
Cached set of credentials was it. Deleted them and voilà. – Vinko Vrsalovic Apr 12 '11 at 12:09

Have you verified DNS is correct? With AD problems this is more often than not the problem. Check that the client and server machines both have valid DNS entries(and check the DHCP server).

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.