I have a Windows XP Pro machine that I use for work. I was trying to figure
out why it wasn't able to see any of the other computers on my home network
when I noticed that it was configured as a member of a domain as opposed to
the default MSHOME workgroup. I changed the settings to make the machine a
member of the workgroup and restarted. Now when I try to log on to the
computer at start up I am told.....The system could not log you on. Make
sure your User name and domain are correct, then type your password again.

Help.....is there any way to get past the logon screen so I can change back
to the correct domain?

Thanks in advance!!!

This problem can now only be solved by someone with either a valid local
logon name and password or by your network administrator by re-joining it to
the domain. Once this is done please let your network administrator know
what you're doing and why, the odds are that they'll help you accomplish it
in the best and safest manner.

--
Richard G. Harper [MVP Shell/User] (E-Mail Removed)
* PLEASE post all messages and replies in the newsgroups
* for the benefit of all. Private mail is usually not replied to.
* My website, such as it is ... http://rgharper.mvps.org/
* HELP us help YOU ... http://www.dts-l.org/goodpost.htm


"Rich3120" <(E-Mail Removed)> wrote in message
news7290970-9698-4758-A0C9-(E-Mail Removed)...
>I have a Windows XP Pro machine that I use for work. I was trying to
>figure
> out why it wasn't able to see any of the other computers on my home
> network
> when I noticed that it was configured as a member of a domain as opposed
> to
> the default MSHOME workgroup. I changed the settings to make the machine
> a
> member of the workgroup and restarted. Now when I try to log on to the
> computer at start up I am told.....The system could not log you on. Make
> sure your User name and domain are correct, then type your password again.
>
> Help.....is there any way to get past the logon screen so I can change
> back
> to the correct domain?
>
> Thanks in advance!!!

Forgive me for being obtuse but rejoining the domain would be the solution
if I was not able to access the network. At this point I am not able to get
past the logon screen.

Thanks for the help!

"Richard G. Harper" wrote:

> This problem can now only be solved by someone with either a valid local
> logon name and password or by your network administrator by re-joining it to
> the domain. Once this is done please let your network administrator know
> what you're doing and why, the odds are that they'll help you accomplish it
> in the best and safest manner.
>
> --
> Richard G. Harper [MVP Shell/User] (E-Mail Removed)
> * PLEASE post all messages and replies in the newsgroups
> * for the benefit of all. Private mail is usually not replied to.
> * My website, such as it is ... http://rgharper.mvps.org/
> * HELP us help YOU ... http://www.dts-l.org/goodpost.htm
>
>
> "Rich3120" <(E-Mail Removed)> wrote in message
> news7290970-9698-4758-A0C9-(E-Mail Removed)...
> >I have a Windows XP Pro machine that I use for work. I was trying to
> >figure
> > out why it wasn't able to see any of the other computers on my home
> > network
> > when I noticed that it was configured as a member of a domain as opposed
> > to
> > the default MSHOME workgroup. I changed the settings to make the machine
> > a
> > member of the workgroup and restarted. Now when I try to log on to the
> > computer at start up I am told.....The system could not log you on. Make
> > sure your User name and domain are correct, then type your password again.
> >
> > Help.....is there any way to get past the logon screen so I can change
> > back
> > to the correct domain?
> >
> > Thanks in advance!!!
>
>
>

Have you tried entering the username as administrator and leaving the
password blank?

"Rich3120" wrote:

>
> Forgive me for being obtuse but rejoining the domain would be the solution
> if I was not able to access the network. At this point I am not able to get
> past the logon screen.
>
> Thanks for the help!
>
> "Richard G. Harper" wrote:
>
> > This problem can now only be solved by someone with either a valid local
> > logon name and password or by your network administrator by re-joining it to
> > the domain. Once this is done please let your network administrator know
> > what you're doing and why, the odds are that they'll help you accomplish it
> > in the best and safest manner.
> >
> > --
> > Richard G. Harper [MVP Shell/User] (E-Mail Removed)
> > * PLEASE post all messages and replies in the newsgroups
> > * for the benefit of all. Private mail is usually not replied to.
> > * My website, such as it is ... http://rgharper.mvps.org/
> > * HELP us help YOU ... http://www.dts-l.org/goodpost.htm
> >
> >
> > "Rich3120" <(E-Mail Removed)> wrote in message
> > news7290970-9698-4758-A0C9-(E-Mail Removed)...
> > >I have a Windows XP Pro machine that I use for work. I was trying to
> > >figure
> > > out why it wasn't able to see any of the other computers on my home
> > > network
> > > when I noticed that it was configured as a member of a domain as opposed
> > > to
> > > the default MSHOME workgroup. I changed the settings to make the machine
> > > a
> > > member of the workgroup and restarted. Now when I try to log on to the
> > > computer at start up I am told.....The system could not log you on. Make
> > > sure your User name and domain are correct, then type your password again.
> > >
> > > Help.....is there any way to get past the logon screen so I can change
> > > back
> > > to the correct domain?
> > >
> > > Thanks in advance!!!
> >
> >
> >

As I said - the only possible solutions involve someone who has a valid
local logon for the computer. Apparently you don't. That means you're
going to have to take the computer back in and 'fess up to your mistake.

--
Richard G. Harper [MVP Shell/User] (E-Mail Removed)
* PLEASE post all messages and replies in the newsgroups
* for the benefit of all. Private mail is usually not replied to.
* My website, such as it is ... http://rgharper.mvps.org/
* HELP us help YOU ... http://www.dts-l.org/goodpost.htm


"Rich3120" <(E-Mail Removed)> wrote in message
news:C3111481-7A6C-4EF2-815C-(E-Mail Removed)...
>
> Forgive me for being obtuse but rejoining the domain would be the solution
> if I was not able to access the network. At this point I am not able to
> get
> past the logon screen.
>
> Thanks for the help!
>
> "Richard G. Harper" wrote:
>
>> This problem can now only be solved by someone with either a valid local
>> logon name and password or by your network administrator by re-joining it
>> to
>> the domain. Once this is done please let your network administrator know
>> what you're doing and why, the odds are that they'll help you accomplish
>> it
>> in the best and safest manner.
>>
>> --
>> Richard G. Harper [MVP Shell/User] (E-Mail Removed)
>> * PLEASE post all messages and replies in the newsgroups
>> * for the benefit of all. Private mail is usually not replied to.
>> * My website, such as it is ... http://rgharper.mvps.org/
>> * HELP us help YOU ... http://www.dts-l.org/goodpost.htm
>>
>>
>> "Rich3120" <(E-Mail Removed)> wrote in message
>> news7290970-9698-4758-A0C9-(E-Mail Removed)...
>> >I have a Windows XP Pro machine that I use for work. I was trying to
>> >figure
>> > out why it wasn't able to see any of the other computers on my home
>> > network
>> > when I noticed that it was configured as a member of a domain as
>> > opposed
>> > to
>> > the default MSHOME workgroup. I changed the settings to make the
>> > machine
>> > a
>> > member of the workgroup and restarted. Now when I try to log on to the
>> > computer at start up I am told.....The system could not log you on.
>> > Make
>> > sure your User name and domain are correct, then type your password
>> > again.
>> >
>> > Help.....is there any way to get past the logon screen so I can change
>> > back
>> > to the correct domain?
>> >
>> > Thanks in advance!!!
>>
>>
>>

UKDaz wrote:

> Have you tried entering the username as administrator and leaving the
> password blank?
>

You're missing the point. The OP removed his work computer from the
domain, mistakenly thinking this was a Good Thing and would let him use
his home network. There is no chance that a sysadmin would have a null
administrator password on a domain account. There is a good chance that
no local accounts exist on the machine, which is good security
practice.

As Mr. Harper said, the OP will have to ask his sysadmin to rejoin the
computer to the domain. Once he has done that, he can use the computer
at home by doing this:

Information from MVP Lanwench:

Note - you don't need to change to a workgroup just to access resources
on it. You shouldn't play with your laptop's network settings at all.
Once you've logged in using your domain account (using cached
credentials), and have an IP address on the home network, you can map
drives, use printers, whatnot, very easily - one way, in a command
line:

net use x: \\computername\sharename /user:computername\username <enter>

MS KB article about the Net Use command - http://tinyurl.com/3bpnj

Malke
--
MS MVP - Windows Shell/User
Elephant Boy Computers
www.elephantboycomputers.com
"Don't Panic!"

I imagine that the previous post is correct, there is likely no valid local
logon for this computer. I wish it were as simple as "'fessing up" to a
mistake. My machine and I live in Colorado and my employer is in the Boston
area so "taking it in" is not an option.

"Richard G. Harper" wrote:

> As I said - the only possible solutions involve someone who has a valid
> local logon for the computer. Apparently you don't. That means you're
> going to have to take the computer back in and 'fess up to your mistake.
>
> --
> Richard G. Harper [MVP Shell/User] (E-Mail Removed)
> * PLEASE post all messages and replies in the newsgroups
> * for the benefit of all. Private mail is usually not replied to.
> * My website, such as it is ... http://rgharper.mvps.org/
> * HELP us help YOU ... http://www.dts-l.org/goodpost.htm
>
>
> "Rich3120" <(E-Mail Removed)> wrote in message
> news:C3111481-7A6C-4EF2-815C-(E-Mail Removed)...
> >
> > Forgive me for being obtuse but rejoining the domain would be the solution
> > if I was not able to access the network. At this point I am not able to
> > get
> > past the logon screen.
> >
> > Thanks for the help!
> >
> > "Richard G. Harper" wrote:
> >
> >> This problem can now only be solved by someone with either a valid local
> >> logon name and password or by your network administrator by re-joining it
> >> to
> >> the domain. Once this is done please let your network administrator know
> >> what you're doing and why, the odds are that they'll help you accomplish
> >> it
> >> in the best and safest manner.
> >>
> >> --
> >> Richard G. Harper [MVP Shell/User] (E-Mail Removed)
> >> * PLEASE post all messages and replies in the newsgroups
> >> * for the benefit of all. Private mail is usually not replied to.
> >> * My website, such as it is ... http://rgharper.mvps.org/
> >> * HELP us help YOU ... http://www.dts-l.org/goodpost.htm
> >>
> >>
> >> "Rich3120" <(E-Mail Removed)> wrote in message
> >> news7290970-9698-4758-A0C9-(E-Mail Removed)...
> >> >I have a Windows XP Pro machine that I use for work. I was trying to
> >> >figure
> >> > out why it wasn't able to see any of the other computers on my home
> >> > network
> >> > when I noticed that it was configured as a member of a domain as
> >> > opposed
> >> > to
> >> > the default MSHOME workgroup. I changed the settings to make the
> >> > machine
> >> > a
> >> > member of the workgroup and restarted. Now when I try to log on to the
> >> > computer at start up I am told.....The system could not log you on.
> >> > Make
> >> > sure your User name and domain are correct, then type your password
> >> > again.
> >> >
> >> > Help.....is there any way to get past the logon screen so I can change
> >> > back
> >> > to the correct domain?
> >> >
> >> > Thanks in advance!!!
> >>
> >>
> >>
>
>
>

Uh ... I believe that at this point an old saying about a creek combined
with a lack of paddles is going to be involved. Check with the domain
administrators, I can't believe they would not leave one local logon
(Administrator) that can be accessed in an emergency of this type.

--
Richard G. Harper [MVP Shell/User] (E-Mail Removed)
* PLEASE post all messages and replies in the newsgroups
* for the benefit of all. Private mail is usually not replied to.
* My website, such as it is ... http://rgharper.mvps.org/
* HELP us help YOU ... http://www.dts-l.org/goodpost.htm


"Rich3120" <(E-Mail Removed)> wrote in message
news:75E009A2-2253-477B-94F0-(E-Mail Removed)...
>I imagine that the previous post is correct, there is likely no valid local
> logon for this computer. I wish it were as simple as "'fessing up" to a
> mistake. My machine and I live in Colorado and my employer is in the
> Boston
> area so "taking it in" is not an option.
>
> "Richard G. Harper" wrote:
>
>> As I said - the only possible solutions involve someone who has a valid
>> local logon for the computer. Apparently you don't. That means you're
>> going to have to take the computer back in and 'fess up to your mistake.
>>
>> --
>> Richard G. Harper [MVP Shell/User] (E-Mail Removed)
>> * PLEASE post all messages and replies in the newsgroups
>> * for the benefit of all. Private mail is usually not replied to.
>> * My website, such as it is ... http://rgharper.mvps.org/
>> * HELP us help YOU ... http://www.dts-l.org/goodpost.htm
>>
>>
>> "Rich3120" <(E-Mail Removed)> wrote in message
>> news:C3111481-7A6C-4EF2-815C-(E-Mail Removed)...
>> >
>> > Forgive me for being obtuse but rejoining the domain would be the
>> > solution
>> > if I was not able to access the network. At this point I am not able
>> > to
>> > get
>> > past the logon screen.
>> >
>> > Thanks for the help!
>> >
>> > "Richard G. Harper" wrote:
>> >
>> >> This problem can now only be solved by someone with either a valid
>> >> local
>> >> logon name and password or by your network administrator by re-joining
>> >> it
>> >> to
>> >> the domain. Once this is done please let your network administrator
>> >> know
>> >> what you're doing and why, the odds are that they'll help you
>> >> accomplish
>> >> it
>> >> in the best and safest manner.
>> >>
>> >> --
>> >> Richard G. Harper [MVP Shell/User] (E-Mail Removed)
>> >> * PLEASE post all messages and replies in the newsgroups
>> >> * for the benefit of all. Private mail is usually not replied to.
>> >> * My website, such as it is ... http://rgharper.mvps.org/
>> >> * HELP us help YOU ... http://www.dts-l.org/goodpost.htm
>> >>
>> >>
>> >> "Rich3120" <(E-Mail Removed)> wrote in message
>> >> news7290970-9698-4758-A0C9-(E-Mail Removed)...
>> >> >I have a Windows XP Pro machine that I use for work. I was trying to
>> >> >figure
>> >> > out why it wasn't able to see any of the other computers on my home
>> >> > network
>> >> > when I noticed that it was configured as a member of a domain as
>> >> > opposed
>> >> > to
>> >> > the default MSHOME workgroup. I changed the settings to make the
>> >> > machine
>> >> > a
>> >> > member of the workgroup and restarted. Now when I try to log on to
>> >> > the
>> >> > computer at start up I am told.....The system could not log you on.
>> >> > Make
>> >> > sure your User name and domain are correct, then type your password
>> >> > again.
>> >> >
>> >> > Help.....is there any way to get past the logon screen so I can
>> >> > change
>> >> > back
>> >> > to the correct domain?
>> >> >
>> >> > Thanks in advance!!!
>> >>
>> >>
>> >>
>>
>>
>>

You're absolutely correct about the need for (and lack of paddles).
Fortunately there was an admin logon available that allowed me to get to my
critical files and download them to another machine. The laptop is on it's
way (via FedEx) back to the admin to be re-added to the domain.

Thanks for your assistance.

"Richard G. Harper" wrote:

> Uh ... I believe that at this point an old saying about a creek combined
> with a lack of paddles is going to be involved. Check with the domain
> administrators, I can't believe they would not leave one local logon
> (Administrator) that can be accessed in an emergency of this type.
>
> --
> Richard G. Harper [MVP Shell/User] (E-Mail Removed)
> * PLEASE post all messages and replies in the newsgroups
> * for the benefit of all. Private mail is usually not replied to.
> * My website, such as it is ... http://rgharper.mvps.org/
> * HELP us help YOU ... http://www.dts-l.org/goodpost.htm
>
>
> "Rich3120" <(E-Mail Removed)> wrote in message
> news:75E009A2-2253-477B-94F0-(E-Mail Removed)...
> >I imagine that the previous post is correct, there is likely no valid local
> > logon for this computer. I wish it were as simple as "'fessing up" to a
> > mistake. My machine and I live in Colorado and my employer is in the
> > Boston
> > area so "taking it in" is not an option.
> >
> > "Richard G. Harper" wrote:
> >
> >> As I said - the only possible solutions involve someone who has a valid
> >> local logon for the computer. Apparently you don't. That means you're
> >> going to have to take the computer back in and 'fess up to your mistake.
> >>
> >> --
> >> Richard G. Harper [MVP Shell/User] (E-Mail Removed)
> >> * PLEASE post all messages and replies in the newsgroups
> >> * for the benefit of all. Private mail is usually not replied to.
> >> * My website, such as it is ... http://rgharper.mvps.org/
> >> * HELP us help YOU ... http://www.dts-l.org/goodpost.htm
> >>
> >>
> >> "Rich3120" <(E-Mail Removed)> wrote in message
> >> news:C3111481-7A6C-4EF2-815C-(E-Mail Removed)...
> >> >
> >> > Forgive me for being obtuse but rejoining the domain would be the
> >> > solution
> >> > if I was not able to access the network. At this point I am not able
> >> > to
> >> > get
> >> > past the logon screen.
> >> >
> >> > Thanks for the help!
> >> >
> >> > "Richard G. Harper" wrote:
> >> >
> >> >> This problem can now only be solved by someone with either a valid
> >> >> local
> >> >> logon name and password or by your network administrator by re-joining
> >> >> it
> >> >> to
> >> >> the domain. Once this is done please let your network administrator
> >> >> know
> >> >> what you're doing and why, the odds are that they'll help you
> >> >> accomplish
> >> >> it
> >> >> in the best and safest manner.
> >> >>
> >> >> --
> >> >> Richard G. Harper [MVP Shell/User] (E-Mail Removed)
> >> >> * PLEASE post all messages and replies in the newsgroups
> >> >> * for the benefit of all. Private mail is usually not replied to.
> >> >> * My website, such as it is ... http://rgharper.mvps.org/
> >> >> * HELP us help YOU ... http://www.dts-l.org/goodpost.htm
> >> >>
> >> >>
> >> >> "Rich3120" <(E-Mail Removed)> wrote in message
> >> >> news7290970-9698-4758-A0C9-(E-Mail Removed)...
> >> >> >I have a Windows XP Pro machine that I use for work. I was trying to
> >> >> >figure
> >> >> > out why it wasn't able to see any of the other computers on my home
> >> >> > network
> >> >> > when I noticed that it was configured as a member of a domain as
> >> >> > opposed
> >> >> > to
> >> >> > the default MSHOME workgroup. I changed the settings to make the
> >> >> > machine
> >> >> > a
> >> >> > member of the workgroup and restarted. Now when I try to log on to
> >> >> > the
> >> >> > computer at start up I am told.....The system could not log you on.
> >> >> > Make
> >> >> > sure your User name and domain are correct, then type your password
> >> >> > again.
> >> >> >
> >> >> > Help.....is there any way to get past the logon screen so I can
> >> >> > change
> >> >> > back
> >> >> > to the correct domain?
> >> >> >
> >> >> > Thanks in advance!!!
> >> >>
> >> >>
> >> >>
> >>
> >>
> >>
>
>
>

I'm glad all will be well (enough) in the end for you.

--
Richard G. Harper [MVP Shell/User] (E-Mail Removed)
* PLEASE post all messages and replies in the newsgroups
* for the benefit of all. Private mail is usually not replied to.
* My website, such as it is ... http://rgharper.mvps.org/
* HELP us help YOU ... http://www.dts-l.org/goodpost.htm


"Rich3120" <(E-Mail Removed)> wrote in message
news:6057DB75-24B2-4176-A374-(E-Mail Removed)...
> You're absolutely correct about the need for (and lack of paddles).
> Fortunately there was an admin logon available that allowed me to get to
> my
> critical files and download them to another machine. The laptop is on
> it's
> way (via FedEx) back to the admin to be re-added to the domain.
>
> Thanks for your assistance.
>
> "Richard G. Harper" wrote:
>
>> Uh ... I believe that at this point an old saying about a creek combined
>> with a lack of paddles is going to be involved. Check with the domain
>> administrators, I can't believe they would not leave one local logon
>> (Administrator) that can be accessed in an emergency of this type.
>>
>> --
>> Richard G. Harper [MVP Shell/User] (E-Mail Removed)
>> * PLEASE post all messages and replies in the newsgroups
>> * for the benefit of all. Private mail is usually not replied to.
>> * My website, such as it is ... http://rgharper.mvps.org/
>> * HELP us help YOU ... http://www.dts-l.org/goodpost.htm
>>
>>
>> "Rich3120" <(E-Mail Removed)> wrote in message
>> news:75E009A2-2253-477B-94F0-(E-Mail Removed)...
>> >I imagine that the previous post is correct, there is likely no valid
>> >local
>> > logon for this computer. I wish it were as simple as "'fessing up" to
>> > a
>> > mistake. My machine and I live in Colorado and my employer is in the
>> > Boston
>> > area so "taking it in" is not an option.
>> >
>> > "Richard G. Harper" wrote:
>> >
>> >> As I said - the only possible solutions involve someone who has a
>> >> valid
>> >> local logon for the computer. Apparently you don't. That means
>> >> you're
>> >> going to have to take the computer back in and 'fess up to your
>> >> mistake.
>> >>
>> >> --
>> >> Richard G. Harper [MVP Shell/User] (E-Mail Removed)
>> >> * PLEASE post all messages and replies in the newsgroups
>> >> * for the benefit of all. Private mail is usually not replied to.
>> >> * My website, such as it is ... http://rgharper.mvps.org/
>> >> * HELP us help YOU ... http://www.dts-l.org/goodpost.htm
>> >>
>> >>
>> >> "Rich3120" <(E-Mail Removed)> wrote in message
>> >> news:C3111481-7A6C-4EF2-815C-(E-Mail Removed)...
>> >> >
>> >> > Forgive me for being obtuse but rejoining the domain would be the
>> >> > solution
>> >> > if I was not able to access the network. At this point I am not
>> >> > able
>> >> > to
>> >> > get
>> >> > past the logon screen.
>> >> >
>> >> > Thanks for the help!
>> >> >
>> >> > "Richard G. Harper" wrote:
>> >> >
>> >> >> This problem can now only be solved by someone with either a valid
>> >> >> local
>> >> >> logon name and password or by your network administrator by
>> >> >> re-joining
>> >> >> it
>> >> >> to
>> >> >> the domain. Once this is done please let your network
>> >> >> administrator
>> >> >> know
>> >> >> what you're doing and why, the odds are that they'll help you
>> >> >> accomplish
>> >> >> it
>> >> >> in the best and safest manner.
>> >> >>
>> >> >> --
>> >> >> Richard G. Harper [MVP Shell/User] (E-Mail Removed)
>> >> >> * PLEASE post all messages and replies in the newsgroups
>> >> >> * for the benefit of all. Private mail is usually not replied to.
>> >> >> * My website, such as it is ... http://rgharper.mvps.org/
>> >> >> * HELP us help YOU ... http://www.dts-l.org/goodpost.htm
>> >> >>
>> >> >>
>> >> >> "Rich3120" <(E-Mail Removed)> wrote in message
>> >> >> news7290970-9698-4758-A0C9-(E-Mail Removed)...
>> >> >> >I have a Windows XP Pro machine that I use for work. I was trying
>> >> >> >to
>> >> >> >figure
>> >> >> > out why it wasn't able to see any of the other computers on my
>> >> >> > home
>> >> >> > network
>> >> >> > when I noticed that it was configured as a member of a domain as
>> >> >> > opposed
>> >> >> > to
>> >> >> > the default MSHOME workgroup. I changed the settings to make the
>> >> >> > machine
>> >> >> > a
>> >> >> > member of the workgroup and restarted. Now when I try to log on
>> >> >> > to
>> >> >> > the
>> >> >> > computer at start up I am told.....The system could not log you
>> >> >> > on.
>> >> >> > Make
>> >> >> > sure your User name and domain are correct, then type your
>> >> >> > password
>> >> >> > again.
>> >> >> >
>> >> >> > Help.....is there any way to get past the logon screen so I can
>> >> >> > change
>> >> >> > back
>> >> >> > to the correct domain?
>> >> >> >
>> >> >> > Thanks in advance!!!
>> >> >>
>> >> >>
>> >> >>
>> >>
>> >>
>> >>
>>
>>
>>