Multi domain setup in one server

[Frankie]

The company I work uses one server for two companies
within a site via LAN. Since they are basically two
companies, I'd like to create two domains within a single
server with Windows 2000 server installed.
Is it possible to do so, and how? And if they have some
resources needed to be shared across the two domains, is
that possible at all?

Or should I setup one domain with 2 OU to maintain the
server in this given situation?

 

[ptwilliams]

There's only one way to have two different domains on one box - and that's
running two or more virtual domain controllers using something like VMWare
or VirtualServer. Otherwise, a domain is strictly one-box-thing <g>.

If you just want to grant access to shared resources, perhaps you're better
off keeping this a stand alone box and being quite relaxed on the whole
security (permissions) of the data, etc.

Could you explain your scenario a little more? That may help us help you.

--

Paul Williams
http://www.msresource.net


Why not join us in our free, public forum?
http://forums.msresource.net
______________________________________
The company I work uses one server for two companies
within a site via LAN. Since they are basically two
companies, I'd like to create two domains within a single
server with Windows 2000 server installed.
Is it possible to do so, and how? And if they have some
resources needed to be shared across the two domains, is
that possible at all?

Or should I setup one domain with 2 OU to maintain the
server in this given situation?

 

[Guest]

We have two companies there sharing virtually one big
office. Since they are right next to each other and the
server simply acts as a file sharing + DB server for 15
clients, we think we should deploy only one server.
However, we must present to the industry as two seperate
companies for commerical reasons.
the reason that pops me thinking of two domains is
different employees in different companies should login
as:
somebody@company_a.com and somebody@company_b.com

If you guys' experiences conclude that one domain is
easier to manage and deploy and stuff like that, I will
stick to it... (doesn't matter terribly much for login
names since no outsider is able to access into the
office, it's just that we use email to communicate to our
customers and we don't want them to know company_b is
related to company_a)

Thanks a lot and I am happy to provide more info.

 

[Tomasz Onyszko]

We have two companies there sharing virtually one big
(...)

Thanks a lot and I am happy to provide more info.

If this two companies are using the same file and DB resources and only
thing You want is to make them visible outside of Your network as two
separated companies then deploy single domain, split the users from this
two companies to separated OU (just for Your management simplicity) and
then configure them separated outside e-mail adressess (becouse this is
I think what You are concerned about - that e-mail addresses visible for
the customers should be separated).

I don't know what e-mail system You are using but this can be done even
at the client side and on the server side as well (If You are using
Exchange server You can deploy two recipient policies with different
scope to assign adresses to users in different copmanies)