Interesting.. Just received a NVG 510 from eBay and it also failed authentication on first startup. After a few minutes, it started a firmware updated and rebooted itself. Then it was able to connect. I wonder why the 2210-02-1ATT wasn’t built with this fail-back mechanism.
If you want to save yourself the trouble of hacking your way into the 2210-02 to simply get your modem online due to AT&T’s foolishness, you can just update your modem using this firmware file. It was downloaded directly from AT&T’s server, and a few people have told me it works. Use at your own risk, though!
nta787r27_attsw.bin MD5 (nta787r27_attsw.bin) = 715b2b5d3071731fffbb91ca686a5377
Installing new 802.1x certificates on the 2210-02 is amazingly simple. Due to poor planning by AT&T, the 2210-02 ADSL2+ may have old certificates that prevent it from getting online. Instead of releasing a firmware file to update the certificates, they basically said screw you. For some background, check out this post.
For some backstory, check out this post. To summarize, AT&T’s security cert expired. Without it, you cannot sync your modem. They could easily release the firmware update binary file to allow users to connect, but they won’t. (insert name calling here)
This policy motivated me to get my 2210 online at any cost. And now I’m documenting all my results so anybody else can also get their older 2210s online.
So I recently signed up for AT&T’s “U-Verse Internet”, which is just rebranded ADSL2+ that uses IP-DSLAM instead of the older ATM/PPPoE setup. For $15 less than TWC’s 10/1 package, I get 11.2Mbps/0.92Mbps. Not bad.