You should not have that much trouble setting it up. I would try a factory reset, change as little as possible (use quick start guide) and retest. If using WIFI, use different SSIDs. If it still fails, it sounds to me like you got a defective router and needs to be replaced.

@Leathers 

 

The D-Link looks to be a typical router so the A8 should be working like the D-Link.

 

I would do a factory reset on the A8, have the Ethernet connection from its WAN to your modem. See if the internet light on the A8 is showing as amber which indicates it sees something connected.

 

I would then reach out to the ISP and tell them the modem is not recognizing the new router.

 

Before you do all that, you can test to see if it is the case of the modem not recognizing the new router by connecting your D-Link back and see if that works.

One other thought. Check to see if you are getting an IP address on the LAN as that may be the issue. If it is zero that is your issue.

@ArcherC8 

 

Honestly, I had thought of the Factory Reset with minimal setup (using the Quick-Start Guide) as well, and after trying it, there was still no connection to the Net.

 

I've been using my desktop computer and the web setup as that method is more familiar to me. (TBH, apps [to me] don't seem like a stable platform for things like interacting with routers, access points, and the like) I do have the Tether app, but that didn't work any more than the other methods I tried.

 

Just for shits and giggles, I tried again upon returning home from work today. Sadly, no joy.  I had thought about downgrading to the original firmware (I saved a copy before upgrading) but I don't believe that's going to make any difference. One thing I failed to mention in my original post, the 'Internet' connection on the router always stays a solid amber.  So in accordance with what @Tony posted in his reply, the modem IS seeing the router, but the router is unable to understand how to connect to the Net.  

 

I most definitely feel like I'm running around in circles.  The Archer won't connect to the modem, but when I use the same cable on the old router (the D-Link) everything works as it has been.  I'm more and more thinking there's something not connected inside the router, but I don't want to crack the case and go looking for fear of voiding my warranty.  If it was a loose wire, that would be an easy fix.

 

Anyway, I appreciate your taking the time to give me a hand.

 

One other thought. Check to see if you are getting an IP address on the LAN as that may be the issue. If it is zero that is your issue.

 

In the LAN section of the router Advanced page, I am getting the 192.168.0.1 address as well as the correct subnet mask of 255.255.255.0

 

However, this is what I'm getting on the Status portion.  It never changes from saying 'Connecting' at the top.

 

Internet

Status:

Connecting

Internet Connection Type:

Dynamic IP

IP Address:

0.0.0.0

Subnet Mask:

0.0.0.0

Default Gateway:

0.0.0.0

Primary DNS:

0.0.0.0

Secondary DNS:

0.0.0.0

 

At this point, I'm definitely leaning toward the defective router option.  It's about the only thing that makes sense.

@Tony 

 

If D-Link hadn't ceased supporting the 868-L, I probably would still be using it.  But it's 6 years old, there are better options in the marketplace, so here we are.

 

As I mentioned to @ArcherC8 before shutting down yesterday, and actually before posting my message, I had done a Factory Reset and did a minimal setup with the Quick guide that had come with the unit.  Didn't work.  Again as I mentioned in the last message I just posted, I did it again this evening, and just now before writing this message.  Steady Amber light from the Internet connection, and all zeros except for the LAN IP address and subnet mask.  I even tried manually inputting the Primary and Secondary DNS addresses from my ISP.  Didn't work.

 

I called my ISP, but they couldn't offer anything other than to wish me luck.  There's no problem on their end, and I can prove that because I'm right now connected to the D-Link router, and am connected to the 'Net as always.  When I'm connected to the Archer, bupkus.

 

I appreciate your efforts, but I'm increasingly believing this to be a hardware boondoggle.  If I wasn't concerned about the warranty, I'd crack open the case and start looking for loose wires.  But I didn't win either Powerball or Mega Millions this weekend, so money is still an issue.

@Leathers 

 

Follow the steps in the post "My new router is not obtaining an IP address from my cable modem" which is about the tenth entry in the posts.

 

 I should have said WAN IP address in my prior post.

@ArcherC8 

 

I actually stumbled upon that solution suggestion a day or so ago, gave it a try and didn't get a positive result.  I did attempt to fiddle with the settings, changing it from a default of a router to the Access Point option.  The light on the Internet connection did change from Orange to Green, but it was a ruse.  The device wasn't online, it was merely attempting to do what the function of the AP is designed for.  Once I changed it back to Router, I was back on Orange again.

 

I think I've done all I can do here.  I'm going to contact Amazon and see about getting a replacement.  I'm not soured on TP-Link products, I'm going to see if I can get just another router and perhaps this one was just plain defective.  At any rate, as I said before, I'm grateful for you and @Tony taking the time to assist me with my issue.   Thanks.

I had that issue after I did a factory reset and had to perform it several times. I unplugged the modem and router for several minutes to ensure the capacitors would drain (I shut off my UPS that supplied power to both) and that seamed to work. As far as Amazon goes, just go to your Amazon "orders" and you can start the return process.

It makes sense that that would (normally) work. In other situations, hardware does seem to have a 'lagging memory' capacity, and shutting things off for a time will allow it to 'forget' where it was connected to. I was hopeful this was going to be the solution but disconnecting both the power coupling AND the fiber line (actually opening the modem to disconnect the line physically from it, which by the way you're NOT supposed to do) didn't seem to make any difference.

 

At least I know how to disconnect the fiber line now since I need to move the modem to a more central location in the house, to better facilitate Wi-Fi here (our modem and router are at one end of the house and it's a bad situation for the remainder of the house in terms of Wi-Fi).

 

Amazon is really good about returns. Almost too good. While they ask for a reason, I honestly don't think they read them. I've seen videos on YouTube showing people buying those pallets of returns from Amazon, and it's amazing what people send back. Some things are completely destroyed, others are unopened. It can be pretty bizarre to watch. Anyway, thanks again.

@Leathers 

 

If you are getting 0s, I am pretty sure the issue is that your modem is only bound to your D-Link router. 

 

I am assuming your modem is a cable modem, and if so, the ISP will be able to reset the MAC binding. This will then cause the modem to reboot, and then bind to whatever is connected. 

 

So as far as what you are able to do is the following (previous FAQs probably mentioned):

 

-Leave the TP-Link router connected to the modem and powered on, and cut the power to the modem, and turn the modem back on. After the modem has been on for several hours, see if the WAN IP has changed, refresh the page.

 

-Leave the TP-Link router connected to the modem and powered on, cut the power to the modem, unscrew the coax cable from the modem, turn the modem on. Leave the modem alone for about 5 minutes, then while the modem is on, screw the coax cable back into the modem. After a couple of minutes check the WAN IP of the router.

 

If neither above works, contact the ISP and tell them nothing is failing, you just need to reset the MAC binding. In other words, your modem will only give internet to your D-Link as it recognizes its MAC address, not of the TP-Link. If the tech does not know what you are talking about, ask to speak to a higher level one.