Wireless doesn't coect to internet, but can coect when using wired coection

Recently I have been having trouble coecting to the inteet using wireless, but I am able to coect via a wired coection. I'm using a TP-Link Archer C7 wireless router as an access point, and it has been working fine for around 3 months without requiring a reset. Recently I have been unable to coect when using this wireless coection, and i'm a bit puzzled as to what the cause is. DHCP and DNS servers are hosted locally, but I have not been able to find any indication of a cause for my lack of coection. I have restarted the DHCP and DNS servers on both domain controllers in the network, but I have noticed no difference as a result. Additionally I have factory reset the router, and configured it from scratch with no luck. When I set up the router I disabled DHCP, firewall, nat, and any forwarding inside the Archer C7 router. What I find most interesting is that if I coect via Etheet to the Archer C7 I am instantly able to coect to the inteet, and achieve great download/upload speeds. However any attempts to coect to the inteet while using wifi have proven to be futile. As a test I removed the Archer C7 router from the network, tued it off to prevent any possible wireless interference, and configured a second router as an access point with similar configurations from the first. Still, I was unable to coect to the inteet. I have also tried to remove the security on the wireless with no distinguishable effect. Sometimes when I attempt to coect to the wireless network DHCP works properly and assigns the correct information, as detailed below. Yet other attempts to coect to wireless produce network information with an IP begiing with 169, and a subnet of 255.255.0.0, which to me suggests that the router is unable to reach the DHCP server to provision the correct information. I am able to ping from the Archer C7 to the main router, and from the Archer C7 to the DNS/DHCP servers with no packet loss. Any device that is coected to the wireless network experiences severe (40% - 80%) packet loss when attempting to ping the router (192.168.1.1) or DNS/DHCP servers (192.168.1.11,192.168.1.12). Also as a note I have attempted to manually set the network information, but am still not able to access the inteet. I have tried to set the DNS servers to 8.8.8.8 in the network information of the coected wireless device with no luck. I set the DHCP server in the archer C7 router within my IP scheme, but encompassing IP's that are excluded. That also did not produce any changes, but it was interesting to note that any devices coected to the archer C7 were assigned an IP address within the scope of the domain DHCP servers, rather than utilizing the DHCP server present within the archer C7. Wireless devices utilized the DHCP serer in the archer C7, however it didn't seem to make any difference. I have also tried to move the Archer C7 to utilize a different Etheet port, and changed the Etheet cable that was being used. Network information of a device coected to wireless has been provided below. Any ideas of what the possible cause of this newly arisen behavior that prevents me from accessing the inteet while on wireless? Let me know if I can provide any additional information, and thank you for trying to help.

Network information (Coected to wireless): IP: 192.168.1.22 Subnet: 255.255.255.0 Router: 192.168.1.1 DNS: 192.168.1.11, 192.168.1.12

Network information (Actual addresses): Router: 192.168.1.1 Subnet: 255.255.255.0 DNS: 192.168.1.11, 192.168.1.12 Archer C7: 192.168.1.239

I have been searching for a few days for the solution to this problem, and I have included some links below to two other posts I have read that were not able to solve the problem I am experiencing. I have read many more, but I am only allowed to post two links.

https://forums.techguy.org/threads/solved-wired-coection-works-but-not-wireless.1083408/

http://www.tomshardware.com/answers/id-1946566/laptop-coection-shows-coected-access-inteet-application.html