<div>
You need to specify a DHCP relay agent or IP Helper object in the VLAN configuration.<br />
<br />
-saige-
</div>


<div>
169.254.x.y are <a href="http://www.pcmag.com/encyclopedia/term/37858/apipa" rel="ugc">APIPA</a> addresses and are assigned to DHCP clients when a DHCP server cannot be contacted. &nbsp;I'm guessing your VLAN does not have a <a href="https://technet.microsoft.com/en-us/library/dd469685.aspx?f=255&MSPPError=-2147217396" rel="ugc">DHCP Relay Agent</a> to forward DHCP requests from the client to the server.
</div>


<div>
I cannot use the DHCP Relay Agent component on a computer that is running the DHCP service
</div>


<div>
What switch are you using. &nbsp;The link supplied is for using a DHCP relay agent for RRAS configuration.<br />
<br />
There should be a similar setting in the switch's vlan configuration for assigning a relay agent or helper ip address.<br />
<br />
-saige-
</div>


<div>
&quot;<i>I cannot use the DHCP Relay Agent component on a computer that is running the DHCP service</i>&quot;<br />
You wouldn't have to if the DHCP Server could talk on each VLAN.
</div>


<div>
APIPA addresses are assigned when the DHCP is unavailable and the Client is setup for DHCP<br />
<br />
the client can have a static address<br />
<br />
MS OS will assign these addresses in the 169.254.x.x realm<br />
<br />
other providers have 'bought' the rest of the address space<br />
<br />
a quick test would be to plug it into another and see if you get an address<br />
<br />
that way you can narrow it down to the vLan and the switch<br />
<br />
so we can help with the switch setup if necessary - what type is it -
</div>


<div>
Particular VLAN wasn’t trunked to closet switch. As soon as VLAN was allowed on trunk, device started getting IP address.
</div>


<div>
<div class="content wysiwyg-content">
I have several vlans on switch. &nbsp;When I assign a specific port to a vlan and connect a device, I pull a 169.x.x.x address instead of an address in the scope of that vlan. &nbsp;All other vlans on the switch pull proper addresses.
</div>
</div>


I have several vlans on switch.  When I assign a specific port to a vlan and connect a device, I pull a 169.x.x.x address instead of an address in the scope of that vlan.  All other vlans on the switch pull proper addresses.

169.x.x.x ip address

A switch is a device that filters and forwards packets of data between LAN segments. Switches operate at the data link layer or the network layer of the Open Systems Interconnection (OSI) Reference Model and therefore support any packet protocol. LANs that use switches to join segments are called switched LANs or, in the case of Ethernet networks, switched Ethernet LANs. A hub is a connection point for devices in a network. Hubs are commonly used to connect segments of a LAN. A hub contains multiple ports; when a packet arrives at one port, it is copied to the other ports so that all segments of the LAN can see all packets.

Switches / Hubs

Transmission Control Protocol/Internet Protocol (TCP/IP) is the set of networking protocols that define end-to-end connectivity specifying how data should be packeted, addressed, transmitted, routed and received at the destination. This functionality is organized into four abstraction layers which are used to sort all related protocols according to the scope of networking involved.

TCP/IP

The Dynamic Host Configuration Protocol (DHCP) is an auto configuration protocol used on IP networks and an extension of the Bootstrap Protocol. DHCP allows for computers to be configured automatically to communicate with each other over an IP network without the need for manual setup by a network administrator. The implementation of DHCP relies on a DHCP server to hand out network configuration information to DHCP-capable clients that request an IP address (and other information required or useful in communicating with other devices on an IP network). In addition to an IP address, common configuration information served over DHCP includes a default gateway, subnet mask and DNS sever(s).