I have been working with Microsoft BDD and WIM files to deploy Vista
Business images out to users. The first machine I roll out, I have an
issue with a residual ip address somewhere in the system.

We use static ip addresses and for some reason, this machine has
decided to hold on to the static address I used to initially prep the
machine. It's not in the static address field in the network config.
It's not in the advanced table. It's not setup as an alternate
address. It's an IPv4 address but is no where to be found.

I have scanned the registery and it's not in there unless it's encoded
somehow.

Configuring the card for DHCP and release/renew did not clear it.

Configuring the actual manual address did not fix it (it now has 2
addresses). Configuring the bad address as the manual one would not
remove it either.

Uninstalling the card and reinstalling it did not fix it.

I can't find this anywhere. It's the oddest thing I have ever seen.
If I give the pc a static DNS and leave the ip address empty, the
computer will function properly on the network because of this hidden
address.

Any help or thoughts would be appreciated.

Chris Harvie

wrote in message
oups.com...
I have been working with Microsoft BDD and WIM files to deploy Vista
Business images out to users. The first machine I roll out, I have an
issue with a residual ip address somewhere in the system.

We use static ip addresses and for some reason, this machine has
decided to hold on to the static address I used to initially prep the
machine. It's not in the static address field in the network config.
It's not in the advanced table. It's not setup as an alternate
address. It's an IPv4 address but is no where to be found.

I have scanned the registery and it's not in there unless it's encoded
somehow.

Configuring the card for DHCP and release/renew did not clear it.

Configuring the actual manual address did not fix it (it now has 2
addresses). Configuring the bad address as the manual one would not
remove it either.

Uninstalling the card and reinstalling it did not fix it.

I can't find this anywhere. It's the oddest thing I have ever seen.
If I give the pc a static DNS and leave the ip address empty, the
computer will function properly on the network because of this hidden
address.

Any help or thoughts would be appreciated.

Chris Harvie

How about the HOSTS file?
Jim

I have a thought.

wrote in message
oups.com...
I have been working with Microsoft BDD and WIM files to deploy Vista
Business images out to users. The first machine I roll out, I have an
issue with a residual ip address somewhere in the system.

We use static ip addresses and for some reason, this machine has
decided to hold on to the static address I used to initially prep the
machine. It's not in the static address field in the network config.
It's not in the advanced table. It's not setup as an alternate
address. It's an IPv4 address but is no where to be found.

I have scanned the registery and it's not in there unless it's encoded
somehow.

Configuring the card for DHCP and release/renew did not clear it.

Configuring the actual manual address did not fix it (it now has 2
addresses). Configuring the bad address as the manual one would not
remove it either.

Uninstalling the card and reinstalling it did not fix it.

I can't find this anywhere. It's the oddest thing I have ever seen.
If I give the pc a static DNS and leave the ip address empty, the
computer will function properly on the network because of this hidden
address.

Any help or thoughts would be appreciated.

Chris Harvie

On Jun 28, 4:20 pm, "Jim" wrote:

How about the HOSTS file?
Jim- Hide quoted text -

- Show quoted text -

The host file is just the standard hosts file with the two local
addresses 127.0.0.1 and ::1 for IPv4 and IPv6 respectively.

I just spent about an hour on the phone with HP support and they are
stumped too. Most likely we are going to have to push it up to
Microsoft.

Thanks though.

Chris

On Jun 28, 4:24 pm, "Vista_Support"
wrote:
I have a thought.


Was it any good?