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

I have a network connection share issue. The first connection works, and seems to stay connected for at least a few hours. However, after each time my windows 7 PC reboots, it can no longer form a network connection to the shared folder, nor browse to it, until I not only unmap and remap the mapped drive, but also, I have to use cmdkey to delete the stored credentials like this:

cmdkey /delete:Domain:target=HOSTNAME

My work PC is on a domain, and I am not the IT administrator, but I'm curious if there is anything I can do to investigate this issue. Any settings in registry or group policy that I could examine to see why the first connection works, but each subsequent attempt (once a stored credential exists) to browse or use the connection, fails with a connection error saying it is "not accessible", like this:

enter image description here

I do not even get any error until at least several minutes go by. THe first thing I see is a window frozen and empty, and then I get this error:

This has happened when connecting to a share on a DROBO device, and on a share which is not on the domain, but which was a Microsoft Home Server. I wonder if there's something broken in WIndows 7 professional with regards to connecting to non-domain shares when an active directory domain controller exists, and a particular workstation is joined to a domain?

The problem only occurs if I click "remember credentials". It is not fixed by any amount of working with net use. Usingcmdkey to delete all stored credentials for the host is the only way to get back in, and it affects all non-domain shared folders.

Update I'm hoping there are some registry locations I could check that could be misconfigured in some way that might explain why SMB/CIFS stored credentials for non-domain systems seem to be auto-invalidated in this weird way. Knowing how whacko Microsoft Windows domain and security handling is sometimes, this could be some kind of stupid "feature".

share|improve this question

It is possible that the local time and the machine hosting the shares are out of sync. Though your domain admin should be taking care of this. Typically when token for your credentials is passed to the machine but is out of sync, it will stop working.

Another possibility is that your local machine might be trying to pass your domain credentials to the Windows Home Server. And being it is not part of the domain, it would bounce you out.

Though admittedly, it shouldn't let you login in either case (unless the domain controller and your workstation are synced up, but the Windows Home Server is not).

share|improve this answer

One reason I can see for this is that you need to store the credentials in the format of MACHINE_NAME\USERNAME and then the password. This way it knows exactly what is applies to.

share|improve this answer
Doesn't change anything. – Warren P Jun 7 '12 at 2:21

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.