The short story is that although the two IP subnets may be on the same physical "segment" (or virtual physical segment....), they are not on the same IP subnet or, as you call it, network. Therefore, there has to be a router with an interface on each subnet to act as the default gateway to the other subnet.
-----Original Message----- From: Stephen Wimberly [mailto:swimbe...@gmail.com] Sent: Friday, July 30, 2010 10:27 AM To: NT System Admin Issues Subject: Hyper-V and 'Default Gateway' Is it possible to use a different default gateway on one Hyper-V guest than the Hyper-V host is using? What I have is a situation where we have multiple IP ranges within the "same network" meaning there is no router nor firewall between the different IP segments, but each IP subnet is different so I have multiple default gateways. let's say the first is 192.168.0.1 with a mask of 255.255.255.192 and the second would be 192.168.0.70 / mask of 255.255.255.192. In short I have tried all kinds of configurations but i can't seem to get a connection using any other gateway address, and it would make sense that it should agree with the host, but I cant find anywhere to 'verify' that! I have found many documents telling me that all the virtual servers on a Hyper-V host must be in the "same network" but no where does it define the parameters of the network! (Each of my Hyper-V guests are pointed directly at a physical network card on the host, they are _not_ NATed) ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
