Creating a trust between win 2k and win2k3

[skfm]

Hi, I am really at lost here and I need some advice. Here is the prob. I have a w2k situated at the HQ which is the DC with root domain of hq.com.my. And I will be setting up a w2k3 at my factory in another site as factory.com.my. The thing is, i would like to connect both side through vpn so that when my bosses are at the factory side, they could still be able to share files from the hq.

My setup,

At the Hq,
Server w2k sp 4
ip: 192.168.10.2
domain : hq.com.my

at the factory,
server w2k3
ip : 192.168.11.1
domain:factory.com.my

So how do i go about setting this up, what about the dns. I was thinking about the parent- child trust, but the subnet is not the same. I need to set this up urgently as my bosses is already at my neck O top of this, I will have to do the same for another branch.

Please help, your advice is appreciated.

Thanks.

 

[WhoKilledKenny]

Thoughts...
You don't necessarily have to set up a trust. You can place domain controllers for your current domain at the factory. You could then organize the location in AD using and OU called e.g Factory. This would be a good way for you, as an administrator to manage your domain. Different subnets would not be a reason for creating trusts. You can use Active Directory-sites and services to set up multiple sites (in the same domain) and control replication over the WAN link.

VPN between sites? - What type of WAN technology are you using to connect the different location?

If you are required to set up a trust, you should research and deploy a child domain. You can do this with other locations that you bring online in the future.

But... If it were me, I would just expand my current domian to multiple sites, especially if all remote sites are geographically within a local area.

 

[pgaliardo]

I agree with WhoKilledKenny. Your setup doesn't seem to warrant seperate domains and trusts. One of the advantages of Active Directory was to reduce the whole Master Domains and trusts necessary from NT 4.0.

I think seperate OU's would work well in this setup.

I'm not sure if you need to setup another zone in DNS if you go the child domain route, but if you take WhoKilledKenny's advice, you eliminate that problem also, because you will only need 1 Active directory integrated zone.