DHCP and 169.254

  • Thread starter Thread starter dr
  • Start date Start date
Is 169.254 the "autoconfig" address? Sounds like you're not getting an
address assigned by DHCP, so the client PC is autoconfiguring itself to
169.254.x.x

Is your DHCP server Pingable?
 
Yes, 169.254.x.x is the (APIPA) Automatic Private IP Address range used by
Windows.

This means that a DHCP Server is not reachable via IP broadcast (which is
required by DHCP). Is the DHCP Server on your local network? If not, are
there relay agents in place to get the DHCP broadcasts out to the DHCP
Server?

-Chris
--
==============================
Chris Edson
(e-mail address removed)

This posting is provided "AS IS" with
no warranties, and confers no rights.
===============================
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

Need help understanding how ipv4 and ipv6 coexist under Windows 7 0
DHCP 1
169.254.x.y ? 4
Wireless & DCHP & 169.254. 2
Automatic Private IP Addressing (APIPA) 6
Wireless card can't reach DHCP server 3
win2k client not being able to reach dhcp server in router 2
(DHCP) consistently fails to lease an Internet Protocol (IP) 3

Back
Top