DHCP doesn't work anymore after SP2

[Graham Charles]

Hey,

Sometime after XPSP2 installation, my wired AND wireless network adapters
will no longer retrieve an address; the adapter status constantly shows
"Acquiring Network Address." Assigning fixed IPs to these adapters makes
them work fine. I've tried different adapters, and they show the same
problem, so I'm thinking it's not related to the specific network hardware.

Any thoughts?

Thanks,

g.

[WTC]

Related to the DHCP server. DHCP server not assinging you a IP address
address, so your machine
sign you an address of 169.254.XXX.XXX. It is called APIPA (Automatic
Private IP Addressing).

William


"Graham Charles" > wrote in message
...
> Hey,
>
> Sometime after XPSP2 installation, my wired AND wireless network adapters
> will no longer retrieve an address; the adapter status constantly shows
> "Acquiring Network Address." Assigning fixed IPs to these adapters makes
> them work fine. I've tried different adapters, and they show the same
> problem, so I'm thinking it's not related to the specific network
> hardware.
>
> Any thoughts?
>
> Thanks,
>
> g.
>
>

[Graham Charles]

Thanks for trying, but as I understand, if that were really the case, the
adapter would report "limited connectivity," which it does not... I never
get an IP address, APIPA nor DHCP. IPCONFIG confirms this.

The DHCP server correctly assigns the other 5 machines on the network, and
nothing in its configuration changed; this machine is the only variable.

g.


"WTC" > wrote in message
...
> Related to the DHCP server. DHCP server not assinging you a IP address
> address, so your machine
> sign you an address of 169.254.XXX.XXX. It is called APIPA (Automatic
> Private IP Addressing).
>
> William
>
>
> "Graham Charles" > wrote in message
> ...
> > Hey,
> >
> > Sometime after XPSP2 installation, my wired AND wireless network
adapters
> > will no longer retrieve an address; the adapter status constantly shows
> > "Acquiring Network Address." Assigning fixed IPs to these adapters makes
> > them work fine. I've tried different adapters, and they show the same
> > problem, so I'm thinking it's not related to the specific network
> > hardware.
> >
> > Any thoughts?
> >
> > Thanks,
> >
> > g.
> >
> >
>
>

[Alex Nichol]

Graham Charles wrote:

>Thanks for trying, but as I understand, if that were really the case, the
>adapter would report "limited connectivity," which it does not... I never
>get an IP address, APIPA nor DHCP. IPCONFIG confirms this.

What shows if you right click the connection in Network Connections,
Properties, highlight TCP/IP and take Properties. That can (and usually
is) set to obtain DNS (and IP address) Automatically, but might have got
changed to 'use the following' without anything actually set there


--
Alex Nichol MS MVP (Windows Technologies)
Bournemouth, U.K. (remove the D8 bit)

[Graham Charles]

"Alex Nichol" > wrote in message
...
> What shows if you right click the connection in Network Connections,
> Properties, highlight TCP/IP and take Properties. That can (and usually
> is) set to obtain DNS (and IP address) Automatically, but might have got
> changed to 'use the following' without anything actually set there
>


No, that was fine... all settings were as they should be. MS decided this
was hardware failure, predictably.

Oh, well.

g.