|
Home > Archive > microsoft.public.cert.exams.mcse > June 2002 > Domain not available
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Domain not available
|
|
| Don Julio 2002-06-22, 6:40 pm |
| Because I messed up i had to format my Win2k partition on my domain
controller in my home lab. I then reinstalled with all my previous
settings. I run dcpromo and created a domain with the same name as
previous.
Now when I log on the domain from my client PC (win2k prof) as
administrator, everthing is fine. I can browse to my DC perfectly.
However, if I try to log on from my client PC as a user which I created in
Active Directory of course, I get the following message;
"Logon Message, The system cannot log you on now because the domain <domain
name> is not available"
The strange thing though is if i try to log on the domain from the client as
a user which does not exist i get the standard "..........make sure your
username and domain are correct blah blah..."
My conclusion is that the sysem does seem to recognise that a user exists
but will not log them on but other than that I am well and truly stuck
Also I can ping from both PC's ok
Any suggestions please
| |
| Kerry Hoskin 2002-06-22, 6:40 pm |
| you'll need to add your client PC's computer account to the domain
Kerry
"Don Julio" <me@home.com> wrote in message
news:eVGJ1gF5BHA.1660@tkmsftngp05...
> Because I messed up i had to format my Win2k partition on my domain
> controller in my home lab. I then reinstalled with all my previous
> settings. I run dcpromo and created a domain with the same name as
> previous.
>
> Now when I log on the domain from my client PC (win2k prof) as
> administrator, everthing is fine. I can browse to my DC perfectly.
>
> However, if I try to log on from my client PC as a user which I created in
> Active Directory of course, I get the following message;
> "Logon Message, The system cannot log you on now because the domain
<domain
> name> is not available"
>
> The strange thing though is if i try to log on the domain from the client
as
> a user which does not exist i get the standard "..........make sure your
> username and domain are correct blah blah..."
>
> My conclusion is that the sysem does seem to recognise that a user exists
> but will not log them on but other than that I am well and truly stuck
>
> Also I can ping from both PC's ok
>
> Any suggestions please
>
>
>
| |
| Don Julio 2002-06-22, 6:40 pm |
| I hope I haven't misunderstood you, but I have created these accounts in the
active directory on my DC which should make them a domain/user. I can't
think that I am doing anything different from when it worked perfectly
before I had to wipe the system.
thanks
"Kerry Hoskin" <kjho@pml.ac.uk> wrote in message
news:O88klOG5BHA.1304@tkmsftngp04...
> you'll need to add your client PC's computer account to the domain
>
> Kerry
>
> "Don Julio" <me@home.com> wrote in message
> news:eVGJ1gF5BHA.1660@tkmsftngp05...
> > Because I messed up i had to format my Win2k partition on my domain
> > controller in my home lab. I then reinstalled with all my previous
> > settings. I run dcpromo and created a domain with the same name as
> > previous.
> >
> > Now when I log on the domain from my client PC (win2k prof) as
> > administrator, everthing is fine. I can browse to my DC perfectly.
> >
> > However, if I try to log on from my client PC as a user which I created
in
> > Active Directory of course, I get the following message;
> > "Logon Message, The system cannot log you on now because the domain
> <domain
> > name> is not available"
> >
> > The strange thing though is if i try to log on the domain from the
client
> as
> > a user which does not exist i get the standard "..........make sure your
> > username and domain are correct blah blah..."
> >
> > My conclusion is that the sysem does seem to recognise that a user
exists
> > but will not log them on but other than that I am well and truly stuck
> >
> > Also I can ping from both PC's ok
> >
> > Any suggestions please
> >
> >
> >
>
>
| |
| Paul Adare 2002-06-22, 6:40 pm |
| In article <eSoKk#G5BHA.2684@tkmsftngp04>, me@work.com says...
> I hope I haven't misunderstood you, but I have created these accounts in the
> active directory on my DC which should make them a domain/user. I can't
> think that I am doing anything different from when it worked perfectly
> before I had to wipe the system.
>
When you wiped the system, you wiped all accounts, including computer
accounts. You need to set the workstation to belong to a workgroup, and
then join it to the domain.
--
Paul Adare
A fine is a tax for doing wrong. A tax is a fine for doing well.
| |
| Don Julio 2002-06-22, 6:40 pm |
| I will try this when I get home
many thanks
"Paul Adare" <padare@newsguy.com> wrote in message
news:MPG.17248cd4997eeb069896d7@msnews.microsoft.com...
> In article <eSoKk#G5BHA.2684@tkmsftngp04>, me@work.com says...
> > I hope I haven't misunderstood you, but I have created these accounts in
the
> > active directory on my DC which should make them a domain/user. I can't
> > think that I am doing anything different from when it worked perfectly
> > before I had to wipe the system.
> >
>
> When you wiped the system, you wiped all accounts, including computer
> accounts. You need to set the workstation to belong to a workgroup, and
> then join it to the domain.
>
> --
> Paul Adare
> A fine is a tax for doing wrong. A tax is a fine for doing well.
| |
| Don Julio 2002-06-22, 6:40 pm |
| I'm just trying to understand what has gone on, presumably the problem has
to do with the client PC SID? and if so do I have to remove the current
computer object from Active Directory or is it dynamic?
Hope this makes sense, i'm not very good at wording things.
"Paul Adare" <padare@newsguy.com> wrote in message
news:MPG.17248cd4997eeb069896d7@msnews.microsoft.com...
> In article <eSoKk#G5BHA.2684@tkmsftngp04>, me@work.com says...
> > I hope I haven't misunderstood you, but I have created these accounts in
the
> > active directory on my DC which should make them a domain/user. I can't
> > think that I am doing anything different from when it worked perfectly
> > before I had to wipe the system.
> >
>
> When you wiped the system, you wiped all accounts, including computer
> accounts. You need to set the workstation to belong to a workgroup, and
> then join it to the domain.
>
> --
> Paul Adare
> A fine is a tax for doing wrong. A tax is a fine for doing well.
| |
| Kerry Hoskin 2002-06-22, 6:40 pm |
| delete the current computer object (if one exists) remove the client PC from
the domain, i.e put it in a work group, reboot, then add it back to the
domain and reboot
Kerry
"Don Julio" <me@work.com> wrote in message
news:eaPiS1H5BHA.2388@tkmsftngp04...
> I'm just trying to understand what has gone on, presumably the problem has
> to do with the client PC SID? and if so do I have to remove the current
> computer object from Active Directory or is it dynamic?
>
> Hope this makes sense, i'm not very good at wording things.
>
>
> "Paul Adare" <padare@newsguy.com> wrote in message
> news:MPG.17248cd4997eeb069896d7@msnews.microsoft.com...
> > In article <eSoKk#G5BHA.2684@tkmsftngp04>, me@work.com says...
> > > I hope I haven't misunderstood you, but I have created these accounts
in
> the
> > > active directory on my DC which should make them a domain/user. I
can't
> > > think that I am doing anything different from when it worked perfectly
> > > before I had to wipe the system.
> > >
> >
> > When you wiped the system, you wiped all accounts, including computer
> > accounts. You need to set the workstation to belong to a workgroup, and
> > then join it to the domain.
> >
> > --
> > Paul Adare
> > A fine is a tax for doing wrong. A tax is a fine for doing well.
>
>
| |
| Paul Adare 2002-06-22, 6:40 pm |
| In article <eaPiS1H5BHA.2388@tkmsftngp04>, me@work.com says...
> I'm just trying to understand what has gone on, presumably the problem has
> to do with the client PC SID? and if so do I have to remove the current
> computer object from Active Directory or is it dynamic?
>
If, as you said, you wiped the domain controller completely, then as I
said, you no longer have an account for your workstation in the domain.
You deleted it when you wiped the DC.
--
Paul Adare
A fine is a tax for doing wrong. A tax is a fine for doing well.
| |
| Don Julio 2002-06-22, 6:40 pm |
| Many thanks both of you
"Paul Adare" <padare@newsguy.com> wrote in message
news:MPG.17249bd5c7b09fcf9896d8@msnews.microsoft.com...
> In article <eaPiS1H5BHA.2388@tkmsftngp04>, me@work.com says...
> > I'm just trying to understand what has gone on, presumably the problem
has
> > to do with the client PC SID? and if so do I have to remove the current
> > computer object from Active Directory or is it dynamic?
> >
>
> If, as you said, you wiped the domain controller completely, then as I
> said, you no longer have an account for your workstation in the domain.
> You deleted it when you wiped the DC.
>
> --
> Paul Adare
> A fine is a tax for doing wrong. A tax is a fine for doing well.
| |
| Don Julio 2002-06-22, 6:40 pm |
| Kerry, Paul
It worked perfectly thank you. I won't embarrass myself by telling you how
long I spent trying to fix this :-)
"Don Julio" <me@work.com> wrote in message
news:uObxdAI5BHA.2388@tkmsftngp04...
> Many thanks both of you
>
>
> "Paul Adare" <padare@newsguy.com> wrote in message
> news:MPG.17249bd5c7b09fcf9896d8@msnews.microsoft.com...
> > In article <eaPiS1H5BHA.2388@tkmsftngp04>, me@work.com says...
> > > I'm just trying to understand what has gone on, presumably the problem
> has
> > > to do with the client PC SID? and if so do I have to remove the
current
> > > computer object from Active Directory or is it dynamic?
> > >
> >
> > If, as you said, you wiped the domain controller completely, then as I
> > said, you no longer have an account for your workstation in the domain.
> > You deleted it when you wiped the DC.
> >
> > --
> > Paul Adare
> > A fine is a tax for doing wrong. A tax is a fine for doing well.
>
>
|
|
|
|
|