New Issue with TP Link Router Not connecting to Modem

My 6 month old TP Link Router just stopped being connected to the internet. When I plug the ethernet cable directly from the modem (not modem/router) I have a connection. Cycled modem and Reset router and started over. Went into router and at IP address it just freezes on "Connecting" .

Called TP Link service and they said "Excede pushed a firmware update and it is not providing an IP address to the router. They have had many calls on this and am working with Excede to resolve the problem." Has anyone else had this problem? Is it the modem or router? I do not have another router to swap out for a test. Help!

If a combination modem/router (not sure about the even newer one for Viasat-2), most TP Link routers default to an IP address that conflicts with the Viasat device's default IP address.

If wanting to use the TP Link as a router extending the Viasat router functionality you must explicitly configure the TP Link device to avoid the IP address conflict as well as utilize a seperate IP address range for its DHCP server functionality.

It is just the modem with no router for 12Mbps service. I got it about 6 months ago when I became a new Excede subscriber. My existing D Link router would not work with it so I went out an bought this TP Link. It has worked flawless until Friday. Now I can't get it to connect.

As stated in the original text (possibly not clearly), the first thing I did was reset the modem using the small button in the back. It made no difference other than resetting my passwords, etc. Thanks,

Thanks for the given information i am following this site everyday i found this very helpful. Recently i found some error message in my MS paint tool i am using this drawing tool from many years but i never faced this kind of issues before. i was trying to solve this problem by own but i was unable to solve it then i contact this website.https://babasupport.org/microsoft/paint-customer-service/500

So it doesn't sound like a New Issue with all TP Link Routers that was created when Excede pushed a firmware update or I would have gotten a lot more response from people with similar issues.

I am guessing it is ether a hardware problem with my modem or just an incompatibility issue? I will test my modem on another router (my daughters DSL) and see if it works. I will also borrow another router and see if works with the Excede modem. Between the two, I should be able to isolate the problem.

You are right, this is what I was told when my 3 week old tp router quit, I couldnt fix it and after 2 hours support couldnt fix it. The update killed tp link routers , i went and paid for a netgear 1750
And it has been fine ever since! Anyone need a tp link router? Kidding. Lol

I did not and TP Link customer service did not check. They just said is was a know Excede issue that was being worked on. I did check and there is a later version available so I will install it when I get home tonight. Thanks for the suggestion.

I only had my Tp-link router 3 weeks, it stopped dead overnight! Tplink support was great! They tried everthing . It never worked even on wired connections
. Called viasat, they recommended a netgear router with there equipment.
I forked out 120 bucks for a good one. No regrets! Plugged it in and it works beautifully!

My TP Link router did the same. It worked the first day then crapped out. I had an old Asus 100 Mbps router in the garage attic. It worked fine I purchased a new iAsus which works but not all the time. It will work then just quit like the TP Link. . The old one.... It always works.

Greg, it may work for a while, but the IP address will change in the modem at a later date, it periodically will do that, and then you will have problems connecting. The setting for Viasat must be Dynamic IP address.

I believe Greg is referring to the his router's DHCP server which assigns IP addresses for his local/home network (and not the public IP address assigned by Viasat). I actually had to do this on my home network due to an old networked HP printer that can/could only be addressed by its local IP address for whatever reason. When the dynamic IP address changed I couldn't access the printer. while doing that, I simply assigned static local IP address to all of my devices and limited the allowed IP address range to those for my known devices (FWIW - paranoia strikes deep, into your life it will creep).