Comments on: Virtual PC IP Routing: enabling VPC NAT & loopback connector at the same time

By: Duane Slonski

Duane Slonski — Thu, 11 Mar 2010 19:30:13 +0000

Just landed on this post via Google search. I love it. This post switch my percept and I am getting the RSS feeds. Cheers Up.

By: justinohms

justinohms — Fri, 22 Jan 2010 00:32:06 +0000

You would just replace the word ‘add’ with ‘delete’ actually I think you just have to put the IP so it would be route DELETE 172.16.16.4 if you run the command route -? you will get the help file for the route command.

By: EDH

EDH — Tue, 12 Jan 2010 13:20:47 +0000

What’s the command to UNDO the “route –P add 172.16.16.4 mask 255.255.255.255 172.16.16.2 metric 1″ command ?

Thanks,
EDH

By: Anthony Rodriguez

Anthony Rodriguez — Mon, 14 Dec 2009 22:31:42 +0000

This is a great post. Tried your tips and it worked exactly as you described. Nice work.n

By: Chris Houston

Chris Houston — Fri, 20 Nov 2009 16:08:08 +0000

Thank you for posting this!

After trying three or four different solutions found on other blogs to no avail, I eventually was able to get a ping to work using your method.

( I am running Windows 7 with a virtual XP SP 3 )

I then found that the windows firewall was blocking HTTP connections between the host and the vitual machine, once this was fixed, hey presto it worked!

Thanks again,

Chris

By: W

Fri, 21 Aug 2009 02:55:44 +0000

Thanks for the great info.

What would you do if you wanted to limit the virtual pc to only be able to see the host machine, and not the internet as a whole (e.g. to basically use the virtual pc os as an IE6 testing virtual machine only).

Thanks.

By: virtpc

virtpc — Thu, 06 Aug 2009 11:10:17 +0000

One point that was at first unclear to me: After setting up the loopback adapter on the host (instructions for doing so here), the host system's loopback connector will appear in the guest system's network connections list as another generic ethernet adapter. Configure *that* adapter to 172.16.16.4, if it doesn't default to that setting.

By: deaconb

deaconb — Wed, 15 Jul 2009 15:06:43 +0000

I had some issues with your routing table command.

You have a typo in the gateway IP – 2.16.16.2 should be 172.16.16.2.

Also, I was unable to get the command to run unless the -p parameter is passed as the last item:

route ADD 172.16.16.2 MASK 255.255.255.255 172.16.16.4 METRIC 1 -p

Typos aside… thanks for the article and saving me a bunch of time trying to figure this out on my own!