I have a windows XP machine with 3 network cards installed running the Dude. Network 2 and 3 have subnet routers behind the main Mikrotik. Routes are set and when operating networks 2 and 3 on separate machines everything works fine. I would like to eliminate one of the machines and only use on Dude computer.
The problem that I am having is that Network 2 and 3 get confused on which Gateway to use is my assumption. If I unplug Network 2 then Network 3 starts working if I plug Network 2 back in then Network 2 works again and Network 3 stops working. What stops working is that I can not get to any clients in the subnets. 10.10.2.49 is a 750UP and the addresses are 10.10.21.X, Subnets in Network 3 are located at 10.11.2.48 and use 10.11.61.X, 10.11.62.X etc.
The gateway is the default route. You have 3 default routes but only one of them has the lowest metric. On your windows server in a cmd prompt type “route print”. Find 0.0.0.0 with the lowest metric and that is the network card all your traffic is taking.
Since 10.11.61.x is not “connected” the route to it is through 10.11.2.250 but your route to 0.0.0.0 has the lowest cost and is through 192.168.1.1 the packet that is supposed to be sent to 10.11.61.x is going out the wrong interface and never gets to the correct network.
You see that the default route (Gateway.. or 0.0.0.0) have 100 . The 192,172 and 10 net’s have 15. Then the 15 metric is prioritised before 100 who is the default Gateway. This say something like. If traffic is not going to 172,192 or 10 nets, og to default.
Thanks for the help. This almost works. The 10.10.2.X network has a 750UP at 10.10.2.49 and all the clients are at 10.10.21.X. These are the only clients that I can’t ping and therefor the Dude does not see them. If I give 10.11.2.X a higher metric then the 10.10.21.X works but the entire 10.11.2.X network goes red.
OK I got it. I was talking with a friend about this and after looking at the “route print” we got currious about how to control the destination that is shown. He Google "Windows destination route and came up with this link http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/sag_tcpip_pro_addstaticroute.mspx?mfr=true . It seems that you can set routes in your computer just like you would in a router and it soved all of the problems. The command is like this.
