Multiple Windows Server 2008 R2

I have attached the image plz help me out ....

want to make communicate all the clients of "Server B" with "Server A".....

Make sure Routing is enabled on Server B - https://technet.microsoft.com/en-us/...(v=ws.10).aspx

Then if still not working (I believe it should), try adding the static route on Server B (https://technet.microsoft.com/en-us/...(v=ws.10).aspx):

Command is:

Code:

route add destination mask subnetmask gateway metric costmetric if interface

route add -p ServerA-IP-towards-Internal-A-Network mask Internal-A-subnetmask ServerB-IP-towards-Internal-A-Network

Just an example would be, assuming IPs are set like this for your network
route add -p 172.20.0.1 mask 255.255.0.0 172.20.0.254

Tnx for response... Let me try it but before i move forward dont you think i should touch routing on the server "A" to...!!!?

The command is for making network B computers to reach Server A, which you asked. If you have more requirements list them here. For example, you didn't say anything about Internet connectivity requirements.

yes exactly i would like that too,,, if plz...

Lets go step by step:
Is your network at the moment functional? Is DHCP working on both servers?

First enable Routing on both Servers A and B, and see what you can achieve like that. Please run in cmd after enabling routing:

Code:

route print |clip

It will not output anything visible but copy the results to the clipboard directly. CTRL+V here (or to a notepad) once you run it. Attach both servers.

really appreciate the way you are responding... i will send it but firstly about the command for static route you have sent me i was unable to understand the syntax as i am configuring a rout through "server 2008 routing Remote access console"..

I am also attaching the screenshot you can check it there and guide me through it i would explain it a little...

Interface Internal ( The one that is connected to the 10.10.10.0 network) having IP 10.10.10.10

Destination 172.20.0.0 ( Network ID to which i want to get access)

Gateway 172.20.13.16 ( The IP of another interface Lan card to which the network 172.20.0.0 is connected)

is this the right way to introduce Static route ... if yes then What about "route add -p" command... ?

" One thing to mention the Server B itself ping its 172.20.13.16 Lan interface and Server A IP 172.20.0.1 as well but its clients failed to communicate with them "

Its the routing table print of above configured setting

Command should be doing the same thing as the graphical interface.

In order to have a better descriptive network, perhaps change the ServerB interface names to Network10 and Network172 (it doesn't change how the network works whatever name you give them). I believe you can change from Network Interfaces.

Did you add that 172.20.0.0/255.255.0.0 route with gateway 172.20.13.16 on Interface 10.10.10.10? This doesn't look right. It is sending packets destined for 172.20.0.0 back on to 10.0.0.0 network. Delete that static one please.

By the way, did you actually test ServerA connectivity from networkB (after deleting the above static)? Not by ping but in Explorer address bar \\ServerA-Name or \\ServerA-IP-Address?

The address you want me to delete is assigned to the 2nd interface card of "Server B" that is connected to the Network 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 ...