Re: NT4/2K3 DNS Domain Name - Fallback Issues

From: KingBuzzo (KingBuzzo_at_discussions.microsoft.com)
Date: 01/13/05 

Date: Thu, 13 Jan 2005 08:45:07 -0800

I mean the trust between the NT4 Domain and the workstation was broken
because the W2K3 AD DC renamed the workstation upon login.

"Chriss3 [MVP]" wrote:

> 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!
> >> >>
> >> >>
> >> >>
> >>
> >>
> >>
>
>
>

Relevant Pages

  • Re: Floating Computer between domains
    ... "JoshG" wrote in message ... If your domains are in the same forest, they automatically trust each other, ... can manage your network password access through the local user account under ... > I need the workstation machine to be able to float between the two ...
    (microsoft.public.windows.server.active_directory)
  • Re: logon on to server again
    ... He did just say "remove and re-add" which I guess could be interpreted as removing the trust and not the workstation. ... You will switch from domain to workgroup and this will remove the computer from the domain and clear the trust relationship the OS thinks it has with the server. ...
    (microsoft.public.windows.server.sbs)
  • Re: reestablish trust relationship
    ... I now have a workstation that has issues when accessing this ... Apparently the trust relationship is lost due to ... > SID issues. ... Intra-forest trusts between DCs and/or member machines (joined ...
    (microsoft.public.windows.server.dns)
  • Re: logon on to server again
    ... as removing the trust and not the workstation. ... re-add the workstation from the domain. ... computer's account was deleted from the server in AD users and ...
    (microsoft.public.windows.server.sbs)
  • Re: sharing folders across domains
    ... If the domains are in the same Active Directory forest you should be able to ... If they are not you can create and external trust between the ... If you want them to access just one workstation you ... might be better of simply adding the user accounts for these users to the ...
    (microsoft.public.windows.server.networking)