Vpc nat is giving me class b address?

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

superbugged - 28 Apr 2004 18:16 GMT

WInxp as my host
Os is windows 2000 server

I am using "Nat" in vpc so I can use the dial up
connection on the host. My guest os is set up to "obtain
ip automatically" but for some odd reason virtual pc is
giving the guest os the ip of "169.254.168.49 with an
subnet of 255.255.0.0.

From what I understand the vpc nat is supposed to give me
an ip from 192.168.131.x and a subnet of 255.255.255.0
That is not happening for me. How do I correct this
problem?

Reply to this Message

anonymous@discussions.microsoft.com - 30 Apr 2004 01:46 GMT

When Windows 98, 2000, and XP can't find a DHCP server
(such as the NAT in VPC) they default to an "Automatic
Private IP Address" which is usually one like the
169.254.168.49 you metion.

In order for the NAT in VPC to work I'm pretty sure you
have to have the "Microsoft Loopback Adapter" installed
on your host OS.

>-----Original Message-----
>WInxp as my host
[quoted text clipped - 12 lines]
>
>.

Reply to this Message

Scott Baker - 30 Apr 2004 01:54 GMT

You do not have to install the Loopback adapter to use
NAT. From VPC's viewpoint, the loopback adapter is
another NIC on the Host. VPC's Shared Networking (NAT) is
built-in and includes DHCP service for the VMs connecting
to it.

You _are_ correct about the 169 address. The Guest OS is
not picking up DHCP for some reason, so it's assigning
its own.

Scott

>-----Original Message-----
>When Windows 98, 2000, and XP can't find a DHCP server
[quoted text clipped - 25 lines]
>>
>.

Reply to this Message