Multiple Windows Server 2008 R2

if we delete this then what would be the right way to point the internal (10.10.10.10 )network the exit path.!!!

• route add -p 172.20.0.1 mask 255.255.0.0 172.20.0.254 this was the route you had specified ... i don't know on which interface it should be configured using UI console ... !!!

1. Another thing in this route is that you are more specific in directing the destination network which gives error when configuring the route through UI...it asks for or works normally when i enter the network 172.20.0.0 instead of 172.20.0.1

The route 172.20.0.0 / 255.255.0.0 / On-link / 172.20.13.16 -- should route packets from 10.0.0.0 network to 172.20.0.0

"route add -p 172.20.0.1 mask 255.255.0.0 172.20.0.254" was just an example, your IP addresses are different

Again, that IP 172.20.0.1 was an IP I gave as an example to ServerA internal interface. You can instead use the network ID as the destination (not the Server IP), which is 172.20.0.0

I think the problem lies with IP class i am using ... i should change it to 192.168.0.X class more convenient one and less cumbersome in configuration ...

This is not a valid thought. Nothing wrong with using 10.0.0.0 network. You have to understand that IPs/network IDs I use are not necessarily true for your case. Instead try to understand the mentality behind them.

Can you access Internet from ServerB or clients on network B now?

i understand that what you are referring to ...

i must also mention here that before turning to static routing option ... i worked on NAT to access the internet from Server B clients you know its a simple set of configurations but again i am unable to do that either. Don't know whats the problem with "routing n remote access services"
.
.
. For Your Q? Still i cant access the 172.20.0.0 network.. i even cant reach the 2nd interface of Server B which has been assigned an automatic IP of 172.20.13.16 by the Server A

I must tell you here that i didn't have configure a gateway option on Server B during the configuration of DHCP services and left it blank.... is it appropriate....?

Ok, couple of things:
Change to static IP on ServerB, servers should always have static.
Configure ServerB DHCP to have 10.10.10.10 as gateway. A gateway is where to send the packets when the interface doesn't know the destination network.

Is this a new office or part of it new?

No its the same network i was trying to update you about my other attempts n configuration

Thanks...
.
.
I did the following things yesterday...

For NAT

I succeeded to some extent. now i am able to ping 172.20.0.0 network client from 10.10.10.11 clientof Server B ... but cant ping from 172.20.0.20 ( A client inside 172.20.0.0 Network)......

But i cant access the Internet !!!



1. Introduced the gateway of 10.10.10.10 through DHCP for internal Network clients "Lan1"

2. Gave the static IP of 172.20.13.16 to External OR LAN 2 interface without giving the gateway.

3. I linked LAN2 to the public interface (172.20.0.0 network) to connect to the internet

Aha....

After NAT configuration .......
I succeeded i can ping both the 172.20.0.0 network clients, Server A itself and also can access internet beyond the Server A Network from Server B clients and Network 10.0.0.0

Sever B Client ipconfig statistics:

Ip = 10.10.10.11 (Assigned by DHCP)
Dns= 10.10.10.10
DHCP= 10.10.10.10
Gateway= 10.10.10.10
Everything is working alright with these settings.

At the moment I have set aside the Static routing option .....

My Q is ......

How would i be able now to access the 10.0.0.0 Network from 172.20.0.0 ?
Do i have to go for static routing option or just modify the existing configuration i have stated above?

You can't ping individual computers behind a NAT unless you forward ports to them. Maybe 1 or 2 servers but for an entire segment this is infeasible. Also not a very good practice to NAT internally. The method below will achieve what you want with routing LAN networks.

Simple Diagram:


I started with changing Network Interface names to more meaningful ones:
On ServerA: Internet and Network172
On ServerB: Network172 and Network10

All interfaces are configured with static IPs, it goes as:
ServerA - Internet:
192.168.0.110 / 255.255.255.0 - Gateway: 192.168.0.1 - DNS Servers: nothing set
ServerA - Network172:
172.20.0.1 / 255.255.0.0 - Gateway: nothing set - DNS servers: 172.20.0.254 (since you have AD on ServerB, I guess your DNS is there too)
ServerB - Network172:
172.20.0.254 / 255.255.0.0 - Gateway: 172.20.0.1 - DNS Servers: 172.20.0.254
ServerB - Network10:
10.10.10.10 / 255.0.0.0 - Gateway: nothing set - DNS Servers: 10.10.10.10

Due to the nature of TCP/IP setup on internal interfaces, they were set as "Unidentified Networks", and had to resort to Group Policy to designate them as Private. (Skip if yours are already private). Open Group Policy (run "mmc" and add snap-in for Group Policy Object)


Install Routing and Remote Access on both servers (if not already), both servers will be configured as "Routers" for LAN routing only.


Configure ServerA Internet interface as NAT: Right click General for ServerA and "New Routing Protocol" and select NAT from the list. A NAT entry will show under IPv4, right click and "New Interface", select Internet (this is the name I gave earlier for ServerA outer interface, 192.168.0.110) from the list.

Add Static Route for segment 10.0.0.0: Under ServerA IPv4 list, right click "Static Routes" - "New Static Route" as below:


Next post - ServerB

ServerB:

RRAS: Nothing special needed, everything is default.
DNS: Your DNS should already have forwarders enabled for any non-authoritative name resolution. To test things; I had to create a forward lookup zone (called it "internal") that forwards to root servers. It is listening on both 172.20.0.254 and 10.10.10.10.


Client PC on Network 10.0.0.0/255.0.0.0 (Yours should be automatic and configured with DHCP):


Hopefully, I have not left out anything. Windows Firewall is off for both Servers and the client PC! You will have to open proper ports/allow programs etc.

To add: I have shared a folder on both Servers and client PC can access both by entering DNS name, browsing can only see ServerB as ServerA is on a different segment (it does show with DNS name after accessing from address bar). (You can also use Distributed File System -DFS- for shares if so needed).