Quantcast
Channel: CenturyLink forum - dslreports.com
Viewing all articles
Browse latest Browse all 4880

CenturyLink ZyXEL 2100z not activating

$
0
0
Sorry in advance for lengthy post, just want to put all the info out there. I recently had a tech come out and upgrade my CL DSL Lines to 80/10 speeds. When he did that he took away my old single line DSL ZyXEL router and replaced it with an Actiontec modem/router. This activated fine and delivered internet. However, the wireless speeds were less than half of which were being delivered via Ethernet (about 23Mbps...). Having had bad luck with Actiontec, i demanded a different brand be sent to me. CL then sent me an ZyXEL C2100z (which supports the two DSL line). I could not get this modem/router to obtain solid green DSL lights. They continued to flash, would sometimes go red, but would never go solid green. I troubleshooted with several power cycles, hard resets, manually entering my PPP username/PW, no luck. CL was convinced it was a bad modem. So they sent me a technicolor modem. This worked fine, however....back to the original issue, wireless speeds are terrible (compared to what i should be getting). So, i figured i would ask for a replacement ZyXEL C2100z since it has the ability to have the 5ghz wireless. Once i got my replacement, i have the same exact issues as the other ZyXEL c2100z, tried the same troubleshooting with no luck. As of right now i have the technicolor back on the network as a temp solution, but i really want this ZyXEL to work so i can be on 5ghz instead of the 2.4. Anyone have any solutions to this? As of now, CL is chalking this up to a bad modem AGAIN. However, i am not convinced. I think there may be some setting issues with this modem straight from CL or something. I have confirmed with CL that the ZyXEL C2100z is a compatible modem/router on my VDSL2 80/10 internet. Any help would be appreciated.

Viewing all articles
Browse latest Browse all 4880

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>