Frontier DSL & DM200 Modem Issues

[conway1990]

So, I have DSL through Frontier (Their highest tier, yet biggest joke of a plan: Business Extreme) and my biggest issue right now is not speed, but the number of users that can use the service. Once we surpass six devices, the modem/router has a mental breakdown and freezes up until a restart. #HowDoesThisQualifyAsABusinessOffering 

Anyway, I thought I would upgrade our system so I went out and splurged on a $60 DSL Modem (DM200) and thought I would pair a totally cool Unifi system with it. Now, I have setup quite a few systems before, though I am certainly no expert. Well, I could not figure out how to use the DM200 with Frontier, and neither could Netgear phone support. Legit just spent 8 hours on this. And, to make things worse, the property is in a remote location so I do not have cell service. Therefore, I have a hard time talking to Support WHILE on the phone that uses wifi. 

So, does anyone have ANY experience with Frontier's DSL offering? Any suggestions? I have the PPPoE username / password and VPI/VCI, and have quadrupal checked with four different Frontier reps. Still, no dice. Just when I thought it couldn't get any worse than Comcast and Verizon, it has. Much worse. 

Anyway, thanks so much in advance for all of your help!!

[antinode]

> So, does anyone have ANY experience with Frontier's DSL offering?

   Not I, but...

> Any suggestions?

   One, perhaps.

> I have the PPPoE username / password and VPI/VCI, and  have quadrupal
> checked with four different Frontier reps. Still, no dice.

   What kind of "no dice"?  Does the DSL stuff fail to link/train, or is
the failure in the DSL/PPP credentials?

   I know nothing about the DM200, but some versions of Netgear firmware
(on some kinds of hardware) fail properly to handle some special
characters in a DSL/PPP password.  The case I found involved a "<" on a
DGN2200v4 (V1.0.0.86_1.0.86).  Someone else reported here that ";"
caused trouble on his D6400 (V1.0.0.60) in the UK.  I assume that any
UNIX-shell-special character could trigger the defect.  (Or, perhaps any
HTML-special character.)  In any case, if your DSL/PPP password contains
more than alphanumeric characters, it might be worth running the
experiment.  In my case, adding a backslash escape character (in the Web
interface) worked around the problem: "abc<def" -> "abc\<def".  The
fellow with the semi-colon changed his password to remove the ";".

      https://community.netgear.com/t5/x/x/m-p/1354547