Using Shared Networking (NAT) with a Windows Server 2003 virtual machinehttp://blogs.msdn.com/virtual_pc_guy/archive/2005/01/06/347965.aspxVirtual PC has a convenient feature called 'Shared Networking'. What this is is a small virtual NAT (network address translation) router - which is quite similar to the cheap hardware broadband routers that a lot of people use (myself included). The advantageen-USCommunityServer 2.1 SP1 (Build: 61025.2)re: Using Shared Networking (NAT) with a Windows Server 2003 virtual machinehttp://blogs.msdn.com/virtual_pc_guy/archive/2005/01/06/347965.aspx#347999Fri, 07 Jan 2005 00:03:00 GMT91d46819-8472-40ad-a661-2c78acb4018c:347999Deven KampenhoutGreat post! NAT is one of those simple yet ever-so-usefull technologies. I recall my first experiences with NAT when I built my own home-grown version of the DSL gateway before they were available on the public market. <br> <br>Another HUGE advantage of NAT is that it creates a virtually unlimited number of IP addresses. In the case where you'd like to create a large number of virtual machines, you're not limited by the amount of &quot;real&quot; IP space allocated to your network.re: Using Shared Networking (NAT) with a Windows Server 2003 virtual machinehttp://blogs.msdn.com/virtual_pc_guy/archive/2005/01/06/347965.aspx#348547Fri, 07 Jan 2005 18:06:00 GMT91d46819-8472-40ad-a661-2c78acb4018c:348547Anonymous CowardNow if only VPC let you edit the NAT subnet and addresses. Yes, I really had an issue with this! VMWare does let you :-)