I have an XP laptop (spyware/virus free - or as close as can be! + all
service packs) that gets a DHCP address from a netgear DG834G at home
and it gets 10.0.0.3. no problem there.

As soon as this laptop is brought into work it is supposed to get a
DHCP address (also on a 10.x.x.x network) but for a fraction of a
second retains its 10.0.0.3 address and it has an IP conflict with a
domain controller (2003 R2 server), before getting a DHCP address
correctly. Because this conflicts with a DC it causes all sorts of
problems.

The obvious solution is to change the DHCP scope at home but we
shouldn't need to do this, or change the DC's IP Address but we
shouldn't need to do this.

Any ideas?

Thanks
Gavin Shakespeare

Modify the NetGear so that it's DHCP allocation range starts beyond the
IP address of your Domain controller.

<(E-Mail Removed)> wrote in message
news:3b26b5a8-eb0c-485e-a2cf-(E-Mail Removed)...
>I have an XP laptop (spyware/virus free - or as close as can be! + all
> service packs) that gets a DHCP address from a netgear DG834G at home
> and it gets 10.0.0.3. no problem there.
>
> As soon as this laptop is brought into work it is supposed to get a
> DHCP address (also on a 10.x.x.x network) but for a fraction of a
> second retains its 10.0.0.3 address and it has an IP conflict with a
> domain controller (2003 R2 server), before getting a DHCP address
> correctly. Because this conflicts with a DC it causes all sorts of
> problems.
>
> The obvious solution is to change the DHCP scope at home but we
> shouldn't need to do this, or change the DC's IP Address but we
> shouldn't need to do this.
>
> Any ideas?
>
> Thanks
> Gavin Shakespeare

In article <3b26b5a8-eb0c-485e-a2cf-
(E-Mail Removed)>, (E-Mail Removed)
says...
> I have an XP laptop (spyware/virus free - or as close as can be! + all
> service packs) that gets a DHCP address from a netgear DG834G at home
> and it gets 10.0.0.3. no problem there.
>
> As soon as this laptop is brought into work it is supposed to get a
> DHCP address (also on a 10.x.x.x network) but for a fraction of a
> second retains its 10.0.0.3 address and it has an IP conflict with a
> domain controller (2003 R2 server), before getting a DHCP address
> correctly. Because this conflicts with a DC it causes all sorts of
> problems.
>
> The obvious solution is to change the DHCP scope at home but we
> shouldn't need to do this, or change the DC's IP Address but we
> shouldn't need to do this.
>
> Any ideas?

Are you doing a full shutdown on the laptop or are you doing a
suspend/resume?

I've never seen a laptop retain an IP after it's properly shut-down, but
it makes sense that it would retain the IP after a suspend.

--

Leythos
- Igitur qui desiderat pacem, praeparet bellum.
- Calling an illegal alien an "undocumented worker" is like calling a
drug dealer an "unlicensed pharmacist"
(E-Mail Removed) (remove 999 for proper email address)

<(E-Mail Removed)> wrote in message
news:3b26b5a8-eb0c-485e-a2cf-(E-Mail Removed)...
>I have an XP laptop (spyware/virus free - or as close as can be! + all
> service packs) that gets a DHCP address from a netgear DG834G at home
> and it gets 10.0.0.3. no problem there.
>
> As soon as this laptop is brought into work it is supposed to get a
> DHCP address (also on a 10.x.x.x network) but for a fraction of a
> second retains its 10.0.0.3 address and it has an IP conflict with a
> domain controller (2003 R2 server), before getting a DHCP address
> correctly. Because this conflicts with a DC it causes all sorts of
> problems.
>
> The obvious solution is to change the DHCP scope at home but we
> shouldn't need to do this, or change the DC's IP Address but we
> shouldn't need to do this.
>
> Any ideas?
>
> Thanks
> Gavin Shakespeare

Put this text in a file named "IP_reset.cmd" on the desktop:

ipconfig /release
ipconfig /renew

Save it and run it at startup and whenever needed. Otherwise, I agree, it
sounds like that laptop is being closed and carried rather than shut down.

HTH
-pk