# Client launcher not finding relevant address

**URL:** <https://forum.inductiveautomation.com/t/client-launcher-not-finding-relevant-address/12487>\
**Category:** Ignition\
**Created:** [December 21, 2016, 1:20am UTC](https://forum.inductiveautomation.com/t/client-launcher-not-finding-relevant-address/12487 "2016-12-21T01:20:33Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![CamJam](https://avatars.discourse-cdn.com/v4/letter/c/3ec8ea/32.png) [@CamJam](https://forum.inductiveautomation.com/u/CamJam)\
**Post date:** [December 21, 2016, 1:20am UTC](https://forum.inductiveautomation.com/t/client-launcher-not-finding-relevant-address/12487/1 "2016-12-21T01:20:33Z")

</div>

Hi,

I am in need of some help with the client launcher. I have a windows 8 computer that gets stuck at start up. The client launcher will always look for a 169.254.5.138:8088:8034 address when the PC boots.

I have a static 192.168.57.200 address and have disabled AIPA in the registry even though its not a DHCP address.

I have flushed the DNS cache and reset the adapter.

I only have one NIC on the PC and not sure why or where Ignition is getting a 169.254.xxx.

Does anyone have a solution for something like this. I am running Ignition version 7.8.3 on the PC.

Regards,  
Cameron

---

<div class="post-metadata">

**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\
**Post date:** [December 21, 2016, 2:00pm UTC](https://forum.inductiveautomation.com/t/client-launcher-not-finding-relevant-address/12487/2 "2016-12-21T14:00:07Z")

</div>

Addresses that begin with 169.\* are fallback addresses given to a network adapter when DHCP fails – aka the “APIPA” address range. Something is wrong with your DHCP setup, most likely.

---

<div class="post-metadata">

**Author:** ![CamJam](https://avatars.discourse-cdn.com/v4/letter/c/3ec8ea/32.png) [@CamJam](https://forum.inductiveautomation.com/u/CamJam)\
**Post date:** [December 21, 2016, 7:49pm UTC](https://forum.inductiveautomation.com/t/client-launcher-not-finding-relevant-address/12487/3 "2016-12-21T19:49:44Z")

</div>

Had to disable Omron services for direct Ethernet connection to get rid of the 169.254 address and also set ArpRetryCount to 0 in the tcp/ip registry.

All seems to be fixed. 😃