Hi people,

I have got a real strange issue here. I have VPC running fine and dandy on
one machine and it is able to connect to the network fine. However, I have
another identical machine (hardware wise) which I am trying to run the same
vpc (Windows XP SP2) on it and connect to a network, and it is failing.

The strangest thing about it is that the vpc gets assigned its IP settings
properly from the network DHCP, but then after that, I cannot ping anything
apart from the local host. I cant even ping the DHCP server that I just got
my IP settings from!?

Any ideas?

Cheers

Are you running a copies of the same vm on both? Unless you change the MAC
on one of them you would get a conflict.

"Leaky" <no@xxxxxx> wrote in message
news:%23SIVb0cuIHA.4772@xxxxxx

> Hi people,
>
> I have got a real strange issue here. I have VPC running fine and dandy
> on one machine and it is able to connect to the network fine. However, I
> have another identical machine (hardware wise) which I am trying to run
> the same vpc (Windows XP SP2) on it and connect to a network, and it is
> failing.
>
> The strangest thing about it is that the vpc gets assigned its IP settings
> properly from the network DHCP, but then after that, I cannot ping
> anything apart from the local host. I cant even ping the DHCP server that
> I just got my IP settings from!?
>
> Any ideas?
>
> Cheers
>

Im not running them at the same time. I have tried removing the mac address
out of the vmc file so it regenerates it.

This is very strange!


"Colin Barnhorst" <c.barnhorst@xxxxxx> wrote in message
news:EDFA9487-5FC7-4E99-853D-5AC2697C9181@xxxxxx

> Are you running a copies of the same vm on both? Unless you change the
> MAC on one of them you would get a conflict.
>
> "Leaky" <no@xxxxxx> wrote in message
> news:%23SIVb0cuIHA.4772@xxxxxx

>> Hi people,
>>
>> I have got a real strange issue here. I have VPC running fine and dandy
>> on one machine and it is able to connect to the network fine. However, I
>> have another identical machine (hardware wise) which I am trying to run
>> the same vpc (Windows XP SP2) on it and connect to a network, and it is
>> failing.
>>
>> The strangest thing about it is that the vpc gets assigned its IP
>> settings properly from the network DHCP, but then after that, I cannot
>> ping anything apart from the local host. I cant even ping the DHCP
>> server that I just got my IP settings from!?
>>
>> Any ideas?
>>
>> Cheers
>>

>

Even more odd, is that I have just shared out the image and added it to ms
vpc on another machine (same spec) and started it up there and it works
fine.

Ive been told that there isnt any funky switches here that only allow 1 IP
address per port, so it must be something specific to that machine.

Cheers

"Leaky" <no@xxxxxx> wrote in message
news:ueI6FdluIHA.420@xxxxxx

> Im not running them at the same time. I have tried removing the mac
> address out of the vmc file so it regenerates it.
>
> This is very strange!
>
>
> "Colin Barnhorst" <c.barnhorst@xxxxxx> wrote in message
> news:EDFA9487-5FC7-4E99-853D-5AC2697C9181@xxxxxx

>> Are you running a copies of the same vm on both? Unless you change the
>> MAC on one of them you would get a conflict.
>>
>> "Leaky" <no@xxxxxx> wrote in message
>> news:%23SIVb0cuIHA.4772@xxxxxx

>>> Hi people,
>>>
>>> I have got a real strange issue here. I have VPC running fine and dandy
>>> on one machine and it is able to connect to the network fine. However,
>>> I have another identical machine (hardware wise) which I am trying to
>>> run the same vpc (Windows XP SP2) on it and connect to a network, and it
>>> is failing.
>>>
>>> The strangest thing about it is that the vpc gets assigned its IP
>>> settings properly from the network DHCP, but then after that, I cannot
>>> ping anything apart from the local host. I cant even ping the DHCP
>>> server that I just got my IP settings from!?
>>>
>>> Any ideas?
>>>
>>> Cheers
>>>

>>

>
>

"Leaky" <no@xxxxxx> wrote in message
news:OznCXpluIHA.3792@xxxxxx

> Even more odd, is that I have just shared out the image and added it to ms
> vpc on another machine (same spec) and started it up there and it works
> fine.

When you use the 'New Virtual Machine' wizard to add an existing VM, it
automatically changes the MAC address (at least VPC2007 does this).

> ...

Well, i ran it up and it had the same mac address as when it is ran on the
offending PC, so it isnt the mac address.


"SaGS" <AntiSpamRemoveAllZsags54Z95@xxxxxx> wrote in message
news:O92xKOouIHA.1220@xxxxxx

> "Leaky" <no@xxxxxx> wrote in message
> news:OznCXpluIHA.3792@xxxxxx

>> Even more odd, is that I have just shared out the image and added it to
>> ms vpc on another machine (same spec) and started it up there and it
>> works fine.

>
> When you use the 'New Virtual Machine' wizard to add an existing VM, it
> automatically changes the MAC address (at least VPC2007 does this).
>

>> ...

>
>

>>> Even more odd, is that I have just shared out the image and added it to

>>> ms vpc on another machine (same spec) and started it up there and it
>>> works fine.

>>
>> When you use the 'New Virtual Machine' wizard to add an existing VM, it
>> automatically changes the MAC address (at least VPC2007 does this).

>Well, i ran it up and it had the same mac address as when it is ran on the
>offending PC, so it isnt the mac address.
>

You should always create a new guest when you copy your virtual
machine to another host. At the disk step just select the copied vhd
file and you will have a guest running with the appropriate hardware
emulation and a unique MAC address. Don't copy the vmc file.


Bo Berglund