this should be so simple..... but it ain't ... so far

  • Thread starter Thread starter kinda lost
  • Start date Start date
K

kinda lost

Guest
my 2000 server died and i built a new 2003 server with the old servers
computer name and ip address, install dns, wins, and dhcp all fine
i have all the AD user id's and passwords set up in the AD
i have 35 users that use to login to the old 2000 domain (mixed xp pro and
windows 2000 machines)

i can login sometimes as administrator and other times i get errors or
can't login at all

is there something on the workstations that identifiy them to the old server
and NOT to the new server

hope there is a simple fix for this

ps. i unjoined my xp workstation from the domain and then rejoined the
domain and then i could log on everytime without a problem

but i don't want to do that with 35 machines as it would be time consuming
and also setup a new profile for all machines
i just want to have the users login as they did before as the new 2003
server is configured that same as the old 2000 server, file paths, printers,
etc

thanks in advance
kinda lost
 
Re: this should be so simple..... but it ain't ... so far

You need all the computers to join the new domain.
Anthony,
http://www.airdesk.co.uk


"kinda lost" <kindalost@discussions.microsoft.com> wrote in message
news:7D51FA4E-F385-4075-89C4-F9DA44DF51A9@microsoft.com...
> my 2000 server died and i built a new 2003 server with the old servers
> computer name and ip address, install dns, wins, and dhcp all fine
> i have all the AD user id's and passwords set up in the AD
> i have 35 users that use to login to the old 2000 domain (mixed xp pro and
> windows 2000 machines)
>
> i can login sometimes as administrator and other times i get errors or
> can't login at all
>
> is there something on the workstations that identifiy them to the old
> server
> and NOT to the new server
>
> hope there is a simple fix for this
>
> ps. i unjoined my xp workstation from the domain and then rejoined the
> domain and then i could log on everytime without a problem
>
> but i don't want to do that with 35 machines as it would be time consuming
> and also setup a new profile for all machines
> i just want to have the users login as they did before as the new 2003
> server is configured that same as the old 2000 server, file paths,
> printers,
> etc
>
> thanks in advance
> kinda lost
>
>
 
Re: this should be so simple..... but it ain't ... so far

kinda lost wrote:
> my 2000 server died and i built a new 2003 server with the old servers
> computer name and ip address, install dns, wins, and dhcp all fine
> i have all the AD user id's and passwords set up in the AD
> i have 35 users that use to login to the old 2000 domain (mixed xp
> pro and windows 2000 machines)


You've created a comletly new domain even though you used the same
configuration settings. Unless you have another domain controller or a
recent complete backup, you'll have to join the rest of the workstations to
the new domain. Worse, you'll have to fix up the user profiles as they will
get a brand new one when the logon to the new domain for the first time.

Backups are really important, especially for smaller sites.


>
> i can login sometimes as administrator and other times i get errors
> or can't login at all
>
> is there something on the workstations that identifiy them to the old
> server and NOT to the new server
>
> hope there is a simple fix for this
>
> ps. i unjoined my xp workstation from the domain and then rejoined the
> domain and then i could log on everytime without a problem
>
> but i don't want to do that with 35 machines as it would be time
> consuming and also setup a new profile for all machines
> i just want to have the users login as they did before as the new 2003
> server is configured that same as the old 2000 server, file paths,
> printers, etc
>
> thanks in advance
> kinda lost

--
/kj
 
Re: this should be so simple..... but it ain't ... so far

i used the same exact domain name, just on a new machine

"kj [SBS MVP]" wrote:

> kinda lost wrote:
> > my 2000 server died and i built a new 2003 server with the old servers
> > computer name and ip address, install dns, wins, and dhcp all fine
> > i have all the AD user id's and passwords set up in the AD
> > i have 35 users that use to login to the old 2000 domain (mixed xp
> > pro and windows 2000 machines)
>
>
> You've created a comletly new domain even though you used the same
> configuration settings. Unless you have another domain controller or a
> recent complete backup, you'll have to join the rest of the workstations to
> the new domain. Worse, you'll have to fix up the user profiles as they will
> get a brand new one when the logon to the new domain for the first time.
>
> Backups are really important, especially for smaller sites.
>
>
> >
> > i can login sometimes as administrator and other times i get errors
> > or can't login at all
> >
> > is there something on the workstations that identifiy them to the old
> > server and NOT to the new server
> >
> > hope there is a simple fix for this
> >
> > ps. i unjoined my xp workstation from the domain and then rejoined the
> > domain and then i could log on everytime without a problem
> >
> > but i don't want to do that with 35 machines as it would be time
> > consuming and also setup a new profile for all machines
> > i just want to have the users login as they did before as the new 2003
> > server is configured that same as the old 2000 server, file paths,
> > printers, etc
> >
> > thanks in advance
> > kinda lost
>
> --
> /kj
>
>
>
 
Re: this should be so simple..... but it ain't ... so far

kinda lost wrote:
> i used the same exact domain name, just on a new machine

Right, but the domain name is just for the convenience of us humans. All the
computers care about is the "Domain Globally Unique Identifier" (GUID),
which is a unique number create when the domain is created.

All the computers will see this as a completely different domain no matter
what name or values you used when you installed again. Your only recourse is
having the ability to restore /recover the *exact* original domain from
backups. If you don't have one, or don't have another functioning domain
controller from the original domain, you are starting over from scratch.


>
> "kj [SBS MVP]" wrote:
>
>> kinda lost wrote:
>>> my 2000 server died and i built a new 2003 server with the old
>>> servers computer name and ip address, install dns, wins, and dhcp
>>> all fine
>>> i have all the AD user id's and passwords set up in the AD
>>> i have 35 users that use to login to the old 2000 domain (mixed xp
>>> pro and windows 2000 machines)
>>
>>
>> You've created a comletly new domain even though you used the same
>> configuration settings. Unless you have another domain controller or
>> a recent complete backup, you'll have to join the rest of the
>> workstations to the new domain. Worse, you'll have to fix up the
>> user profiles as they will get a brand new one when the logon to the
>> new domain for the first time.
>>
>> Backups are really important, especially for smaller sites.
>>
>>
>>>
>>> i can login sometimes as administrator and other times i get errors
>>> or can't login at all
>>>
>>> is there something on the workstations that identifiy them to the
>>> old server and NOT to the new server
>>>
>>> hope there is a simple fix for this
>>>
>>> ps. i unjoined my xp workstation from the domain and then rejoined
>>> the domain and then i could log on everytime without a problem
>>>
>>> but i don't want to do that with 35 machines as it would be time
>>> consuming and also setup a new profile for all machines
>>> i just want to have the users login as they did before as the new
>>> 2003 server is configured that same as the old 2000 server, file
>>> paths, printers, etc
>>>
>>> thanks in advance
>>> kinda lost
>>
>> --
>> /kj

--
/kj
 
Re: this should be so simple..... but it ain't ... so far

Hello kinda,

With the creation of a fresh installed 2003 server and making it domain controller
you also built a new fresh domain. Even if you choose the same servername,
ip address and domain name, it is a complete NEW domain with new Security
identifiers that are incompatible with the old SID's from the workstations.

So you have no other option as to join all workstations to the new domain
and create new user accounts for you users. With the administrator you can
copy the content from the old profiles to the new created user folders, so
that they can have the old data back, stored in c:\documents and settings\username.


For the future think about good/tested backups at least from system state
of the DC and all user data. Additional you should always have 2 DC's in
one domain, where are both Global catalog and DNS server.

Also look here about SID:
http://technet2.microsoft.com/windo...7404-41a6-9be7-171d40c398db1033.mspx?mfr=true

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm

> my 2000 server died and i built a new 2003 server with the old servers
> computer name and ip address, install dns, wins, and dhcp all fine i
> have all the AD user id's and passwords set up in the AD i have 35
> users that use to login to the old 2000 domain (mixed xp pro and
> windows 2000 machines)
>
> i can login sometimes as administrator and other times i get errors
> or can't login at all
>
> is there something on the workstations that identifiy them to the old
> server and NOT to the new server
>
> hope there is a simple fix for this
>
> ps. i unjoined my xp workstation from the domain and then rejoined the
> domain and then i could log on everytime without a problem
>
> but i don't want to do that with 35 machines as it would be time
> consuming and also setup a new profile for all machines i just want to
> have the users login as they did before as the new 2003 server is
> configured that same as the old 2000 server, file paths, printers, etc
>
> thanks in advance kinda lost
>
 
Back
Top