@Virgo Thanks for your response.  Yes, both the AP and controller are hardwired through a PoE switch to the main router and I can access both via their IP address on the LAN.  As well both can access the internet just fine (they performed upgrades and downloaded their firmware from the TPlink site)

I am back at it this week.  So, I can verify that the OC200 and the EAP245 both have network access, I can access both on the wired network.  I can also plug my computer into ETH2 of the EAP245, and it is able to get an IP address and use the network (though I presume it's a hardware switch inside the device).

So the issue seems to be that AP is not forwarding packets to the router when connected to it wirelessly.  The clients associate, but don't get a DHCP address.  Even configuring the client to use a static IP address on the same network, the packets still don't make it to the router.    This AP is controlled by the OC200 controller.  Yet I don't see any settings for the controller or AP (accessing the controller web UI) for configuring gateway etc.

UPDATE:  I factory reset the EAP245, and using a very basic configuration I was able to connect a wireless client and everything operated as expected - the client was able to acquire an IP address and use the network.  So it's definitely something wrong when the AP is imported into the controller.

  @dolhop 

LAN settings on the controller are under admin, wired networks, LAN.   In there make sure its on the same subnet as the router

What is the addresses you are using and what subnet?     I have set this up many times before with just an OC200 an APs, it should work easy.

If you can list the IPs you are getting / have set presently we may be able to spot something.     For example

Router 192.168.1.1

OC200 192.168.1.10

AP1 192.168.1.11 etc etc 

Can you see the AP and OC200 as clients on your router DHCP logs?  what about the devices?   do they appear there and not get an dhcp OR not appear at all?