two nics - two networks

[Auddog]

I have a windows 2003 server with one nic (192.168.100.x). We just
purchased a second company that's in our building. Can I add a second nic
and configure it to there network ip scheme (192.168.25.x) so that I can
share one server? I want to share the server, just not the information on
the server. Will either of the networks be able to one another if I don't
bridge the networks cards? Thanks for any help you can provide.

A

 

[Danny Sanders]

There are problems associated with having 2 NICs on a DC.

Why not just add them to your network?


hth
DDS

 

[Auddog]

I would like to have one employee of the new company be able to access some
of the information. But I don't want to store all their information on my
server. I have read that I will need to have two different subnets to make
this work. If that is the case how will windows 2003 know which network to
talk to for AD? Will there be other problems?

 

[Danny Sanders]

I would like to have one employee of the new company be able to access some

of the information.

Use ADMT to migrate the users from the domain in the new company and add
them to your existing domain.
Not sure where "some" of the information is located on your domain but you
allow them access to it by using NTFS security.

But I don't want to store all their information on my server.

Not sure what kind of server the information is stored on in the current
domain. DC? run dcpromo to remove AD and make it a member server. Then add
it to your domain and use this server to store their data on.
Member server? Just remove the server from the existing domain and add it to
your domain and use this server to "store their information on".

I have read that I will need to have two different subnets to make
this work.

Typical branch office set up is to place a DC in the branch office, define a
subnet for the branch office, Move the DC into the site OU and the clients
in that site authenticate to the DC in that site.

What you want is to have the newly acquired office as a site on your domain.
You don't want to multihomed your DC.

hth
DDS

 

[Auddog]

Thanks for giving me the straight answer. It appears that I have a little
work ahead of me. Thanks once again.

A

 

[Phillip Windell]

Creating a new IP network segment is not, and should never be the first thing
you do to protect resources. Resources can be perfectly protected on a single
subnet LAN (remember LANs used run on Netbuei and IPX/SPX). You protect
resources first by using what provides the resource to start with. Files you
protect with NTFS, Web and FTP are protected by the Web/FTP Server and NTFS
combined, Databases are protected by the Database Server's own native security
and by the security built into the Application that access the database.

Protecting resources by blocking traffic at Layer4 is the last thing you do and
is only a "rough" and "crude" protection that is not very granular at all,...and
often "breaks" things as often as if does anything else.

--
Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com

The views expressed (as annoying as they are, and as stupid as they sound), are
my own and not those of my employer, or Microsoft, or anyone else associated
with me, including my cats.