How routing works?

I dont think the subnets can comunicate if I remove the the lan cable from the two switches that connect them. I dont think its internaling going from one interface to the other i think its going out of the interface onto the physical network and then to the other interface.

i noticed when did tracert from from worksation 192.168.1.2 to 192.168.0.151 it went straight there. 192.168.1.100 and 192.168.0.151 are both in the RARS server. And i had workstation 192.168.1.2's gateway 192.168.1.100. When i went to ping another computer in the 192.168.0.0 subnet it would hit 192.168.1.100 then the computer. I think the routing was going from the source to the RARS interface then back out into the physical network i dont think it was internaly routing it. I changed the gate way on the 192.168.1.2 to 192.168.0.151 I know that it was internally routing to 192.168.0.151 because it went straight there. I did this through remote desktop so i wont know till i get to work on monday when i remove the lan cable if the routing will work then the subnets can be physically seperated and each have their own broadcast domain

Hi Brandon,

I think that result is expected. The tracert will show each hop, the RRAS will be the first hop along the path, it will show the IP Address of the interface that it hits, in this case 192.168.1.100 and then hit the computer next since its only leaving the 192.168.0.151 so i wouldn't really expect to see this in the trace.

I think you will find that if you unplug the lead between the switches and just have the RRAS server plugged into both switches it should still work because it will then route through the RRAS server.

Cheers

I didn't need the extra lan cable connecting the two subnets they are each in there own colision domains now. And the Dhcp is not a problem they each are getting Dhcp from there assigned server. the only way the two subnets are connected is through the fact that the two nics are in the same server routing between each other.