Re: NT4/2K3 DNS Domain Name - Fallback Issues
From: Chriss3 [MVP] (noSpamHere_at_chrisse.se)
Date: 01/13/05
- Next message: Chriss3 [MVP]: "Re: Delegation in AD"
- Previous message: Paul: "Re: Adding Solaris 10 machine to Active Directory Authentication"
- In reply to: KingBuzzo: "Re: NT4/2K3 DNS Domain Name - Fallback Issues"
- Next in thread: KingBuzzo: "Re: NT4/2K3 DNS Domain Name - Fallback Issues"
- Reply: KingBuzzo: "Re: NT4/2K3 DNS Domain Name - Fallback Issues"
- Messages sorted by: [ date ] [ thread ]
Date: Thu, 13 Jan 2005 17:19:47 +0100
The trust should not be broken, Verify your trust sate in Active Directory
Domains & Trusts tool.
How to verify a trust:
http://www.microsoft.com/resources/documentation/WindowsServ/2003/standard/proddocs/en-us/sag_ADtrustVerify.asp
-- Regards Christoffer Andersson Microsoft MVP - Directory Services No email replies please - reply in the newsgroup ------------------------------------------------ http://www.chrisse.se - Active Directory Tips "KingBuzzo" <KingBuzzo@discussions.microsoft.com> skrev i meddelandet news:023BF4AA-1803-4100-BC91-51B8240643C8@microsoft.com... > Yes, and then when I tried to log back into the old domain the trust was > broken because the computername was different. > > Maybe I did something wrong? > > "Chriss3 [MVP]" wrote: > >> I think the name is not changed, just the FQDN are added. but the name of >> the particular computer are still the same. Are you meaning the NetBIOS >> Name >> is changed? >> >> -- >> Regards >> Christoffer Andersson >> Microsoft MVP - Directory Services >> >> No email replies please - reply in the newsgroup >> ------------------------------------------------ >> http://www.chrisse.se - Active Directory Tips >> >> "KingBuzzo" <KingBuzzo@discussions.microsoft.com> skrev i meddelandet >> news:EA1D2E44-2915-40DF-BF45-94446A003601@microsoft.com... >> > Yes, I understand how it has the two names for backward compatibility >> > but >> > after logging a workstation into the upgraded domain, it actually >> > renamed >> > it >> > which caused a problem when I tried to log into the old domain as I was >> > testing my fallback plan. >> > >> > "Chriss3 [MVP]" wrote: >> > >> >> There is both a Pre-Windows2000 Name (NetBIOS Name) and a FQDN Name. >> >> Down level clients or servers, Pre-Windows2000 still use the NetBIOS >> >> Name. >> >> >> >> -- >> >> Regards >> >> Christoffer Andersson >> >> Microsoft MVP - Directory Services >> >> >> >> No email replies please - reply in the newsgroup >> >> ------------------------------------------------ >> >> http://www.chrisse.se - Active Directory Tips >> >> >> >> "KingBuzzo" <KingBuzzo@discussions.microsoft.com> skrev i meddelandet >> >> news:AA9220C7-463C-4668-8461-2A7234AE7201@microsoft.com... >> >> >I am currently upgrading an NT 4.0 PDC in a lab to 2003. >> >> > >> >> > The current Netbios Domain name is DOMAIN and when I get to step 1 >> >> > of >> >> > the >> >> > AD >> >> > setup it wants to change it to a FQDN name. >> >> > >> >> > After I change the domain name to DOMAIN.Company.State.com and a >> >> > user >> >> > logs >> >> > in, it changes the workstation name from wrkstn to >> >> > wrkstn.Company.State.com. >> >> > >> >> > If the upgrade is successful in production this would be fine, but >> >> > if I >> >> > try >> >> > to remove the new 2K3 Domain Controller and put my backup NT 4.0 >> >> > Domain >> >> > Controller back in production, it won't recognize the client because >> >> > the >> >> > computer name has changed. >> >> > >> >> > Is there any way around this or am I missing something here? >> >> > >> >> > Thanks! >> >> >> >> >> >> >> >> >>
- Next message: Chriss3 [MVP]: "Re: Delegation in AD"
- Previous message: Paul: "Re: Adding Solaris 10 machine to Active Directory Authentication"
- In reply to: KingBuzzo: "Re: NT4/2K3 DNS Domain Name - Fallback Issues"
- Next in thread: KingBuzzo: "Re: NT4/2K3 DNS Domain Name - Fallback Issues"
- Reply: KingBuzzo: "Re: NT4/2K3 DNS Domain Name - Fallback Issues"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
