unable to build trust relationship between windows 2003 and 2000

[Guest]

I have 2 different domain which is 2000 and 2003. In 2003 can see 2000 domain
in network negihborhood but can't access it. I can ping the ip address and
can build trust relationship. But in 2000 everytime I set a trust
relationship it seems that 2000 cannot see 2003 says that "it cannot be
contacted". I can ping the ip address of the 2003 domain but cannot see in
the network neighborhood. What seems to be the problem?

 

[Steven L Umbach]

You may also want to post in an active_directory newsgroup.

For the trusts to work right your DNS must be configured correctly as the
domain controller in each domain needs to find the domain controller in the
other domain via its _srv records. Being able to ping each other by name is
not enough. It is also a good idea that the wins servers in each domain are
set to be replication partners with each other so that network browsing
works better.

For 2000 to 2003 you will probably need a domain controller to be a DNS
secondary zone holder for the Windows 2003 domain.

For 2003 to 2000 a domain controller running DNS can do conditional
forwarding to a DNS server in the Windows 2000 domain for the Windows 2000
domain name.

When all is done correctly you can use nslookup to verify correct DNS
operation by running it on a domain controller in one domain using the
domain name of the other domain as shown in the example below.


http://technet2.microsoft.com/windo...4e9b-4643-87e9-2d4ffeaecf001033.mspx?mfr=true
--- DNS secondary

http://articles.techrepublic.com.com/5100-1035_11-5112303.html?tag=sc ---
DNS conditional forwarding

Using Nslookup
1. From your DNS server, type nslookup at a command prompt.
2. Type set type=all, and then press ENTER.
3. Type _ldap._tcp.dc._msdcs.domainname and then press ENTER.
Nslookup returns one or more SRV service location records in the following
format
hostname.domainname internet address = ipaddress
where hostname is the host name of a domain controller, domainname is the
domain to which the domain controller belongs, and ipaddress is the domain
controller's Internet Protocol (IP) address.