Vista - Routing problems with Virtual PC

I have setup 2 test enviornments which consists of Windows 2003 virtual pc
and an XP virtual pc on network 1 and Small Business server virtual pc and an
XP virtual pc on network 2. The network configurations are as follows. From
XPvirtual pc1, I can ping both NICs on Win2003 but not the host
(192.168.1.66). From XPvirtual pc2 I can ping the host (192.168.1.66) IP but
not from the host back. I have setup RRAS the same on both servers but am
getting different results. Ultimately I am looking to test the servers as
routers to/from the 192.168.1.0 network. Any help is appreciated.
Host : 192.168.1.66 255.255.255.0 192.168.1.1
Win2003: Nic1: 192.168.1.10 255.255.255.0 192.168.1.1, Nic2: 192.168.2.1
255.255.255.0 -no gateway
XPvirtual pc1: 192.168.2.10 255.255.255.0 192.168.2.1
SBS: Nic1:192.168.1.15 255.255.255.0 192.168.1.1, Nic2:192.168.3.1
255.255.255.0 -no gateway
XPvirtual pc2:192.168.3.10 255.255.255.0 192.168.3.1

"Drake96" <Drake96@xxxxxx> wrote in message
news:1837968D-C0E4-4018-BA72-41F190CEB10C@xxxxxxRouting with virtual machines and virtual networks is just the same as
any other routing. The networking protocols don't know or care whether you
are using vms or virtual networks.

Pings in on direction only are almost always caused by firewall problems.
Temporarily disable the firewall or modify the firewall settings on the
clients to allow ICMP echo.

> Routing with virtual machines and virtual networks is just the same asNot exactly - I have had a problem with Outpost Firewall where it turned out
to be a conflict between the Virtual PC and Outpost network drivers that are
installed into the physical driver properties.

Thanks for the reply. I should have provided more information in my origional
post. I have no firewalls enabled on any of the virtuals or the host box. I
have also tried creating static routes, that did not resolve the problem
either. The host is a laptop with a wireless nic and the built in nic. I am
using a loopback adapter on the built in nic (as the internal network
connection). At first, I tried using the local only option for the xp vm's
and the internal nic of the servers but that did not work either. I have
tried bridging the network connections without success and changed the
binding order for the NICs. At this point I am just grasping at anything I
can think of. I have never used windows as a router before, but it does not
look to be difficult. I have verified the steps from a number of sources on
the net. Any additional help is appreciated.

"Bill Grant" wrote:

If you can ping in one direction, there is no point in changing any
routes.

When you ping, the initial message is sent to the target machine using
the routes that are on the initiating machine. The reply is sent using the
routes which are on the target machine. If you get a ping reply, the routes
on both machines are correct. That is why ping is used to check network
connectivity.

If you can ping in one direction and not the other, the problem is not
the basic routing. It is something blocking the target machine from
responding to an ICMP echo request. With XP/Vista hosts, this is usually the
built-in Windows firewall.

"Drake96" <drake96@xxxxxx> wrote in message
news:E4B54F3B-1A20-4E75-B0A8-F9A4136B32CF@xxxxxx

Thanks for the reply. I should have provided more information in my origional
post. I have no firewalls enabled on any of the virtuals or the host box. I
have also tried creating static routes, that did not resolve the problem
either. The host is a laptop with a wireless nic and the built in nic. I am
using a loopback adapter on the built in nic (as the internal network
connection). At first, I tried using the local only option for the xp vm's
and the internal nic of the servers but that did not work either. I have
tried bridging the network connections without success and changed the
binding order for the NICs. At this point I am just grasping at anything I
can think of. I have never used windows as a router before, but it does not
look to be difficult. I have verified the steps from a number of sources on
the net. Any additional help is appreciated.


"Bill Grant" wrote:

> Thanks for the reply.I cannot think of the definitely solution to your problem.



When getting into such problems I normally use a program dedicated for such
problems, and one program I have used with success is MegaPing where I scan
the whole network.



You also could try "ipconfig" and "route print" in a command prompt, which
can tell you a lot about the network.

"drake96" <Drake96@xxxxxx> wrote in message
news:358026C2-B660-4682-8DFA-A6955C8D0F2D@xxxxxxPing is not the best tool to use for a situation like this. You will nee
to use normal networking tools.


RRAS works fine as a router whether it is running in a physical or
virtual machine. If you rally can't sort it out you should post in the
networking newsgroup. It rally has nothing to do with VPC.

"Bill Grant" <not.available@xxxxxx> wrote in message
news:OBC42XArJHA.5912@xxxxxxI really (or rally) should read what I type before I hit Send.