Re: Stupid windows xp client getting out of scope address

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

Lanwench [MVP - Exchange] wrote:
John Gelavis <it.admin@xxxxxxxxxxxxxxxx> wrote:
Lanwench [MVP - Exchange] wrote:
John Gelavis <it.admin@xxxxxxxxxxxxxxxx> wrote:
Lanwench [MVP - Exchange] wrote:
John Gelavis <it.admin@xxxxxxxxxxxxxxxx> 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.
.

Relevant Pages

  • Re: Stupid windows xp client getting out of scope address
    ... I have a client xp laptop that on connection to the lan tries to ... PS DHCP server is Windows 2003 SBS ... What do you mean by an out of scope address? ...
    (microsoft.public.windows.server.networking)
  • Re: Stupid windows xp client getting out of scope address
    ... I have a client xp laptop that on connection to the lan tries to use ... PS DHCP server is Windows 2003 SBS ... What do you mean by an out of scope address? ...
    (microsoft.public.windows.server.networking)
  • Re: Stupid windows xp client getting out of scope address
    ... I have a client xp laptop that on connection to the lan tries ... What do you mean by an out of scope address? ... know whether it is the one assigned on the network at home. ...
    (microsoft.public.windows.server.networking)
  • Re: NAP mit DHCP einsetzen mit einem Windows 2008 Server
    ... Ich glaube nur mit einem Scope Bereich und mit angegeben Wartungsservern ... bei der DHCP Erzwingung wird dem nicht kompatiblen Computer eine /32 Adresse ... Wenn auf das SSoH dann ein SoHR kommt sollte der Client auch compliant sein ...
    (microsoft.public.de.security.netzwerk.sicherheit)
  • Re: 2nd post: Unable to connect clients through SBS DHCP server
    ... Are your clients not getting a DHCP address or even after getting it they ... > Okay, I thought I was going to be ready to run with the> info provided to me in previous thread, but> I still can't get the SBS DHCP server to work for me. ... > Instead of using the 192.168.16.1:254 scope, ... obviously I have no client connections. ...
    (microsoft.public.windows.server.sbs)