NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Losing IP address from cable modem in bridge mode every two weeks
Hi,
I am Comcast Customer with an ARRIS TG1682G Gateway/modem in Bridge Mode. I have a new Netgear 7000P (V1.0.0.58_1.0.50) that is connected to that gateway. When I installed it about 6 weeks ago, it would not get, or the gateway would not give, an IP address. I called Netgear support and they had me direct connect a PC to the gateway, then during the router setup, I needed to use the PC MAC address (IP spoof?) to get things working. Strange, but it worked.
About two weeks later, I lost internet access and find that the router does not have a working IP address again. I went through the same procedure and got it to work. I crossed my fingers to hope the fix would be permanant. Unfortuantley, two weeks later, I got the same problem and solved it with the same procedure.
I have also talked to Comcast support and they don't have an answer as to why this is happening and call the problem solved when we get things working again with the procedure described above.
My guess is that Comcast makes you get a new IP every two weeks and that cause the problem, but that is a guess. I posted this same message in the Comcast forums and on the Comcast subreddit. Is there some way to fix this so I don't have this problem every other Friday morning?
Thanks.
ElaineM,
Thanks for the link. I understand MAC spoofing now because of the troubles in getting this router to run continuously.
Please understand what I am saying:
1) The initial configuration is clunky because I restarted the cable modem BEFORE trying to configure the router and it failed to get an initial IP address. I then restarted the router again and then it got its IP address. I didn't do the second restart until two days ago and that is when it finally got its IP address with its OWN MAC address.
2) Before two days ago, for the last couple months since purchased as guided by your telephone support, the router was using a PC's MAC address that was able to easily obtain an IP address with only one cable modem restart, not two. Using that MAC address during initial configuration would get the router to get an IP address and work. It would only work until a future DHCP renew attempt. Here is where I am guessing on the problem: Either the DHCP server has a problem renewing the lease (not sure on this because it is Comcast and they have millions of customers...but maybe it is because it is Comcast...), or the Nighthawk is not making the renew request correctly (maybe using its own MAC address when it should use the spoof).
The router successfully renewed it DHCP lease last night on time (half time renew).
I have a working system now and I know how to make it work if I ever need to factory reset again but I have seen posts with similar problems here and elsewhere without solutions. I think it bears investigation.
Anyway, when the Nighthawk works, it is great. Great range and great speeds. I am very happy with the product, except for the challenges to get it to finally work consistently.
I will have to call the Customer Care line a third time as I still have not received the replacement router. I think the problem is solved now anyway, so we will see if they can cancel that.
Thanks for your help.
MarcG1
10 Replies
Update: It didn't last two weeks. Four days this time. This morning, I had no internet. The router had the amber light on. I know th drill know:
1: Plug the cable modem directly to a PC with the same cable teh goes to the router.
2: Reboot the cable modem.
3: Renew the IP address on teh PC with ipconfig /release, then ipconfig /renew
4: Plug the cable back into the router
5: Reboot router. Remember: The router is configured to spoof it MAC address with the PC's MAC address
The PC never has a problem getting an IP address, so I am thinking the router is the issue. I have never gotten the router to work with its own IP address.
Update 2: I called Netgear tech support to get a case opened with the problem. They asked me to downgrade the firmware. I told them that I have updated the firmware twice since purchase when I have been in the admin page getting things going again with the release/renew/reboot dance. The problem has cropped up in the last two versions of firmware so I declined to do that. She had me perform a factory reset since I didn't do that after the updates. I am now to monitor it to see if it happens again, if it does I am to call back with the same case number. I am hopeful but not optimistic as I have search this community and have found other posts with very similar problems without any solutions.
Please keep us updated.
Update 3: 6 days since the firmware update, a subsequent factory reset and reconfiguration and it is still running. I have been monitoring the DHCP lease renewals. The leases are 4 days long and they are getting renewed approaximately 2 days in. The longest it has gone since purchase is about two weeks, so we will see.
Update 4: The problem happened agin this morning. I have been monitoring the DHCP Lease since the factory reset and the router was getting 4 day leases and was getting renews well before 2 days left until yesterday. The last time I checked it had about 2 days and 12 hours to go. This morning, we did nothave a connection and when I checked for the IP of the router, it was 0.0.0.0. I did the reboot cable modem, reset IP from my PC, and reboot the router to get things running again. I still don't know if the problem is with the router or Comcast. Neither Netgear or Comcast are giving me ways to find out.
It looks like you are in the process of returning the unit back to us.
Keep us updated once you have tested the replacement router.
