Active directory

Harpreet

When users connect with each other or with server, sometimes it asks for user
name and password although the users exists in active directory in windows
2003 server enterprise edition.

The password prompted for connecting to others PC do not accept the user
name and password of the user who wants to connect to other PC. It says LOGON
FAILURE ...........the user name and password you are trying to access with,
already tried or do not have permissions to access.

But when some other user name and password is provided it accepts and
moreover sometimes this user name and password is not accepted. The PC being
tried to access accepts only the password through which it has been logged
in.

Danny Sanders

> The password prompted for connecting to others PC do not accept the user
> name and password of the user who wants to connect to other PC. It says
> LOGON
> FAILURE ...........the user name and password you are trying to access
> with,
> already tried or do not have permissions to access.

You've got a domain but it sounds like you are trying to use it like a
workgroup. Take advantage of the benefits that a domain provides.

The user is present in AD but not on the PC he is trying to connect to.
Generally you use AD to manage the user accounts that access shares on the
servers on the domain, not the shares on the PCs in the domain.

When you don't have a domain in order to share a folder for another user on
another PC you have to create a user on the computer that is sharing the
folder, using the same username and password the user that needs to access
the share, uses to log onto their PC, then grant that user permission to the
share.

With a domain you generally put the shared folders on servers and use the AD
db to grant access to shares.

One of the benefits of a domain is keeping all the shared folders on
"servers" (not PCs), the servers should be running all the time. Users shut
down PCs. Keeping the shared files on server also means you don't have to
backup every PC in the domain.
Keeping shares on the servers also means a user's PC can crash, you can
rebuild it, put it back on the domain and since all their files are stored
on the server, you don't have to worry about restoring files to their PC.
If their PC crashes, with their files on the servers they can log into
another PC, get to their files, and keep working.

You are creating an administrator's nightmare. If you ever leave this
company another admin will have major problems.

I would suggest putting all the files and folders on that your users need
access to on one or more file servers. In the long run it will make your job
easier.


hth
DDS

"Harpreet" <Harpreet@discussions.microsoft.com> wrote in message
news:55AE9C30-F603-4565-B0D4-B1A7040907AE@microsoft.com...
> When users connect with each other or with server, sometimes it asks for
> user
> name and password although the users exists in active directory in windows
> 2003 server enterprise edition.
>
> The password prompted for connecting to others PC do not accept the user
> name and password of the user who wants to connect to other PC. It says
> LOGON
> FAILURE ...........the user name and password you are trying to access
> with,
> already tried or do not have permissions to access.
>
> But when some other user name and password is provided it accepts and
> moreover sometimes this user name and password is not accepted. The PC
> being
> tried to access accepts only the password through which it has been logged
> in.