Trusting domains between Windows 2003 and Windows 2000 advanced server

[Gaspar]

I have a windows 2003 server controlling the main domain of my LAN called
"principal.com"
Additionally I have a windows 2000 advanced server that some computer
clients access, controlling "secondary.com"

Both servers are in the same network (192.168.0.x); Windows 2003 server is
SERVERMAIN with IP 192.168.0.1, and the other is SERVERSECONDARY with
192.168.0.8

- How do I configure both domains to trust each other? I've never done this.
- What about DNS configuration in servers and clients? Obviously each server
has its own DNS server.

I played around with "Active Directory Domains and Trusts" but the domains
can't see each other.

Thanks.
Gaspar

 

[Robert L [MS-MVP]]

Name resolution is the key for creating a trust between two domains. You may use WINS or lmhosts for the NetBIOS. What I recommend is setup a primary DNS for one domain and secondary for another domain so that you can ping both DCs with their FQND.

Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com
I have a windows 2003 server controlling the main domain of my LAN called
"principal.com"
Additionally I have a windows 2000 advanced server that some computer
clients access, controlling "secondary.com"

Both servers are in the same network (192.168.0.x); Windows 2003 server is
SERVERMAIN with IP 192.168.0.1, and the other is SERVERSECONDARY with
192.168.0.8

- How do I configure both domains to trust each other? I've never done this.
- What about DNS configuration in servers and clients? Obviously each server
has its own DNS server.

I played around with "Active Directory Domains and Trusts" but the domains
can't see each other.

Thanks.
Gaspar

 

[Guest]

I would suspect your domains are not in the same forest which is why they
don't see each other. Good thing you have 2003 as trusts between forests was
not possible in 2000

IMHO this is a bad setup. You have no failover, no second DC, no second GC
holder, no redundent DNS.

You might want to start here
http://technet2.microsoft.com/WindowsServer/en/Library/7b075a25-9f29-4856-883c-f230a8ccd6811033.mspx

 

[Gaspar]

IMHO this is a bad setup.
I know, but I can't change nor nother the secondary domain (enterprise
policies).

 

[Gaspar]

1) I don't use WINS.
2) What do I have to add in lmhosts? the domain name pointing to 192.168.0.1?

Thanks
Name resolution is the key for creating a trust between two domains. You may use WINS or lmhosts for the NetBIOS. What I recommend is setup a primary DNS for one domain and secondary for another domain so that you can ping both DCs with their FQND.

Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com
I have a windows 2003 server controlling the main domain of my LAN called
"principal.com"
Additionally I have a windows 2000 advanced server that some computer
clients access, controlling "secondary.com"

Both servers are in the same network (192.168.0.x); Windows 2003 server is
SERVERMAIN with IP 192.168.0.1, and the other is SERVERSECONDARY with
192.168.0.8

- How do I configure both domains to trust each other? I've never done this.
- What about DNS configuration in servers and clients? Obviously each server
has its own DNS server.

I played around with "Active Directory Domains and Trusts" but the domains
can't see each other.

Thanks.
Gaspar

 

[Michael Giorgio - MS MVP]

This really has nothing to do with the domain seeing each other.

 

[Michael Giorgio - MS MVP]

But you do have DNS..

1) I don't use WINS.
2) What do I have to add in lmhosts? the domain name pointing to
192.168.0.1?