Hi @dsmith5428,

I would have assumed that a hardware reset should reset the AP local admin password back to admin/admin as you described.  But if you changed it, see if you can change it back from the admin website of the EAP (assuming you can log in).  Also try doing a software reset while you're logged in.

Which Omada are you using?  Software or OC-200?

Some things to try:

1) Make sure Omada is updated to current version

https://www.tp-link.com/us/support/download/eap225/#Controller_Software

2) Make sure EAP is updated to current version

https://www.tp-link.com/us/support/download/eap225/#Firmware

3) Try the EAP Discovery tool:

https://www.tp-link.com/us/support/download/eap225/#EAP_Discovery_Tool

Here are some related documents:

https://www.tp-link.com/us/configuration-guides/introduction-of-eap-adoption/?configurationId=22336#maintaining_2_3

https://www.tp-link.com/us/configuration-guides/quick_start_guide_standalone_eap/?configurationId=18701#_idTextAnchor003

How many EAP do you have?  If only one, you don't have to use the Omada management application.  Even if more than one, you only _need_ Omada if you want fast roaming and / or wireless MESH.  Granted, it's nice to have in any case.

-Jonathan

Hi @dsmith5428,

What is the IP address of your gateway?  Is your subnet 192.168.0.x? 

Is it possible your local subnet is different from the one the EAP is trying to use?  E.g. 192.168.1.x?  Is the EAP failing to lead an IP address from your DHCP server (which is probably part of your router?)

This would explain why the EAP cannot "talk" on your home network.  And why wireless clients are assocated with the EAP cannot get to the network/internet.

-Jonathan

Similarly, double check your subnet masks.  These should all be 255.255.255.0.  But if DHCP is working properly, the EAP should get all of this info from the DHCP server/service -- assuming your router is set correctly.

Hi @dsmith5428,

Well that's your problem.  All devices connected to a non-VLAN'ed switch (Layer2) need to be configured for the same subnet in order to talk with each other.  So 192.168.100.x  Unless the "zero" you mentioned before (192.168.0.x) was a typo.

1) Make sure the EAP is configured for DHCP (or set it manually to a free IP on the correct subnet)

2) Check/replace the cable (the leading cause of link negotiation failures)

3) Ensure the DHCP server on your router is set to support enough clients (e.g 50 or 100 or so) depending on how many devices you have on your network.

-Jonathan