Re: Problem establish trust between NT4 and W2K3 AD

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

to create a trust between some domain and a NT4 domain NetBIOS name
resolution is needed to find DCs in both domains. That can be established by
using a LMHOSTS file or using WINS.

You could install WINS on the W2K3 DC, point all servers for WINS to the
W2K3 DC and that way the servers will register the records in WINS. DCs in
each domain will register a 1Ch record in WINS that has the name of the
domain. That is the record in WINS that identifies DCs in domains

--
Cheers,
# Jorge de Almeida Pinto #
BLOG --> http://blogs.dirteam.com/blogs/jorge/default.aspx
-----------------------------------------------------------------------------
* This posting is provided "AS IS" with no warranties and confers no rights!
* Always test before implementing!
-----------------------------------------------------------------------------


-----------------------------------------------------------------------------
"Steven Wong" <sazabi75@xxxxxxxxxxx> wrote in message
news:uYiaTF$CGHA.3820@xxxxxxxxxxxxxxxxxxxxxxx
> thanks,
> so I have to enable the WINS server on NT or W2K3 ?
>
> "Paul Bergson" <pbergson@xxxxxxxxxxxxxxxxx> wrote in message
> news:e4Dvtg7CGHA.2436@xxxxxxxxxxxxxxxxxxxxxxx
>> You have to have wins -or- an lmhost table to define the AD DC. I have
>> tried both and have had more success using WINS but check out the link
>> below.
>>
>> http://support.microsoft.com/kb/245172/en-us
>>
>>
>>
>> --
>>
>>
>> Paul Bergson MCT, MCSE, MCSA, CNE, CNA, CCA
>>
>> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>>
>>
>> "Steven Wong" <sazabi75@xxxxxxxxxxx> wrote in message
>> news:%23UNiwx5CGHA.2704@xxxxxxxxxxxxxxxxxxxxxxx
>> > Hi,
>> >
>> > Please help .. I don't know what am I doing wrong ..
>> >
>> > NT4 Domain
>> >
>> > 1) server name : NTServerA
>> > OS : NT4SP6
>> > IP : 192.168.1.11
>> > Role : PDC
>> > 2) server name : NTServerB
>> > OS : NT4SP6
>> > IP : 192.168.1.12
>> > Role : BDC
>> >
>> > Windows 2003 Active Directory
>> >
>> > 1) server name : W2K3ADA
>> > OS : W2K3SP1 + Latest hot fixes
>> > IP : 192.168.1.1
>> > Role : Primary DC, DNS, GC
>> > 2) server name : W2K3ADB
>> > OS : W2K3SP1 + Latest hot fixes
>> > IP : 192.168.1.2
>> > Role : Backup DC
>> >
>> > All servers are on the same LAN and hardware switch, and NO firewall or
>> > packet filtering in between servers.
>> > Ping by NetBIOS names all OK on all servers
>> >
>> > Whenever I create a trust from NTServerA, I get an error saying Could
> not
>> > find domain controller for this domain.
>> > I am not using WINS.
>> >
>> > I have also followed the following Microsoft Technet but still no hope
>> > http://support.microsoft.com/kb/246261/
>> > http://support.microsoft.com/?kbid=180094
>> >
>> > Anyone got any ideas ??
>> > TIA
>> >
>> > Steven
>> >
>> >
>>
>>
>
>


.

Relevant Pages

  • Re: Help with setting up Sites.
    ... Site A - respresenting physical site B ... servers is increasing by the day. ... Do you have any DCs at SiteB? ... clients servers in the relevant sites to authenticate against them. ...
    (microsoft.public.windows.server.active_directory)
  • Re: adding machine to domain with NATed IPs
    ... sounds that the DCs are not reaching the>> clients ... can the servers pint the clients by IP and Name? ... we specified these IPs as DNS server within ...
    (microsoft.public.windows.server.active_directory)
  • RE: Need Advice (Repost)
    ... configuration there is no preference to the prod DCs over the DR DCs" Is ... if the DR servers are in a different AD site the users will be able to ... Active Directory Sites should be configured in this scenario. ... I've built two Active Directory Domain ...
    (microsoft.public.windows.server.active_directory)
  • Re: build now, join later
    ... admin rights in a child domain. ... instance configure DNS for failover, ... requires more than two dozen servers, ... them to create the child domain and their DCs with it, ...
    (microsoft.public.windows.server.active_directory)
  • Re: Possible DNS Issues
    ... for the winter and is trashing the database on the other DCs when it ... the previous post) DC's(which are Domain Controllers) that authenticate users ... Better to have seen them in the first problem report, ... The error message "no logon servers available" is consistent with a DNS setup ...
    (microsoft.public.windowsxp.network_web)