Hi guys, Sorry i'm such a noob in this. I'm doing Config Manager server but my lead is asking me like to setup the whole environment. We have an AD, and now she want me to do my own networking to do this project. Here's some picture, we have a server that host DNS, DHCP using ip range 172.x.x.x (let's call it Server A) And now i'm going to need to setup an AD server, and DNS server with ip range 192.x.x.x (let's call it server B) Problem is, when server B cannot talk to server A now if I put the ip address 192.x.x.x for it. Unless i'm using the same ip range which is 172.x.x.x it won't communicate at all. Can you give some idea on what need to be done on server B, in order for it to use its own IP address range (192.x.x.x) and still can communicate with server A (which is using ip add 172.x.x.x) ? (Both servers are on Win2k8 and we will have a pool of computers that will be using ip address 192.x.x.x address range) Any advice is appreciated. Thank you. ---Packie

As explained above both the servers are in different subnets in this case you should use a router or a layer 3 Switch for the communication. http://www.windowsnetworking.com/articles_tutorials/How-configure-Windows-2008-Server-IP-Routing.html http://www.virmansec.com/blogs/skhairuddin

Hello, Here's some picture, we have a server that host DNS, DHCP using ip range 172.x.x.x (let's call it Server A) And now i'm going to need to setup an AD server, and DNS server with ip range 192.x.x.x (let's call it server B) also make it a GC. It is recommended to have at least two DC / DNS / GC servers per domain. Problem is, when server B cannot talk to server A now if I put the ip address 192.x.x.x for it. Unless i'm using the same ip range which is 172.x.x.x it won't communicate at all. You have to check your routes. Are they connected via a layer 3 Switch or a router? If not, use one of them. Can you give some idea on what need to be done on server B, in order for it to use its own IP address range (192.x.x.x) and still can communicate with server A (which is using ip add 172.x.x.x) ? Add a router or a Layer 3 Switch. Also make sure that needed ports for AD replication are not blocked: http://technet.microsoft.com/en-us/library/bb727063.aspx This posting is provided "AS IS" with no warranties or guarantees , and confers no rights. Microsoft Student Partner 2010 / 2011 Microsoft Certified Professional Microsoft Certified Systems Administrator: Security Microsoft Certified Systems Engineer: Security Microsoft Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration Microsoft Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration Microsoft Certified Technology Specialist: Windows Server 2008 Applications Infrastructure, Configuration Microsoft Certified Technology Specialist: Windows 7, Configuring Microsoft Certified IT Professional: Enterprise Administrator Microsoft Certified IT Professional: Server Administrator

hi all, thanks for all the feedbacks..really appreciate it! I've installed Routing and Remote access roles, and RIP, but im not sure how it is configured My network setup is simple 1. Existing ip range 172.16.0.0 mask 255.255.255.0 (currently used in the office, up and working) 2. New ip address 192.168.1.0 mask 255.255.255.0 (lab environment, need to be able to communicate with 172.16.0.0 ip range) where should i put the information of 172.x ip range in my Server B in the routing and remote access service? I've followed the information in the URL given by Syed Khairuddin but it didn't tell how this is configured. Sorry i might be wrong and still new to this roles. Server A is using the following config: IP address: 172.16.0.5 Mask: 255.255.255.0 Gateway: 172.16.0.1 DNS: 172.16.0.10 / 172.16.0.11 Should I use the same gateway/DNS for Server B? ---Packie

hi all, thanks for all the feedbacks..really appreciate it! I've installed Routing and Remote access roles, and RIP, but im not sure how it is configured Have you installed it on a DC? If yes then this is not recommended. More here: http://msmvps.com/blogs/acefekay/archive/2009/08/17/multihomed-dcs-with-dns-rras-and-or-pppoe-adapters.aspx My network setup is simple 1. Existing ip range 172.16.0.0 mask 255.255.255.0 (currently used in the office, up and working) 2. New ip address 192.168.1.0 mask 255.255.255.0 (lab environment, need to be able to communicate with 172.16.0.0 ip range) If you have a server with two NICs, you can enable RRAS on it and connect DCs to it. where should i put the information of 172.x ip range in my Server B in the routing and remote access service? If you have just two subnets, you can connect each subnet to one interface your your RRAS server. This posting is provided "AS IS" with no warranties or guarantees , and confers no rights. Microsoft Student Partner 2010 / 2011 Microsoft Certified Professional Microsoft Certified Systems Administrator: Security Microsoft Certified Systems Engineer: Security Microsoft Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration Microsoft Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration Microsoft Certified Technology Specialist: Windows Server 2008 Applications Infrastructure, Configuration Microsoft Certified Technology Specialist: Windows 7, Configuring Microsoft Certified IT Professional: Enterprise Administrator Microsoft Certified IT Professional: Server Administrator

Hi Mr X, no i just have 1 NIC on this server, is it still possible to do this? i mean the server B is able to ping server A if only it's using 172.x ip address now that i wanted to change it using 192.x ip address, it can't reach the server A anymore. i'll read the link you've provided above and try again. Many thanks! ---Packie

no i just have 1 NIC on this server, is it still possible to do this? No. You should have two NICs and each one will be connected to a network. That should be a connectivity problem or a problem with routes. Like I already said, you should have a router with at least two interfaces or a Layer 3 Switch. now that i wanted to change it using 192.x ip address, it can't reach the server A anymore. Perfectly normal as you have not added the needed components. This posting is provided "AS IS" with no warranties or guarantees , and confers no rights. Microsoft Student Partner 2010 / 2011 Microsoft Certified Professional Microsoft Certified Systems Administrator: Security Microsoft Certified Systems Engineer: Security Microsoft Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration Microsoft Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration Microsoft Certified Technology Specialist: Windows Server 2008 Applications Infrastructure, Configuration Microsoft Certified Technology Specialist: Windows 7, Configuring Microsoft Certified IT Professional: Enterprise Administrator Microsoft Certified IT Professional: Server Administrator

Hi Packie, Thank you for your post. (Both servers are on Win2k8 and we will have a pool of computers that will be using ip address 192.x.x.x address range) It seems that you will install DHCP on server B. You need to use router/vlan to separate these two servers rather than connect them in one switch/same vlan, or clients will be assigned to ip address 172.x.x.x/192.x.x.x randomly. If there are more inquiries on this issue, please feel free to let us know. Regards, Rick Tan

Hi all, Thanks for all of your inputs. I have my 2nd NIC up and assigned using 192.x ip address successfully. It is a virtual adapter (as we are using Citrix to run Windows 2008 servers). as Rick Tan mentioned above, I might have problem with IP address assigning as both Server A and Server B have/will have a DHCP role later. can routing (to assign which ip address segment) be done solely on Windows 2008 server only without using hardware router like Cisco etc? many thanks in advanced for any advice.---Packie