Skip to main content
Accessibility Resource Center Skip to main content
Have a phone you love? Get up to $500 when you bring your phone. OR get iPhone 13, on us for a limited time. With Select 5G Unlimited plans. Buy now
end of navigation menu
Fios Quantum Gateway Router - DHCP Not Working
YPYPYP
Newbie

I have a Fios Quantum Gateway Router and latley I have been having issues with multiple devices not obtaining an IP address. On Windows 10 it will just say "unidentified network" and I will not have access to anything (including the router) and on android it will say "unable to obtain IP Address"

Checking the DHCP LAN logs i see a lot of these type of entries:

May 25 05:26:08 2017dhcpdinfo<158>DHCPREQUEST for 192.168.1.153 (192.168.1.1) from --:--:--:--:--:-- (Gateway7C709B) via br-lan: database update failed
May 25 05:26:08 2017dhcpdinfo<158>commit_leases: unable to commit: No space left on device
 
- I have some static IPs but they are outside of the dynamic range
- I have rebooted the router multiple times including resetting to factory defaults
- When I set my laptop up as static IP it connects immeditatly
- For DHCP devices I have to cycle the wifi on/off a few times and eventually it will connect
- I have 7 devices connected via wifi and 4 via ethernet
 
Thanks for the help!
0 Likes
Re: Fios Quantum Gateway Router - DHCP Not Working
jonjones1
Legend

@YPYPYP wrote:

I have a Fios Quantum Gateway Router and latley I have been having issues with multiple devices not obtaining an IP address. On Windows 10 it will just say "unidentified network" and I will not have access to anything (including the router) and on android it will say "unable to obtain IP Address"

Checking the DHCP LAN logs i see a lot of these type of entries:

May 25 05:26:08 2017dhcpdinfo<158>DHCPREQUEST for 192.168.1.153 (192.168.1.1) from --:--:--:--:--:-- (Gateway7C709B) via br-lan: database update failed
May 25 05:26:08 2017dhcpdinfo<158>commit_leases: unable to commit: No space left on device
 
- I have some static IPs but they are outside of the dynamic range
- I have rebooted the router multiple times including resetting to factory defaults
- When I set my laptop up as static IP it connects immeditatly
- For DHCP devices I have to cycle the wifi on/off a few times and eventually it will connect
- I have 7 devices connected via wifi and 4 via ethernet
 
Thanks for the help!

This should be easy. Your router is probably defective. I would call 1-800-VERIZON and get a replacement router.

additionally you can use your own purchased router. Simply do a DNS release, then before Verizon can refresh it immediately disconnect the power to the router.

then take the Ethernet cable that was connected to your Quantum and place it in the WAN port on your new router. Then power it up. You should get a DNS for our purchased router. 

Then test your devices.

https://www.dslreports.com/faq/verizonfios?

This above link may be of assistance.

Good Luck

0 Likes
Re: Fios Quantum Gateway Router - DHCP Not Working
jayriv
Newbie

Easiest is to report to Verizon or Frontier the DHCP database update failure and ask for the replacement OR do this

Login as administrator to the Quantum Wifi Router, go to Advanced, IP address Distribution and select Disabled. Your router will be asked to reboot. NOTES: this will refresh your Quantum Wifi/LAN router EVERYTHING will be earased! You will need to reconfigure your Wifi, just configure the same SSID and WSPAK2 encryption key so all everything will reconnect and obtain the IPs again.

The DHCP database/binding update failure is a serious issue. I just wanted to prove reset the DHCP database will make the DHCP works again and it indeed did!

I will still have to ask Frontier tech support to replace the Quantum Router for me since being charged $9.99/month for it!

0 Likes
Re: Fios Quantum Gateway Router - DHCP Not Working
iterminator
Newbie

I have the same problem my router has started acting weird. Doesn't hand our DHCP IP addresses (i.e. unable to get IP address). Generally it fixes itself but today if would not give iP address.

1. I rebooted the router multiple times.

2. Factory rest the router without any luck.

0 Likes