charles_lawrence
asked on
Lab Testing for my Microsoft Exchange and Active Directory studies
Hi,
Need your idea on how can i implement a Lab Testing for my study on Microsoft Exchange 2003.
What i really want is to implement a setup that is roughly the same scenario with 2 companies that are exchanging mails.
I want to use Virtual PC 2007 on this, is it possible? if yes, please advise how can i implement it.
Please help. Thank you.
-charles
Need your idea on how can i implement a Lab Testing for my study on Microsoft Exchange 2003.
What i really want is to implement a setup that is roughly the same scenario with 2 companies that are exchanging mails.
I want to use Virtual PC 2007 on this, is it possible? if yes, please advise how can i implement it.
Please help. Thank you.
-charles
ASKER
Hi Limjianan, Thanks for the responsed.
What i want in my simulation is, each companies should have different IP address convention (ie. companyA is 192.168.0.1, companyB is 172.16.1.1)..
my plan is to create atleast 5 virtual machines
1 RRAS (lan routing)- Router for both domains
2 AD/ Exchange- CompanyA.local/ CompanyB.local
2 XP OS/ outlook- xpA.companyA.local/ xpB.companyB.local
my objective is, johnsmith@companyA.local can send and receive mails from user in CompanyB.local and VICE VERSA.
guys, if any of you have an idea in mind on how to setup this please share with me. Thanks. ill appreciate it.
This will be a great help for me.
-charles
What i want in my simulation is, each companies should have different IP address convention (ie. companyA is 192.168.0.1, companyB is 172.16.1.1)..
my plan is to create atleast 5 virtual machines
1 RRAS (lan routing)- Router for both domains
2 AD/ Exchange- CompanyA.local/ CompanyB.local
2 XP OS/ outlook- xpA.companyA.local/ xpB.companyB.local
my objective is, johnsmith@companyA.local can send and receive mails from user in CompanyB.local and VICE VERSA.
guys, if any of you have an idea in mind on how to setup this please share with me. Thanks. ill appreciate it.
This will be a great help for me.
-charles
* Pretty simple one.
* Company One: ASIA.COM
*Machine 1:
OS - Windows 2k3 SP1
Name - AsiaDC.com
Roles: DC, DNS, Exchange
Exchange Org name: Asia
IP:192.168.1.1/24
* Company Two: EU.COM
* Machine 2:
OS - Windows 2k3 SP1
Name - EUDC.com
Roles: DC, DNS, Exchange
Exchange Org Name: EU
IP:10.10.10.1/24
* Router (acting as ISP)
* Machine 3:
OS - Windows 2k3 SP1
Name - Router (This machine would be in a WORKGROUP and would have 2 NICs)
Roles: DNS
IP: 192.168.1.254/24
IP:10.10.10.254/24
* Enable LAN routing in this using RRAS
* Now the first Machine 1 would have its DNS server pointing to itself and in the DNS configuration would have the IP of the Router as forwarder (192.168.1.254). Also it would have its gateway entry as 192.168.1.254.
* Then the second Machine 2 would have its DNS server pointing to itself and in the DNS configuration would have the IP of the Router as forwarder (10.10.10.254). Also it would have its gateway entry as 10.10.10.254.
* Finally the Router would have 2 forward lookup zones in it; one as Asia.com and other as EU.com. Both these zones would have their respective Exchange servers host (A) and Mail Exchanger (MX) records {in this case the host names and ips or the respective DCs since they host exchange too)
* And at last you have 2 XP machines as clients, each belonging to their respective domains and can have a static ip address respectively like 192.168.1.25/24 and 10.10.10.25/24 and would have their respective DNS server entries and Gateways
Hope this helps (^_^)
* Company One: ASIA.COM
*Machine 1:
OS - Windows 2k3 SP1
Name - AsiaDC.com
Roles: DC, DNS, Exchange
Exchange Org name: Asia
IP:192.168.1.1/24
* Company Two: EU.COM
* Machine 2:
OS - Windows 2k3 SP1
Name - EUDC.com
Roles: DC, DNS, Exchange
Exchange Org Name: EU
IP:10.10.10.1/24
* Router (acting as ISP)
* Machine 3:
OS - Windows 2k3 SP1
Name - Router (This machine would be in a WORKGROUP and would have 2 NICs)
Roles: DNS
IP: 192.168.1.254/24
IP:10.10.10.254/24
* Enable LAN routing in this using RRAS
* Now the first Machine 1 would have its DNS server pointing to itself and in the DNS configuration would have the IP of the Router as forwarder (192.168.1.254). Also it would have its gateway entry as 192.168.1.254.
* Then the second Machine 2 would have its DNS server pointing to itself and in the DNS configuration would have the IP of the Router as forwarder (10.10.10.254). Also it would have its gateway entry as 10.10.10.254.
* Finally the Router would have 2 forward lookup zones in it; one as Asia.com and other as EU.com. Both these zones would have their respective Exchange servers host (A) and Mail Exchanger (MX) records {in this case the host names and ips or the respective DCs since they host exchange too)
* And at last you have 2 XP machines as clients, each belonging to their respective domains and can have a static ip address respectively like 192.168.1.25/24 and 10.10.10.25/24 and would have their respective DNS server entries and Gateways
Hope this helps (^_^)
ASKER
Hi Rudram, great! thanks for this info.
in your first procedure=> * Enable LAN routing in this using RRAS
is there any configuration in RRAS LAN routing that i need to do for me to establish connection between companies- ASIA.COM, EU.COM??
Awaiting for your response.
-charles
in your first procedure=> * Enable LAN routing in this using RRAS
is there any configuration in RRAS LAN routing that i need to do for me to establish connection between companies- ASIA.COM, EU.COM??
Awaiting for your response.
-charles
* No extra configuration needed. What we are doing here is, we are actuall establishing a connectivity between the 2 NICs of the machine "ROUTER".
* This is because both those NICs, even though they are of the same machine, have been given IP addresses of 2 entirely different networks.
* So what we achieve here is when the DC from Asia.com will try to access or query the DNS server for EU.com, the query would propogate from Asia.com DC to the Router (which is our acting ISP now) and from there using the 2nd NIC of ROUTER it will propogate to the DC of EU.com. Thereby establishing the route for the message to flow.
(^_^)
* This is because both those NICs, even though they are of the same machine, have been given IP addresses of 2 entirely different networks.
* So what we achieve here is when the DC from Asia.com will try to access or query the DNS server for EU.com, the query would propogate from Asia.com DC to the Router (which is our acting ISP now) and from there using the 2nd NIC of ROUTER it will propogate to the DC of EU.com. Thereby establishing the route for the message to flow.
(^_^)
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
OKAY! let me try this asap! ill let you know!
cheers! Thank you.
-charles
cheers! Thank you.
-charles
ASKER
It works fine! Thank you!
first server. (second server)
install windows 2003. IP address 192.168.0.1 192.168.0.2
and promoted to DC. call A.local (another one call b.local)
then install exchange 2003 used a.com (another call b.com)
create a.com and point to 192.168.0.1 (both server)
create b.com and point to 192.168.0.2 (both server)
thiis is a very rough idae how you gonna setup...
it is not a microsoft exchange best pratice (you should not put DC and exchange in 1 server for example)