11-28-2014 01:24 AM - edited 11-28-2014 01:25 AM
Thanks for your idea!
Actually the host only saves the route info to Gateway as below. The route info to server is saved in Gateway.
So this method seems not so reliable.
11-28-2014 07:02 AM
11-28-2014 08:08 AM
Thanks so much for your reply!
I set 0.0.0.0 as the destination address and the result is as the screenshot.
I'll check again and come back to update.
Thanks again and have a nice holiday!
11-28-2014 09:19 AM
12-02-2014 01:40 AM
If I use "route print + server address", there is no route info (active routes is none).
This means route info to the server address is saved in gateway, not the localhost.
So I use 0.0.0.0 as the destination address.
12-02-2014 10:33 AM
Ah, you're right, sorry. As I mentioned I was away from the computer for the Thanksgiving holiday and couldn't test. You'll probably get the same result from simply "route print" without the IP address in that case. I'm not sure if that tells you anything useful, though, although you can use the "metric" to determine which gateway will be used preferentially. However I still think it's the case that if your network connection has a gateway that doesn't actually route to the outside world, then there should be no configured default gateway for that connection. If you do need to go through a gateway for some addresses, you can configure a route using the correct netmask to achieve that.