Your ISP's DHCP is not functioning properly

[ArtFreen]

This error message appears in the router when I try to hook up a new modem. 

I've called in two times to try to resolve this, without success. The solution appears to be for Comcast to send a provisioning signal - whatever that is, but it appears that the techs on the phone I've interacted with aren't up to speed on this. Also, for the record, I have two Asus routers and when I tried to connect either one of them to the brand new Netgear CM1000 modem, I got this same error, so the likelihood that it is a defective router issue seems vanishingly small.

If anyone at Comcast can address this, it would be greatly appreciated. 

[EG]

Are you power cycling the CM1000 each and every time that you change the router that is being connected to it ?

[ArtFreen]

Yes, I've tried power cycling. No amount of power cycling seems to solve this issue. 

[strega7]

There a quite a few threads about this.  I notice it's always an Asus router.  It seems they are sensitive to something that other routers are not.

https://forums.xfinity.com/t5/Your-Home-Network/your-ISP-s-DHCP-is-not-functioning-correctly/td-p/33...

https://forums.xfinity.com/t5/Your-Home-Network/ISP-DHCP-not-functioning-properly/td-p/3355622

https://forums.xfinity.com/t5/Your-Home-Network/your-isp-s-dhcp-does-not-function-properly/td-p/3356...

etc.

It seems like @ComcastChe is the person who knows how to fix this.

[ArtFreen]

Today I tried again to enable my new modem and called Comcast to get assistance with that (in case it didn't work, I needed to be able to revert back to the Comcast modem). Again, after I gave the new MAC address, the ASUS router (RT-AC1900P) displayed the message, "Your ISP's DHCP is not functioning properly." However, at that point, asked the Comcast agent helping me to send a "provisioning" signal to my modem - whatever that is. 

He knew what I was asking for and sent the signal.  After the modem responded to the provisioning signal, my router immediately picked up an IP address and everything then worked perfectly.  I hope this becomes part of the standard procedure for addressing this issue.