Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

AD for 2 network segment

Status
Not open for further replies.

kbengmy

MIS
Sep 11, 2002
9
MY
Server_A --> NIC_1 192.168.1.1
--> NIC_2 192.168.2.1
--> AD = MY_DOM
--> DNS = primary

Server_B --> NIC_1 192.168.1.2
--> NIC_2 192.168.2.2
--> AD = MY_DOM
--> DNS = secondary

Q1. AD tied to which NIC?
Q2. Can NIC_1 & NIC_2 client authenticate by the server?
 
Why should you want this type of configuration?

What you want to acheive?
 
It is a company (company_A) with few sub-company (company_B, company_C ...) located in a same building.

The entire network is flat, no router just pure switch connecting all PCs of company_A & company B. They segment it to 2 network segment to isolate each company PCs. So, company_A will carry 192.168.1.x and company_B will carry 192.168.2.x

They have 2 servers (Server_A & Server_B), both has to be accessible by company_A & company_B.

Initially it was running NT4 with ONLY 1 NIC card BUT configured 2 IP on 1 NIC. (Suprisingly it works for them for couple of years)

After that some time in Oct 06, they upgraded NT4 to 2003 server, and the same concept was 'copied' over but this time they put in 2 NIC and tied each NIC with seperate network segment.

Now, they having some AD problem and i was called in to settle this. It is un-usual to me with this kind of setup, and i done google (no luck) and read through some AD books (no luck as well).

Thank for your advice.
 
It is a company (company_A) with few sub-company (company_B, company_C ...) located in a same building.

The entire network is flat, no router just pure switch connecting all PCs of company_A & company B. They segment it to 2 network segment to isolate each company PCs. So, company_A will carry 192.168.1.x and company_B will carry 192.168.2.x

They have 2 servers (Server_A & Server_B), both has to be accessible by company_A & company_B.

Initially it was running NT4 with ONLY 1 NIC card BUT configured 2 IP on 1 NIC. (Suprisingly it works for them for couple of years)

After that some time in Oct 06, they upgraded NT4 to 2003 server, and the same concept was 'copied' over but this time they put in 2 NIC and tied each NIC with seperate network segment.

Now, they having some AD problem and i was called in to settle this. It is un-usual to me with this kind of setup, and i done google (no luck) and read through some AD books (no luck as well).

Thanks for your advice.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top