Stupid windows xp client getting out of scope address

Hello

I have a client xp laptop that on connection to the lan tries to use an
out of scope address thereby causing a conflict with another appliance
with a fixed ip address. I have tried all the usual practices including
commands at the prompt, eliminating all references to the ip address
from the registry but still the client keeps using the same address
until I do ipconfig release then renew (it then gets a correct address).
Any suggestions other than a big hammer would be appreciated.

PS DHCP server is Windows 2003 SBS

Regards

Frustrated John

Was the XP computer loaded with an image from another computer or have you
changed a NIC in it? Sometimes an old NIC is hanging around in the registry
and needs to be removed. If the old NIC used a static IP this could be the
cause of the problem. Use method #1 in the following link to see if there
are any old NICs that need to be uninstalled.

http://support.microsoft.com/kb/269155

--
Kerry Brown
MS-MVP - Windows Desktop Experience: Systems Administration
http://www.vistahelp.ca/phpBB2/
http://vistahelpca.blogspot.com/


"John Gelavis" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Hello
>
> I have a client xp laptop that on connection to the lan tries to use an
> out of scope address thereby causing a conflict with another appliance
> with a fixed ip address. I have tried all the usual practices including
> commands at the prompt, eliminating all references to the ip address from
> the registry but still the client keeps using the same address until I do
> ipconfig release then renew (it then gets a correct address). Any
> suggestions other than a big hammer would be appreciated.
>
> PS DHCP server is Windows 2003 SBS
>
> Regards
>
> Frustrated John

John Gelavis <(E-Mail Removed)> wrote:
> Hello
>
> I have a client xp laptop that on connection to the lan tries to use
> an out of scope address thereby causing a conflict with another
> appliance with a fixed ip address. I have tried all the usual
> practices including commands at the prompt, eliminating all
> references to the ip address from the registry but still the client
> keeps using the same address until I do ipconfig release then renew
> (it then gets a correct address). Any suggestions other than a big hammer
> would be appreciated.
> PS DHCP server is Windows 2003 SBS
>
> Regards
>
> Frustrated John

What do you mean by an out of scope address? Is the laptop being connected
to your LAN while it's got an IP address assigned from another DHCP server
(on another network)?

What if the laptop is in a powered down state when connected, and then
powered up after being plugged in?

Lanwench [MVP - Exchange] wrote:
> John Gelavis <(E-Mail Removed)> wrote:
>> Hello
>>
>> I have a client xp laptop that on connection to the lan tries to use
>> an out of scope address thereby causing a conflict with another
>> appliance with a fixed ip address. I have tried all the usual
>> practices including commands at the prompt, eliminating all
>> references to the ip address from the registry but still the client
>> keeps using the same address until I do ipconfig release then renew
>> (it then gets a correct address). Any suggestions other than a big hammer
>> would be appreciated.
>> PS DHCP server is Windows 2003 SBS
>>
>> Regards
>>
>> Frustrated John
>
> What do you mean by an out of scope address? Is the laptop being connected
> to your LAN while it's got an IP address assigned from another DHCP server
> (on another network)?
>
> What if the laptop is in a powered down state when connected, and then
> powered up after being plugged in?
>
>
I have been using the scope facility to restrict the lan subnet in my
Win 2003 Server so that DHCP clients are only able to get IP addresses
from a certain range. This way I can prevent (or so I thought) devices
from getting IP addresses that belong to devices with fixed IP addresses.

John Gelavis <(E-Mail Removed)> wrote:
> Lanwench [MVP - Exchange] wrote:
>> John Gelavis <(E-Mail Removed)> wrote:
>>> Hello
>>>
>>> I have a client xp laptop that on connection to the lan tries to use
>>> an out of scope address thereby causing a conflict with another
>>> appliance with a fixed ip address. I have tried all the usual
>>> practices including commands at the prompt, eliminating all
>>> references to the ip address from the registry but still the client
>>> keeps using the same address until I do ipconfig release then renew
>>> (it then gets a correct address). Any suggestions other than a big
>>> hammer would be appreciated.
>>> PS DHCP server is Windows 2003 SBS
>>>
>>> Regards
>>>
>>> Frustrated John
>>
>> What do you mean by an out of scope address? Is the laptop being
>> connected to your LAN while it's got an IP address assigned from
>> another DHCP server (on another network)?
>>
>> What if the laptop is in a powered down state when connected, and
>> then powered up after being plugged in?
>>
>>
> I have been using the scope facility to restrict the lan subnet in my
> Win 2003 Server so that DHCP clients are only able to get IP addresses
> from a certain range. This way I can prevent (or so I thought) devices
> from getting IP addresses that belong to devices with fixed IP
> addresses.

Do you mean exclusions? That's what I use; a range of IPs at both the
beginning & end of the subnet are excluded from DHCP. All my static
addresses are assigned IPs in the beginning of the range.

You haven't really answered all my questions, though.

Lanwench [MVP - Exchange] wrote:
> John Gelavis <(E-Mail Removed)> wrote:
>> Lanwench [MVP - Exchange] wrote:
>>> John Gelavis <(E-Mail Removed)> wrote:
>>>> Hello
>>>>
>>>> I have a client xp laptop that on connection to the lan tries to use
>>>> an out of scope address thereby causing a conflict with another
>>>> appliance with a fixed ip address. I have tried all the usual
>>>> practices including commands at the prompt, eliminating all
>>>> references to the ip address from the registry but still the client
>>>> keeps using the same address until I do ipconfig release then renew
>>>> (it then gets a correct address). Any suggestions other than a big
>>>> hammer would be appreciated.
>>>> PS DHCP server is Windows 2003 SBS
>>>>
>>>> Regards
>>>>
>>>> Frustrated John
>>> What do you mean by an out of scope address? Is the laptop being
>>> connected to your LAN while it's got an IP address assigned from
>>> another DHCP server (on another network)?
>>>
>>> What if the laptop is in a powered down state when connected, and
>>> then powered up after being plugged in?
>>>
>>>
>> I have been using the scope facility to restrict the lan subnet in my
>> Win 2003 Server so that DHCP clients are only able to get IP addresses
>> from a certain range. This way I can prevent (or so I thought) devices
>> from getting IP addresses that belong to devices with fixed IP
>> addresses.
>
> Do you mean exclusions? That's what I use; a range of IPs at both the
> beginning & end of the subnet are excluded from DHCP. All my static
> addresses are assigned IPs in the beginning of the range.
>
> You haven't really answered all my questions, though.
>
>
>
Exclusions yes. Scope is term used by Win Server 2003. I do the same
with my fixed addresses.

The laptop is used at home and work. Both use DHCP.
When it is plugged in at work it uses the wrong address. I don't know
whether it is the one assigned on the network at home.

After getting an IP address from the correct range you can reboot it and
it will retain the correct address.

John Gelavis <(E-Mail Removed)> wrote:
> Lanwench [MVP - Exchange] wrote:
>> John Gelavis <(E-Mail Removed)> wrote:
>>> Lanwench [MVP - Exchange] wrote:
>>>> John Gelavis <(E-Mail Removed)> wrote:
>>>>> Hello
>>>>>
>>>>> I have a client xp laptop that on connection to the lan tries to
>>>>> use an out of scope address thereby causing a conflict with
>>>>> another appliance with a fixed ip address. I have tried all the
>>>>> usual practices including commands at the prompt, eliminating all
>>>>> references to the ip address from the registry but still the
>>>>> client keeps using the same address until I do ipconfig release
>>>>> then renew (it then gets a correct address). Any suggestions
>>>>> other than a big hammer would be appreciated.
>>>>> PS DHCP server is Windows 2003 SBS
>>>>>
>>>>> Regards
>>>>>
>>>>> Frustrated John
>>>> What do you mean by an out of scope address? Is the laptop being
>>>> connected to your LAN while it's got an IP address assigned from
>>>> another DHCP server (on another network)?
>>>>
>>>> What if the laptop is in a powered down state when connected, and
>>>> then powered up after being plugged in?
>>>>
>>>>
>>> I have been using the scope facility to restrict the lan subnet in
>>> my Win 2003 Server so that DHCP clients are only able to get IP
>>> addresses from a certain range. This way I can prevent (or so I
>>> thought) devices from getting IP addresses that belong to devices
>>> with fixed IP addresses.
>>
>> Do you mean exclusions? That's what I use; a range of IPs at both the
>> beginning & end of the subnet are excluded from DHCP. All my static
>> addresses are assigned IPs in the beginning of the range.
>>
>> You haven't really answered all my questions, though.
>>
>>
>>
> Exclusions yes. Scope is term used by Win Server 2003.

Ah. Yes... but exclusions are something you set *in* the scope. If I
understand you correctly, the address you're getting is clearly in your
scope, but not in the range you've allotted for DHCP assignment by virtue
of their not being excluded.

> I do the same
> with my fixed addresses.
>
> The laptop is used at home and work. Both use DHCP.
> When it is plugged in at work it uses the wrong address. I don't know
> whether it is the one assigned on the network at home.
>
> After getting an IP address from the correct range you can reboot it
> and it will retain the correct address.

Are you using the same IP network at home (e.g., 192.168.1.0/24) as at work?
That's always going to be a problem.

Lanwench [MVP - Exchange] wrote:
> John Gelavis <(E-Mail Removed)> wrote:
>> Lanwench [MVP - Exchange] wrote:
>>> John Gelavis <(E-Mail Removed)> wrote:
>>>> Lanwench [MVP - Exchange] wrote:
>>>>> John Gelavis <(E-Mail Removed)> wrote:
>>>>>> Hello
>>>>>>
>>>>>> I have a client xp laptop that on connection to the lan tries to
>>>>>> use an out of scope address thereby causing a conflict with
>>>>>> another appliance with a fixed ip address. I have tried all the
>>>>>> usual practices including commands at the prompt, eliminating all
>>>>>> references to the ip address from the registry but still the
>>>>>> client keeps using the same address until I do ipconfig release
>>>>>> then renew (it then gets a correct address). Any suggestions
>>>>>> other than a big hammer would be appreciated.
>>>>>> PS DHCP server is Windows 2003 SBS
>>>>>>
>>>>>> Regards
>>>>>>
>>>>>> Frustrated John
>>>>> What do you mean by an out of scope address? Is the laptop being
>>>>> connected to your LAN while it's got an IP address assigned from
>>>>> another DHCP server (on another network)?
>>>>>
>>>>> What if the laptop is in a powered down state when connected, and
>>>>> then powered up after being plugged in?
>>>>>
>>>>>
>>>> I have been using the scope facility to restrict the lan subnet in
>>>> my Win 2003 Server so that DHCP clients are only able to get IP
>>>> addresses from a certain range. This way I can prevent (or so I
>>>> thought) devices from getting IP addresses that belong to devices
>>>> with fixed IP addresses.
>>> Do you mean exclusions? That's what I use; a range of IPs at both the
>>> beginning & end of the subnet are excluded from DHCP. All my static
>>> addresses are assigned IPs in the beginning of the range.
>>>
>>> You haven't really answered all my questions, though.
>>>
>>>
>>>
>> Exclusions yes. Scope is term used by Win Server 2003.
>
> Ah. Yes... but exclusions are something you set *in* the scope. If I
> understand you correctly, the address you're getting is clearly in your
> scope, but not in the range you've allotted for DHCP assignment by virtue
> of their not being excluded.
No they are excluded. That's the bit I don't get. If they are excluded
how can this client get a lease for it?
>
>> I do the same
>> with my fixed addresses.
>>
>> The laptop is used at home and work. Both use DHCP.
>> When it is plugged in at work it uses the wrong address. I don't know
>> whether it is the one assigned on the network at home.
>>
>> After getting an IP address from the correct range you can reboot it
>> and it will retain the correct address.
>
> Are you using the same IP network at home (e.g., 192.168.1.0/24) as at work?
> That's always going to be a problem.
>
>

I think that is the problem. It's not my laptop otherwise I would have
changed the home network as a method of avoiding this clash. I might
have to do a housecall to fix this eh.

John Gelavis wrote:
> Lanwench [MVP - Exchange] wrote:
>> John Gelavis <(E-Mail Removed)> wrote:
>>> Lanwench [MVP - Exchange] wrote:
>>>> John Gelavis <(E-Mail Removed)> wrote:
>>>>> Lanwench [MVP - Exchange] wrote:
>>>>>> John Gelavis <(E-Mail Removed)> wrote:
>>>>>>> Hello
>>>>>>>
>>>>>>> I have a client xp laptop that on connection to the lan tries to
>>>>>>> use an out of scope address thereby causing a conflict with
>>>>>>> another appliance with a fixed ip address. I have tried all the
>>>>>>> usual practices including commands at the prompt, eliminating all
>>>>>>> references to the ip address from the registry but still the
>>>>>>> client keeps using the same address until I do ipconfig release
>>>>>>> then renew (it then gets a correct address). Any suggestions
>>>>>>> other than a big hammer would be appreciated.
>>>>>>> PS DHCP server is Windows 2003 SBS
>>>>>>>
>>>>>>> Regards
>>>>>>>
>>>>>>> Frustrated John
>>>>>> What do you mean by an out of scope address? Is the laptop being
>>>>>> connected to your LAN while it's got an IP address assigned from
>>>>>> another DHCP server (on another network)?
>>>>>>
>>>>>> What if the laptop is in a powered down state when connected, and
>>>>>> then powered up after being plugged in?
>>>>>>
>>>>>>
>>>>> I have been using the scope facility to restrict the lan subnet in
>>>>> my Win 2003 Server so that DHCP clients are only able to get IP
>>>>> addresses from a certain range. This way I can prevent (or so I
>>>>> thought) devices from getting IP addresses that belong to devices
>>>>> with fixed IP addresses.
>>>> Do you mean exclusions? That's what I use; a range of IPs at both the
>>>> beginning & end of the subnet are excluded from DHCP. All my static
>>>> addresses are assigned IPs in the beginning of the range.
>>>>
>>>> You haven't really answered all my questions, though.
>>>>
>>>>
>>>>
>>> Exclusions yes. Scope is term used by Win Server 2003.
>>
>> Ah. Yes... but exclusions are something you set *in* the scope. If I
>> understand you correctly, the address you're getting is clearly in
>> your scope, but not in the range you've allotted for DHCP assignment
>> by virtue of their not being excluded.
> No they are excluded. That's the bit I don't get. If they are excluded
> how can this client get a lease for it?
>>
>>> I do the same
>>> with my fixed addresses.
>>>
>>> The laptop is used at home and work. Both use DHCP.
>>> When it is plugged in at work it uses the wrong address. I don't know
>>> whether it is the one assigned on the network at home.
>>>
>>> After getting an IP address from the correct range you can reboot it
>>> and it will retain the correct address.
>>
>> Are you using the same IP network at home (e.g., 192.168.1.0/24) as at
>> work? That's always going to be a problem.
>>
>>
>
> I think that is the problem. It's not my laptop otherwise I would have
> changed the home network as a method of avoiding this clash. I might
> have to do a housecall to fix this eh.

I have solved this issue by re-configuring the home network of the
client machine to exclude the lan addresses from the dhcp pool. Seems
like a quick and dirty method to fix something that the OS of the client
machine should not have been doing, but hey it's MS Windows. Thanks to
those who responded for your help.

John Gelavis <(E-Mail Removed)> wrote:
> John Gelavis wrote:
>> Lanwench [MVP - Exchange] wrote:
>>> John Gelavis <(E-Mail Removed)> wrote:
>>>> Lanwench [MVP - Exchange] wrote:
>>>>> John Gelavis <(E-Mail Removed)> wrote:
>>>>>> Lanwench [MVP - Exchange] wrote:
>>>>>>> John Gelavis <(E-Mail Removed)> wrote:
>>>>>>>> Hello
>>>>>>>>
>>>>>>>> I have a client xp laptop that on connection to the lan tries
>>>>>>>> to use an out of scope address thereby causing a conflict with
>>>>>>>> another appliance with a fixed ip address. I have tried all the
>>>>>>>> usual practices including commands at the prompt, eliminating
>>>>>>>> all references to the ip address from the registry but still
>>>>>>>> the client keeps using the same address until I do ipconfig
>>>>>>>> release then renew (it then gets a correct address). Any
>>>>>>>> suggestions other than a big hammer would be appreciated.
>>>>>>>> PS DHCP server is Windows 2003 SBS
>>>>>>>>
>>>>>>>> Regards
>>>>>>>>
>>>>>>>> Frustrated John
>>>>>>> What do you mean by an out of scope address? Is the laptop being
>>>>>>> connected to your LAN while it's got an IP address assigned from
>>>>>>> another DHCP server (on another network)?
>>>>>>>
>>>>>>> What if the laptop is in a powered down state when connected,
>>>>>>> and then powered up after being plugged in?
>>>>>>>
>>>>>>>
>>>>>> I have been using the scope facility to restrict the lan subnet
>>>>>> in my Win 2003 Server so that DHCP clients are only able to get
>>>>>> IP addresses from a certain range. This way I can prevent (or so
>>>>>> I thought) devices from getting IP addresses that belong to
>>>>>> devices with fixed IP addresses.
>>>>> Do you mean exclusions? That's what I use; a range of IPs at both
>>>>> the beginning & end of the subnet are excluded from DHCP. All my
>>>>> static addresses are assigned IPs in the beginning of the range.
>>>>>
>>>>> You haven't really answered all my questions, though.
>>>>>
>>>>>
>>>>>
>>>> Exclusions yes. Scope is term used by Win Server 2003.
>>>
>>> Ah. Yes... but exclusions are something you set *in* the scope. If I
>>> understand you correctly, the address you're getting is clearly in
>>> your scope, but not in the range you've allotted for DHCP
>>> assignment by virtue of their not being excluded.
>> No they are excluded. That's the bit I don't get. If they are
>> excluded how can this client get a lease for it?
>>>
>>>> I do the same
>>>> with my fixed addresses.
>>>>
>>>> The laptop is used at home and work. Both use DHCP.
>>>> When it is plugged in at work it uses the wrong address. I don't
>>>> know whether it is the one assigned on the network at home.
>>>>
>>>> After getting an IP address from the correct range you can reboot
>>>> it and it will retain the correct address.
>>>
>>> Are you using the same IP network at home (e.g., 192.168.1.0/24) as
>>> at work? That's always going to be a problem.
>>>
>>>
>>
>> I think that is the problem. It's not my laptop otherwise I would
>> have changed the home network as a method of avoiding this clash. I
>> might have to do a housecall to fix this eh.
>
> I have solved this issue by re-configuring the home network of the
> client machine to exclude the lan addresses from the dhcp pool.

Why not change it entirely, to something else?? That way the client would
always go get another address. Or change the one you use at work. If you're
using something really generic, odds are very good that this problem will
happen with others - and anyone using the same IP network & trying to VPN in
won't be able to do so.

On my clients' networks, I always use a less commonly encountered private
network - such as 172.16.x.x/24.


> Seems
> like a quick and dirty method to fix something that the OS of the
> client machine should not have been doing, but hey it's MS Windows.

Actually, it's not just a Windows thing. It's how DHCP works.

> Thanks to those who responded for your help.