Home / server / Questions / 544982
Accepted
cregox
Asked: 2013-10-10 13:22:24 +0800 CST

How do I get my machine to access the share now?

  • 772

Disclaimer: Using windows to share files is definitely not as simple as on *nix, even if it seems like.

First, I'm assuming we can securely (with passwords) share files / folders in basically only two ways:

  1. Have the same user+password on both machines or
  2. Authenticate on the connected shared folder. (providing user name and password)

Is this right? Well...

For some reason, neither way to share folders works properly, in this setup:

Setup

  • Windows 7 (several machines, in fact)
  • Windows 2008 Server - no domains, no Active Directory
  • cawas account set on both, with same non-blank password
  • mygroup group set on Windows 2008 Server, which contains cawas
  • several users, other than cawas set on Windows 7

Yeah, sure, "why don't you use domains?" is a valid question here. Well, I don't know as well. We don't have an admin and it seems like too much work for too little need. Anyway...

Symptons

If I set cawas on the server, I can easily access it from win7, from whichever user I'm logged in.

But if I set just mygroup (and remove cawas) on the server, I can only access it if I'm logged in as cawas on win7. It doesn't even ever asks for a user name and password. Even if I enforce the authentication by using mapping it still doesn't work.

The error is either "can't connect" or "share point already using another username / password", but nothing I do can fix those messages, including net use /delete. The symptom is always the same: doesn't even allow to connect.

The strangest thing happens on another windows 7 machine... Same setup, but it asks for user name and password, we type in, it works! That one doesn't even have cawas (or any user) set as the same from the server.

So, what's going on? How can we fix this?

windows-server-2008

2 Answers

  1. Best Answer

    You can add, edit, or remove credentials by going to Control Panel > User Accounts > Credential Manager. For example, if you're not being prompted for a user name and password, and you would like to be, select the saved credential and choose "Remove from vault".

    If you don't see the Credential Manager in your Control Panel, an alternative way of opening it is by opening Run (Windows_Key + R) and entering control /name Microsoft.CredentialManager.

    • 2

  2. In fact, there's one very practical solution to this: use the same user on windows 7 from the server! It's easy to rename the user on win 7, if that's the problem. This is how we solved my issue - although it doesn't address the stated problem.

    There seems to be, indeed, some kind of user name and password "cache" Windows do. Probably, if you delete that user from the buggy win 7 machine and recreate it, the problem will be gone. I just can't bother to research more and searching for more info on this yielded to no results.

    • 1