On Wednesday, March 21, we lost our cable broadband internet connection here at the EE Daily News. Power cycling our Netgear CMD31T DOCSIS 3.0 did not help, as the modem continued a futile attempt to synch up with Comcast servers. The company's field technicians had just been out to repair cables and adjust signal strength in our neighborhood a few days earlier, so our initial assumption was that the connection failure was related to that work.
Comcast sent out a technician once again, but not until the next morning. Immediately upon his arrival, Comcast's technician informed us that he had some bad news. "Netgear CMD31T modems are not designed to work in California", he said, adding that they are only designed to work with Time Warner Cable systems. The technicians had just been informed of this in a meeting they had that morning, he said. We had installed our Netgear CMD31T more than two months earlier, and it had been connecting to Comcast just fine up till then, so what had changed?
We checked Netgear's documentation on the modem, and found that Comcast had their facts backwards. According to the CMD31T Data Sheet, all major providers except for Time Warner, are supported.
It could have been that the out-of-specification signal levels on the local cable caused the problem, perhaps resulting in damage to the modem. So, we visited our local Frys Electronics store to attempt an exchange.
"Let me guess.. Comcast. Right?"
Apparently we were not the only ones affected. These are the exact words of the Frys Return Desk staffer, immediately upon seeing our CMD31T. "We must have had twenty of these come back just yesterday, and more the day before", he said. He kindly accepted our return for store credit, however, even though we were past the normal return period.
In looking for a replacement, we learned that the Netgear cable modem was now the only cable modem that particular Frys store sells. Pretty odd, for a modem that is "not designed to work in California". Since there was no other choice, we decided to do a straight exchange for another sample of the CMD31T.
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . : sanjose.ca.sanfran.comcast.netIP Address. . . . . . . . . . . . : 184.108.40.206Subnet Mask . . . . . . . . . . . : 255.255.252.0Default Gateway . . . . . . . . . : 220.127.116.11
Upon installing our 2nd Netgear modem, we observed from the front panel lights that it very quickly established an internet connection, within minutes after startup. To check, we executed an ipconfig command from our PC, with the results shown above. Clearly, there was no electrical problem in the cabling. Nor was there any problem with the modem, dispelling Comcast's claim that they don't work on their system. The 2nd CMD31T had no problem at all seeing Comcast's servers.
Pinging google.com [18.104.22.168] with 32 bytes of data:
Reply from 22.214.171.124: bytes=32 time=91ms TTL=53Reply from 126.96.36.199: bytes=32 time=91ms TTL=53Reply from 188.8.131.52: bytes=32 time=93ms TTL=53Reply from 184.108.40.206: bytes=32 time=93ms TTL=53
Ping statistics for 220.127.116.11:Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),Approximate round trip times in milli-seconds:Minimum = 91ms, Maximum = 93ms, Average = 92ms
To confirm that we had a good connection, we pinged Google.com, successfully. In order to completely restore our service, the next step was to call Comcast to "provision" the modem. The process requires providing the MAC address of the modem, so that it can be added as an allowed connection on the company's network. We monitored progress while on the call with Comcast, by continuing to ping Google.com.
Ping request could not find host google.com.Please check the name and try again
As soon as Comcast's Customer Service person completed our modem setup, we were once again cutoff from the internet. It was now apparent that Comcast is blocking the MAC address of the Netgear modems, though the devices have no problem otherwise in establishing a connection on their network.
Our next step was to contact both Netgear and Comcast media relations departments, to investigate this matter. If the unsolicited report that we received at Frys was correct, an unknown number of Comcast customers were suddenly being forced to purchase new modems... with no explanation or forewarning from Comcast.
As of this writing, Netgear has not yet responded to our request. We did get a response from Charlie Douglas, the Senior Director of Public Relations and Communications at Comcast Corporation, in Philadelphia where Comcast is headquartered.
Here is a webpage that lists all the compatible devices we support.
As you'll see, we support the Netgear DOCSIS 3.0 CMD31T cable modem.
Please let me know if you have any other questions.
According to Douglas's initial response, there should be no problem using Netgear cable modems. In fact, the CMD31T is on the approved device list!
We have an approved modem, which our current test (and prior months experience) shows is completely functional and capable of providing a high-speed broadband connection on Comcast. But Comcast in the San Francisco Bay Area is rendering these devices unusable. Why? Has there been some sort of falling out between Comcast and Netgear? We are currently waiting for an answer.
On Monday, March 26, we once again contacted Mr. Douglas, who had promised to investigate further. The answer we received did nothing to settle the matter, as Comcast has now "passed the buck" back to Netgear.
(EE Daily News) Has your investigation uncovered an explanation for the Netgear modem issue?
(Comcast) We have and Netgear plans to contact you. I have passed along your contact info. Pls stand by. You should hear from them shortly.Many questions remain. If they have uncovered an explanation, why has Comcast now decided not to share it with us?
Comcast could conceivably be liable for the unnecessary expense of many returned Netgear CND31T modems. We will update this story as soon as we get new information.
- Purchasers of the CMD31T modem on Newegg also report issues with Comcast service
- Users report same problem with Comcast-Netgear, on the Netgear user forum.
From Netgear's PR firm, via email:
"Last week Comcast upgraded their Cable Internet head-end systems in select cities which caused the Internet connection failure for a few customers who had the NETGEAR CMD31T Docsis 3.0 Cable Modem. We were immediately in touch with Comcast regarding the issue and within a day corrective action was taken. Comcast had rolled back to the older system and all customers were online.
We are working closely with Comcast to ensure that customers do not face Internet disruptions for any such future upgrades to the system."Update 02/28/2012 at 3:30PM PDT
From Charlie Douglas, Senior Director of Public Relations and Communications at Comcast Corporation:
“Comcast is in the process of deploying IPv6 nationally. We recently identified that the retail NetGear CMD31T device ships with and runs an uncertified version of firmware that exacerbates a critical IPv6-related defect. To ensure Comcast customers with these devices will continue to have uninterrupted Internet service, we have rolled back IPv6 temporarily in some parts of our network to give NetGear more time to address the issue. Comcast anticipates NetGear will soon address the issue for their retail devices, which we will test and deploy on an emergency basis.”No word yet on how Comcast and/or Netgear will compensate customers for the expenses incurred for unnecessary modem replacements.