Re: Workstation doesn't log onto network

From: Steven L Umbach (n9rouz_at_nscomcast.net)
Date: 12/01/03 

Date: Mon, 01 Dec 2003 00:05:35 GMT

Don't confuse the account user name with the logon name. Just make sure that the
actual logon name and password that a user uses to logon to their computer is exactly
the same in the Active Directory Users and Computers account for that user. There are
ways to copy profiles, but it differs from operating system. See links below for more
info, though I do not think you need to copy any profiles. -- Steve

http://support.microsoft.com/default.aspx?scid=kb;en-us;811151 --- For XP.
http://support.microsoft.com/default.aspx?kbid=255095 -- W2K, must be logged on as
administrator.

"David Bolt" <davebolt@compuserve.com> wrote in message
news:utz2t44tDHA.1996@TK2MSFTNGP12.phx.gbl...
> Steve,
> I think this one is the answer. Although the account display name is the
> same as an account name on the server, I think the actual name, used in
> re-establishing connections, is different.
> Now, do you happen to know a good way of getting all the settings from one
> user profile to another? I am not at all convinced that the file and setting
> transfer wizard is the solution since it seems to keep per user data for the
> same users on the 'new' machine. What I want is a way of setting up a new
> user with all the settings from an existing user, instead of having to
> install all the applications all over again.
> Thanks
> Dave
> "Steven Umbach" <n9zrou@nscomcast.com> wrote in message
> news:mVTxb.249589$275.921924@attbi_s53...
> > A Certificate Authority would not be able to remedy your situation. A CA
> issues
> > user and machine certificates for such things as smart cards, EFS file
> > encryption, and L2TP vpn. I have no experience with XP home but I know
> that
> > users of XP home can not logon to a domain directly nor can the machine
> itself
> > join the domain. However if there is a user account on the domain
> controller
> > that has the same logon name and password that the user logons to XP Home,
> they
> > should be able to access the network resources that account has
> permissions to
> > without a credential prompt I believe. --- Steve
> >
> > http://www.wown.info/j_helmig/wxphdoms.htm
> >
> http://www.microsoft.com/windowsxp/home/evaluation/overviews/xpindomain.asp
> >
> > "David Bolt" <davebolt@compuserve.com> wrote in message
> > news:Ohe0T6htDHA.2252@TK2MSFTNGP09.phx.gbl...
> > > I manage a network where the users all supply their own machines. We
> have no
> > > control over OS on older machines so a number of workstations are
> running XP
> > > Home. Now, most of these work OK, but a couple do not seem to log on
> > > correctly. Since for instance workstations need to make use of network
> > > printers, this is a problem.
> > > So, any ideas what to look for to see why some machines connect but
> others
> > > don't until for instance I try to browse the network, at which point
> they
> > > ask for a network username and password.
> > > Server is Win2000 Advanced Server.
> > > I have now got a Certification Authority working, just, if that is any
> help.
> > > Thanks
> > > Dave
> > >
> > >
> >
> >
>
>

Relevant Pages

  • Re: Administrative blunder
    ... Enable the line that requires users to logon with a username and password. ... > settings on another user account. ... > in administrator in order to make the computer boot up with my old ...
    (microsoft.public.windowsxp.general)
  • Re: Swapping email accounts
    ... It's not exactly that the user is getting the "wrong email account," at ... The systems "remember" the last person to logon to each computer. ... not type in his user name, which is User1, since the computer "remembers" ... I realize that I will need to deal with the Outlook profiles, ...
    (microsoft.public.exchange2000.admin)
  • [EC-SA-01.2003] Windows XP "welcome screen" exposes the names of all the members of the l
    ... logon screen with what is called "Welcome Screen". ... (including the original administrator account, ... Using the "welcome screen" actually disables / ignores the security ...
    (Bugtraq)
  • 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: Is it really true that NTFS is secure?
    ... > and failure auditing starting with "Audit Account Management," and also try ... > The account Group got put back in the Administrator group again. ... > The logon to account: ...
    (microsoft.public.security)