Hi,

I have a WinXP SP2 machine with virtual PC installed. I have
installed windows server 2003 as a virtual machine.

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 Desktop. I cannot
make this work.

My network is a simple 192.168.10.20 - 192.168.10.50 range assigned through
DHCP. I can connect to all,my other PC's fine. So the network is OK. But the
virtual machine has getting
192.168.131.66 as IP-address through DHCP Server. But this Ip address is not
in my network, which is in another range.

I cannot connect to the virtual machine with remote desktop but i can ping
to virtual machine. I tried to disable the firewall on the virtual machine,
but still no go.

I need to get access my Virtual machine through remote desktop connection.

Does anyone know how to solve this?

On Mon, 2 Feb 2009 22:00:01 -0800, Ansar
<Ansar@xxxxxx> wrote:

>Hi,
>
>I have a WinXP SP2 machine with virtual PC installed. I have
>installed windows server 2003 as a virtual machine.
>
>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 Desktop. I cannot
>make this work.
>
>My network is a simple 192.168.10.20 - 192.168.10.50 range assigned through
>DHCP. I can connect to all,my other PC's fine. So the network is OK. But the
>virtual machine has getting
>192.168.131.66 as IP-address through DHCP Server. But this Ip address is not
>in my network, which is in another range.
>
>I cannot connect to the virtual machine with remote desktop but i can ping
>to virtual machine. I tried to disable the firewall on the virtual machine,
>but still no go.
>
>I need to get access my Virtual machine through remote desktop connection.
>
>Does anyone know how to solve this?

If you're getting a 131 range IP, then you're using Shared Networking.
You won't get host-guest communication using it. Under the Network
settings change from Shared Networking to your NIC listed there.
This will get your guest an IP in the correct range .10.x and should
also allow RDP. After you make the switch reboot the guest OS for the
easiest config.

--
Cheers,
Steve Jain, Virtual Machine MVP
http://vpc.essjae.com/

Hello Steve,

Thank you for your reply!!

I am not get the point that you have mentioned "Under the Network
settings change from Shared Networking to your NIC listed there" .

Please tell me the configuration once again... it could be very helpful for
me..

I have configured the IP address manually range of 192.168.10.XX. but still
the problem exists...

Once again thanks ...

Regards
Ansar

"Steve Jain [MVP]" wrote:

> On Mon, 2 Feb 2009 22:00:01 -0800, Ansar
> <Ansar@xxxxxx> wrote:
>

> >Hi,
> >
> >I have a WinXP SP2 machine with virtual PC installed. I have
> >installed windows server 2003 as a virtual machine.
> >
> >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 Desktop. I cannot
> >make this work.
> >
> >My network is a simple 192.168.10.20 - 192.168.10.50 range assigned through
> >DHCP. I can connect to all,my other PC's fine. So the network is OK. But the
> >virtual machine has getting
> >192.168.131.66 as IP-address through DHCP Server. But this Ip address is not
> >in my network, which is in another range.
> >
> >I cannot connect to the virtual machine with remote desktop but i can ping
> >to virtual machine. I tried to disable the firewall on the virtual machine,
> >but still no go.
> >
> >I need to get access my Virtual machine through remote desktop connection.
> >
> >Does anyone know how to solve this?

>
> If you're getting a 131 range IP, then you're using Shared Networking.
> You won't get host-guest communication using it. Under the Network
> settings change from Shared Networking to your NIC listed there.
> This will get your guest an IP in the correct range .10.x and should
> also allow RDP. After you make the switch reboot the guest OS for the
> easiest config.
>
> --
> Cheers,
> Steve Jain, Virtual Machine MVP
> http://vpc.essjae.com/
>

On Tue, 3 Feb 2009 22:34:00 -0800, Ansar
<Ansar@xxxxxx> wrote:

>
>Hello Steve,
>
>Thank you for your reply!!
>
>I am not get the point that you have mentioned "Under the Network
> settings change from Shared Networking to your NIC listed there" .
>
>Please tell me the configuration once again... it could be very helpful for
>me..
>

Go to the Settings of the VM
Under the Networking section, where adapter 1 is specified, click the
selection menu.
Change from Shared Networking to your NIC listed there, what is
actually listed depends on the NIC installed. On mine it says "Intel
82567LM Gigabit Network"

Once this is selected your VM will be connected directly to your
host's network instead of via NAT in Shared Networking.

After this reboot, the VM so the correct IP can be gotten from your
DHCP.

--
Cheers,
Steve Jain, Virtual Machine MVP
http://vpc.essjae.com/

Hello Steve,

Thanks for your valuable reply!!

I have tried to change the settings of VM from shared networking to NIC
card. But my local system NIC adpater is not showing there...it only shows
local only, Not connected, shared networking (NAT).

I have changed the shared networking to local only and restarted the server.
But still Virtual Machine is not getting Ip address from DHCP Server.

Please reply..

Regards
Ansar



"Steve Jain [MVP]" wrote:

> On Tue, 3 Feb 2009 22:34:00 -0800, Ansar
> <Ansar@xxxxxx> wrote:
>

> >
> >Hello Steve,
> >
> >Thank you for your reply!!
> >
> >I am not get the point that you have mentioned "Under the Network
> > settings change from Shared Networking to your NIC listed there" .
> >
> >Please tell me the configuration once again... it could be very helpful for
> >me..
> >

>
> Go to the Settings of the VM
> Under the Networking section, where adapter 1 is specified, click the
> selection menu.
> Change from Shared Networking to your NIC listed there, what is
> actually listed depends on the NIC installed. On mine it says "Intel
> 82567LM Gigabit Network"
>
> Once this is selected your VM will be connected directly to your
> host's network instead of via NAT in Shared Networking.
>
> After this reboot, the VM so the correct IP can be gotten from your
> DHCP.
>
> --
> Cheers,
> Steve Jain, Virtual Machine MVP
> http://vpc.essjae.com/
>

On Thu, 5 Feb 2009 20:01:01 -0800, Ansar
<Ansar@xxxxxx> wrote:

>
>"Steve Jain [MVP]" wrote:
>

>> On Tue, 3 Feb 2009 22:34:00 -0800, Ansar
>> <Ansar@xxxxxx> wrote:
>>

>> >
>> >Hello Steve,
>> >
>> >Thank you for your reply!!
>> >
>> >I am not get the point that you have mentioned "Under the Network
>> > settings change from Shared Networking to your NIC listed there" .
>> >
>> >Please tell me the configuration once again... it could be very helpful for
>> >me..
>> >

>>
>> Go to the Settings of the VM
>> Under the Networking section, where adapter 1 is specified, click the
>> selection menu.
>> Change from Shared Networking to your NIC listed there, what is
>> actually listed depends on the NIC installed. On mine it says "Intel
>> 82567LM Gigabit Network"
>>
>> Once this is selected your VM will be connected directly to your
>> host's network instead of via NAT in Shared Networking.
>>
>> After this reboot, the VM so the correct IP can be gotten from your
>> DHCP.
>>

>
>Thanks for your valuable reply!!
>
>I have tried to change the settings of VM from shared networking to NIC
>card. But my local system NIC adpater is not showing there...it only shows
>local only, Not connected, shared networking (NAT).
>
>I have changed the shared networking to local only and restarted the server.
>But still Virtual Machine is not getting Ip address from DHCP Server.
>

If your physical NIC does not show up in the list then you have a
problem with the NIC driver or you are using a wireless NIC on your
host.

First attempt at solving this:
- Open the properties of your NIC (on the host)
- Make sure that the "Virtual Machine Network Services" item is
checked in the list. If it is not then:
- Check it and OK out.
- Now stop and start VPC2007
- Go to the guest properties again and see if the NIC has appeared
in the list. If so select it and start the guest.
- Chances are that the networking will now begin to work as you
want.

Second attempt:
- If the above does not work then you need to locate a newer driver
for your network card on the host. Your NIC driver probably does not
cooperate with the VMNS services in the present version....

Finally:
Local only will not give you any connectivity at all! It is meant to
be used for *isolated* guest networks where the intention is that the
guests will *not* be visible to any other computers than the virtual
ones, including being invisible from the host.

--

Bo Berglund (Sweden)