Re: Win2k3 R2 does not route to virtual guests
- From: martin.edelius@xxxxxxxxx
- Date: 7 Jul 2006 15:54:40 -0700
Hi Philip.
1. You don't add routes. All networks are "Directly Connected
Networks",...there are no routes to add.
You need to give me some context here. Are you talking about the entire
setup, the firewall or the host?
2. Get rid of the registry entries you created. They don't apply to this,
and they don't belong there.
Ok, no problemo.
3. ISA is a proxy server not a router.
We use an ISA as a combined firewall/router in another setup so I'm not
sure what you base this statement on. I might have misunderstood the
job of a router (to re-route traffic between networks?).
To use ISA this way requires three
networks with three nics,... the External which would be irrelavant,
and,...two different "internal" networks. The first Internal one is there by
default,...you have to create the other one. Then setup a "routing
relationship" between the two internal networks. Then create Access Rules to
handle the traffic between the two internal networks.
I interpret what you are saying as that the ISA can't redirect traffic
to a device that sits on the same interface/network that the traffic
originally came from. Is this correct?
In VMware, the ISA External Nic needs to be associated with the physical Nic
that goes out to the "real world". The two Internal Nics have to be
associated with two distinct "Virtual nics". All other machies in the "VM
world" have to be associated with the same "virtual nic" corresponding to
the particualr Segment they are on,...only the ISA External nic is ever
associated with the "real world". You "real world" LAN becomes the
"Internet" as far as ISA is concerned
I think you misunderstood my setup. The best way I can explain it to
you is with the image I linked to in my original post.
I do not have a virtual ISA for instance. The ISA is a physical machine
on the physical network that acts as the default gateway (firewall) for
the physical network.
The ISA is irrelevant though as the setup still doesn't work even if I
add a route to my client's local routing table that tells it to use
192.168.0.201 as a gateway for all traffic aimed at the 192.168.194.x
network.
And as far as terminology go -- feel free to help me use the correct
one. It would probably make life easier for all of us. ;)
-- Martin
.
- References:
- Win2k3 R2 does not route to virtual guests
- From: martin . edelius
- Win2k3 R2 does not route to virtual guests
- Prev by Date: Win2k3 R2 does not route to virtual guests
- Next by Date: Re: switch problem
- Previous by thread: Win2k3 R2 does not route to virtual guests
- Next by thread: Re: Win2k3 R2 does not route to virtual guests
- Index(es):
Relevant Pages
|