Domain login

[Guest]

I replaced a dead NT 4 Server - PDC, with a Windows Server 2003 - Domain
Controller. There had been a Windows 2000 App. Server that logged-in to the
"no-suffix" NT Domain. The App. Server got rebooted before the Domain could
be changed on it to be the new WS2003 "suffixed" Domain name... now I can't
login to the Windows 2000 App. Server becasue it can't find the old Domain
name.
What can I do to either change the Domain it's logging into to the new
"suffixed" name, or to get the new WS2003 DC to authenticate it?

 

[Dave Patrick]

Logon locally as administrator, change it to workgroup mode, then join the
new domain after restart.

--

Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect

:
|I replaced a dead NT 4 Server - PDC, with a Windows Server 2003 - Domain
| Controller. There had been a Windows 2000 App. Server that logged-in to
the
| "no-suffix" NT Domain. The App. Server got rebooted before the Domain
could
| be changed on it to be the new WS2003 "suffixed" Domain name... now I
can't
| login to the Windows 2000 App. Server becasue it can't find the old Domain
| name.
| What can I do to either change the Domain it's logging into to the new
| "suffixed" name, or to get the new WS2003 DC to authenticate it?
| --
| techon

 

[Lanwench [MVP - Exchange]]

In

I replaced a dead NT 4 Server - PDC, with a Windows Server 2003 -
Domain Controller. There had been a Windows 2000 App. Server that
logged-in to the "no-suffix" NT Domain. The App. Server got rebooted
before the Domain could be changed on it to be the new WS2003
"suffixed" Domain name... now I can't login to the Windows 2000 App.
Server becasue it can't find the old Domain name.
What can I do to either change the Domain it's logging into to the new
"suffixed" name, or to get the new WS2003 DC to authenticate it?

Hi - I replied to this post in microsoft.public.security.homeusers.

Please don't multipost - if you need to post to multiple groups, it's best
to crosspost instead, by posting a single message to a handful of relevant
groups (separate the NG names with commas) so that everyone can follow the
thread. Thanks

See http://www.blakjak.demon.co.uk/mul_crss.htm

 

[Softenough]

Logon locally as administrator, change it to workgroup mode, then join the
new domain after restart.

Hi Dave,

I did get logged-in locally (finally hit on the original admin pw.) I
changed to WG mode, then rebooted, then tried to join the "suffixed" Domain.
Nothing doing. I plan to play with it as long as necessary this weekend,
and hopefully get this thing out of the quicksand.

Thanks for your reply - it was helpful. If I can just get this thing
connected to the Domain and figure out why now the Backup Exec is "gone,"
I'll have had a good install/upgrade... with the standard and commensurate
learning curve.

 

[Greg Moseley]

Hi,

When you say you are trying to join the 2000 domain to the 'suffixed'
domain do you mean you are entering domain.com in the DOMAIN join box?
If so, you need to ensure that the 2000 server is using the DNS server
that hosts the 2003 domain (most likely the new 2003 Server) within the
TCP/IP properties on the network adapter.

Entering a 'suffixed' domain (really called a Fully Qualified Domain
Name (FQDN)) means that the server will look in DNS rather than
broadcast the network for the domain.

Hope this helps.
Greg

-----Original Message-----
From: Softenough [mailto:[email protected]]
Posted At: 26 November 2005 06:17
Posted To: microsoft.public.win2000.general
Conversation: Domain login
Subject: Re: Domain login

Logon locally as administrator, change it to workgroup mode, then join the
new domain after restart.

Hi Dave,

I did get logged-in locally (finally hit on the original admin pw.) I
changed to WG mode, then rebooted, then tried to join the "suffixed"
Domain.
Nothing doing. I plan to play with it as long as necessary this
weekend,
and hopefully get this thing out of the quicksand.

Thanks for your reply - it was helpful. If I can just get this thing
connected to the Domain and figure out why now the Backup Exec is
"gone,"
I'll have had a good install/upgrade... with the standard and
commensurate
learning curve.