Re: Add domain user to client computer.

grambo wrote:
What exactly is it you're trying to do? I'm a little confused.

Your users shouldn't have any local accounts...use domain accounts only.
They should be able to use cached credentials when out of the office/away
from the network.

If the computer is already joined to the domain, you can't run
connectcomputer on it.

Ok, how do I log on to a client computer with my domain login? I've
tried without a local user but I keep getting the "The system could not
log you on. Make sure...." error. I'm using the same login on the
server and my workstation and have no problems. How do I setup cached
credentials?


No offence intended, but sometimes the obvious gets overlooked,
and somebody has to mention this, just to be sure:

Below the user name and password boxes is a dropdown box which
should always contain the domain name. In fact, while it does
contain the domain name it is impossible to logon to a local
account. If it has been set to the name of the client computer,
then it will not allow a domain logon.

If it is showing the domain, and you still get a 'could not log
you on' message, the problem is likely to be:

you do not have a domain user account, or
the computer does not have a domain client account, or
there is network trouble

In the latter case, you probably need to set the box to the
computer name and logon as the local administrator to sort that
out.

Cached credentials are created automatically after you have made
a successful domain logon, and it means that the machine will
still accept you as a domain user even if it can't contact a
domain controller the next time you try to logon to the domain.
One of its main uses is that you can logon as a domain admin to
fix network problems rather than having to look up the machine
local admin name and password from the list in the company safe.
.

Relevant Pages

  • Re: Logon Server Unavailable
    ... There are currently no logon servers available to service ... You use a office laptop to connect the office VPN, when you map a network ... you may receive this message: "This account is the ... The server is not configured for transactions"> "A domain controller for your domain could not be contacted" ...
    (microsoft.public.windows.server.general)
  • Re: Logon Server Unavailable
    ... There are currently no logon servers available to service ... You use a office laptop to connect the office VPN, when you map a network ... you may receive this message: "This account is the ... The server is not configured for transactions"> "A domain controller for your domain could not be contacted" ...
    (microsoft.public.windows.server.dns)
  • Re: Logon Server Unavailable
    ... There are currently no logon servers available to service ... You use a office laptop to connect the office VPN, when you map a network ... you may receive this message: "This account is the ... The server is not configured for transactions"> "A domain controller for your domain could not be contacted" ...
    (microsoft.public.windows.server.networking)
  • Re: ATTN : Microsoft - Security Event 529....Second Request for help....
    ... According to the events, the logon ... failure is from the local machine account. ... disconnected from the network. ... Security Event ID 529 is a failure audit for logon/logoff. ...
    (microsoft.public.windows.server.sbs)
  • Re: Logon Server Unavailable
    ... >> More Connections Can Be Made At This Time ... >> The network folder specified is currently mapped using a different user ... >> account in its primary domain is missing or the password on that account ... >> There are currently no logon servers available to service the logon ...
    (microsoft.public.windows.server.general)
Loading