Thank you for quick response. I tried to add static route on both machines, SVR1 and SVR2 and the result was still erred out with the message "fullerA.local domain can not be contacted"
route add 192.168.0.0 mask 255.255.0.0 192.168.0.1 -p
route add 192.168.0.0 mask 255.255.0.0 192.168.1.1 -p
The domain controller, SVR1, is located on the 192.168.0.0/24 subnet and the target machine, SVR2, on the 192.168.1.0/24 subnet.
The static IP Address configuration on the target machine, SVR2:
**192.168.0.1 **default gateway. I do have a physical router which issues this value)
192.168.0.105 (DNS server) This value is also the IP address of domain controller
The default gateway is on one subnet and the target machine on another subnet, given that the static routes are added. I still have an error when trying to join target machine to the domain controller.
Am I doing something wrong here? Pleas help if you have available time.
Both, SVR1 and SVR2 are virtual machines (vmware) and using Bridged in network adapter setting. I am thinking if I am trying to physically connect my laptop to the router to check out if anything improves. My domain controller with other two remotely connected machines, and they all are on the same subnet as shown in the screenshot below:
Updated: To simulate the two different subnets, I placed the SVR1 (domain controller) machine on BRIDGED network, and the SVR2 (target) machine in NAT network in VMware environment. The result improves a bit.:
a. Now I can join the SVR2 into the controller domain (SVR1)
b. However, from SVR1, I cannot connect SVR2 into Server Manager for remote management.
b. I can ping to SVR1 from SVR2 but the ping failed from SVR1 to SVR2 ( It means that host in the NAT subnet can see host in the BRIDGED subnet but not the another way around ! Hmm?
I think the isssue is the vmware setting and I might check with vmware discussion forum for the solution
Anyway, Thank Mike as you already gave the pertinent answer and I can head to the right direction when working with domain controller connection on different subnets.
Meanwhile, I am back to watching Printer Sharing Episode.