valid ip address

  • Thread starter Thread starter Dante
  • Start date Start date
D

Dante

I've having trouble getting a valid ip address on my
device. I keep getting a 169.254.x.x Ip Address on my
device most of the time. Once in a while, i'll get a
correct address of 192.168.0.x so it's inconsistent.
Anyone have any idea why this is?
 
Sounds like the device is configured for DHCP, right? That could indicate
that your DHCP server is out of assignable IP addresses or, for some reason,
is not responding to the device's request.

Paul T.
 
To elaborate on Paul's answer, addresses starting with 169 are AutoIP
addresses. The DHCP client in Windows CE has support for AutoIP, which is a
standard for devices assigning their own IP address. The DHCP client will
negotiate an AutoIP address when it fails to get a response (or a valid
response) from a DHCP server.

Bill
 
I've never heard of AutoIP (though that doesn't mean much). Can you point me
to any RFCs or other standards describing it? Is it a proprietary Microsoft
thing, or an emerging industry standard that I just haven't heard about?

Dave
 
An IETF draft can be found at:

http://ianzag.megasignal.com/ftp/do...draft-ietf-zeroconf-ipv4-linklocal-01-Apr.pdf

AutoIP can be turned on in the CE DHCP client via a registry value. It is
not proprietary MS and my understanding has been that it originated in the
UPnP design. MS supports it and it seems to be growing in acceptance. It's
great for small networks that don't have a DHCP/DNS server. It does leave
open an naming problem to be solved though. This is usually resolved via
some sort of broadcast/discovery mechanism.

Bill
 
Back
Top