> Hi,
>
> I have a WinXP SP2 machine with virtual PC installed + additions. I have
> installed windows server SP1 as a virtual machine. The windows XP machine
> is
> in my attick.
>
> I want to use the virtual win2k3 server as a test database server and
> would
> like to connect directly to it with remote desktop on my laptop. I cannot
> make this work.
>
> My home network is a simple 192.168.2.x network (DHCP). I can connect to
> al
> ,my other PC's fine. So the network is OK. But the virtual machine has
> 192.168.131.66 as IP-adres. The network adapter on the virtual machine is
> set
> to sharing (NAT) because I could not find another way to connect the
> virtual
> PC to the internet for virusscan and windows updates
>
> I cannot connect to the virtual machine with remote desktop and ping does
> not work too. I tried to disable the firewall on the virtual machine, but
> still no go.
>
> Does anyone know how to solve this?
>

> Your problem is a basic networking problem unrelated to Virtual PC.
>
> Your Virtual machine cannot use "Sharing (NAT)" if you want to be able to
> connect to it from another machine. That's what a NAT means. This is what it
> looks like, conceptually:
>
> Outside Network <--> NAT (Virtual PC) <--> Virtual Machine
> a.b.c.d <--> 192.168.2.x <--> 192.168.131.66
>
> When the Virtual Machine accesses Outside network, it looks like 192.168.2.x
> is accessing the Outside network. When Outside network tries to access the
> Virtual Machine, it cannot do so because what IP does it use to contact the
> Virtual Machine? If it uses 192.168.2.x, the network packet goes to the NAT
> and never makes it to the VM. If it uses 192.168.131.66, it never gets
> routed to the NAT and thus never reaches the VM. And since it is a NAT, the
> outside world should never know about 192.168.131.66 anyways. So, NAT
> prevents Outside Network from accessing Virtual Machine through the NAT
> while allowing the VM to access the Outside Network... which is the whole
> point of a NAT! :-)
>
> I suspect your XPSP2 Host is using Wireless network card. I had a similar
> problem (I run XPSP2 as Host with Windows Server SP1 as Guest, Host is on a
> wireless network card, and Guest cannot get to the Internet unless I
> configured its Virtual Network as "Sharing"). I then made the Host machine
> use a wired network card and then I didn't need the network to be "Sharing"
> and everything worked as-expected. I suspect it is by-design -- wireless and
> Virtual NIC seem to conflict.
>
> --
> //David
> IIS
> http://blogs.msdn.com/David.Wang
> This posting is provided "AS IS" with no warranties, and confers no rights.
> //
>
> "gooddaddy" <(email address - cut out)> wrote in message
> news:(email address - cut out)...
> > Hi,
> >
> > I have a WinXP SP2 machine with virtual PC installed + additions. I have
> > installed windows server SP1 as a virtual machine. The windows XP machine
> > is
> > in my attick.
> >
> > I want to use the virtual win2k3 server as a test database server and
> > would
> > like to connect directly to it with remote desktop on my laptop. I cannot
> > make this work.
> >
> > My home network is a simple 192.168.2.x network (DHCP). I can connect to
> > al
> > ,my other PC's fine. So the network is OK. But the virtual machine has
> > 192.168.131.66 as IP-adres. The network adapter on the virtual machine is
> > set
> > to sharing (NAT) because I could not find another way to connect the
> > virtual
> > PC to the internet for virusscan and windows updates
> >
> > I cannot connect to the virtual machine with remote desktop and ping does
> > not work too. I tried to disable the firewall on the virtual machine, but
> > still no go.
> >
> > Does anyone know how to solve this?
> >
>
>
>

> Thanks, David. I forgot about the NAT-functionality.
>
> I set the network setting of the virtual machine back to use the network
> card, and now iall works fine. I just don't understand it. Internet
> connectivity and remote desktop is OK now
>

> What is there to fix? It will all work as long as you don't put your
> server behind NAT. If you leave the vm at the default settings (ie using
> physical NIC of the host and getting its network config automatically) the
> vm will look just like another server on your local LAN.

> "gooddaddy" <(email address - cut out)> wrote in message
> news:(email address - cut out)...
>> Thanks, David. I forgot about the NAT-functionality.
>>
>> I set the network setting of the virtual machine back to use the
>> network card, and now iall works fine. I just don't understand it.
>> Internet connectivity and remote desktop is OK now
>>
>
> How did you fix it? I would like to try a similar scenario on my
> home LAN.
>
> Thanks,
>
> Jonathan