HELP, level 1 and "chat" tech's could not help in a timely manner and since there are no longer any FIOS tech's at dslreports to assist - outside or rebooting the router and receivers what else can we do to regain access to my DVR (6416-2). This is a chronic issue that has, in the past, been handled via the techs that monitor the verizon direct forum in 5 minutes. Any assistance is appreciated.
Thanx
Bad gateway and not responding are usually issues with the routers firewall.
Assuming that you do not have any personal settings on the router (you are using the default settings from Verizon), there are two things I can think of to try.
1st. Try a factory reset on the router. This is the first thing you should try. Always seems to work for my neighbor. Just press and hold the reset button on the back of the router for 15 seconds with the router turned on. Wait for it to reboot and your internet to come back on-line. Then power cycle your STB's.
If that doesnt work, log into the router and check to see what firmware your router has. If you have a Gen 1 actiontec router with firmware ending in 10.14.0 there is an issue where that firmware will not let the caller ID on tv nor the remote DVR to work properly. If you have that firmware, you need to roll the firmware back to version 4.0.16.1.56.0.10.12.3 This will allow the remote DVR to work again.
To do this... Log into the router. Once logged in, click on the "System Monitoring" icon in the top right. This will tell you the firmware version that you are using. If you are using the one that ends in 10.14.0, then go to the "advanced" tab, and click on "firmware restore". That will roll you back to the previous version.
One of those should fix it. If not, you will need to contact tech support.
Thanx, I will try that in the morning when the users are snoozing - And thanx again for the quick response
Hi guys, new here but not new to the Bad Gateway - STB Not responding.
Double check the STB to see if Remote Access is still enabled. What happens as others have said is the
port forwarding for the DVR STB in the"Firewall Settings" somehow gets disabled, no way to re-enable.
I have an idea how and why but it doesn't really matter. When all is working I saved off a VZ Router config file. Any time the DVR forward(s) gets blown away I reload my file and it's fixed in 2minutes. May not be the smartest thing
to do but it's worked every time.
Bill
yeah, good idea. But thats why I suggested the reset. By resetting the router and then rebooting the stb. It will re-enter the forwarding.
Your way will work fine and is what most advanced users will use. Mine is just easier for the novice. 
The reason the reset works is that the STB is evidently using UPnP to register the port forward for the control channel . When things get screwed up, resetting the router clears the forwarding rule and then reseting the STB causes it to republish the UPnP request.
What happens when things aren't working is that the port forward somehow ends up pointing to the wrong IP address (STB perhaps changing address?) and at that point when the STB attempts to publish the port forward request, the router finds that one is already in place and refuses to change it to point to the STB.
I've had great success using DHCP address reservation ... essentially, resetting the router and then resetting ALL of the STB's and then getting everything working ... then once working, going into the Advance settings on the router and going to IP Address Distribution and selecting Connection List ... and then locating the address registration for each STB, going into the entry and changing the definition to be "static" so that each STB stays on the same IP address always.
Now, even when things get screwed up, since the rule which is in place in the router always points to the STB which is the DVR, everything continues to work.
space,
does reseting and rebooting the router, wipe all the "configurations" that some of us add? Just curious. I do have some port forwards that I use for house surveillence and music streaming to my cell...
Thanks,
Bill
Yes, a reset will toss the configuration and you will need to re-add the information.
Thanks for the info lasagna, I just have to make sure I keep a copy(ies) of my rtr config handy.
Bill
Hey everyone, I came across this thread and thought it would be a great place to interject and say hello. My name is Karl and I’m one of the new Verizon techs that will be helping out and providing support in these forums. Thank you to spacedebris for providing a great answer to your question. If the problems are not resolved with what’s already been suggested, please respond back to this topic and we can take care of you from there. Thanks -- Karl
Thanx Karl, the factory reset did not work. I am still getting initially "Set-Top Box - 0001096583054238 is not responding." and after refresh "Bad Gateway" Do you have access to Verizon Direct at DSLreports.com? If so I can give you my information in a protected venue and you can see what is going on.
Thanx,
Jim
So I am another person with this problem. I am getting EXTREMELY frustrated, bc this comes after months of problems with our last set top box and even some wiring issues (that have been resolved but took MONTHS and HOURS of phone calls). Now we've switched from Tivo to the Verizon DVR and I am starting to think we've made a big mistake. I would be SO grateful for help on this.
We are getting: 'Set-Top Box - 0000007031568246 is not responding.' and then Bad Gateway. https://www36.verizon.com/fiostv/web/members/Schedules.aspx And of course all recordings fail...
I am afraid to go ahead and reboot the router bc I'm not sure what kind of information we will lose. If I can figure that out and find the information ahead of time I'd be a lot more confident! Please let me know if you can. Thanks.
I'm having the same problem and have tried working through customer service but they have blown me off several time this week saying my issue has been sent to the DVR tech and someone will be in touch.
Trying to figure this out myself I've noticed that the port forwarding rules for both my DRVs are disabled. From what I'm gathering the only way to fix it is to do a hard factory reset on the router which means I lose all of my other custom settings. I do have a backup of the router configuration but it's from after the issue began.
I bit the bullet and did a hard reset on my router last night then went through the process of doing all of my custom settings again. Didn't actually take too long because I had kept notes of everything. Anyway, still no luck with the online access to the DVRs. The previously disabled port-forward firewall rules are no longer in the router which I guess is a step in the right direction because there was no way to activate them once they became disabled. Now I need to figure out how to recreate them. I don't know if the tech manually created them during my install or if the DVRs somehow generate them.
Now instead of a "bad gateway" message I get "not responding" which might be progress. I don't have problems with multi-room DVR access although I haven't checked since resetting everything last night. I also went into the settings on both DVRs and disabled/re-enabled internet access for remote DVR - no luck.
Here's an update on my situation -
Someone from VZ contacted me through the forums here and asked me to submit some info through an online form link. About an hour later I got a phone call asking me to check something on my DVRs. I was at work so couldn't do it right away. When I got home I checked my router and there were some new port-forward rules for the fire wall and I now have online access to one of my two DVRs.\ but the other reports "bad gateway".
Here are the new entries. My DVRs are .102 and .104 - .102 is working, .104 is reporting bad gateway. Also, .13 is my netbook which for some reason has a new entry that doesn't have an option to delete and is reported as a coax connection even though it's running wireless through a WAP (I have disabled the Actiontec wireless).
192.168.1.100:8082 Application
TCP Any -> 35000 Broadband Connection (Coax) Active
192.168.1.101:8082 Application
TCP Any -> 35003 Broadband Connection (Coax) Active
192.168.1.102:63145 Application
UDP Any -> 63146 Broadband Connection (Coax) Active
192.168.1.102:8082 Application
TCP Any -> 35001 Broadband Connection (Coax) Active
192.168.1.103:8082 Application
TCP Any -> 35002 Broadband Connection (Coax) Active
192.168.1.13:50000 Application
UDP Any -> 63145 Broadband Connection (Coax) Active
One more just popped up and now both my DVRs are accessible online.
192.168.1.104:63145 Application
UDP Any -> 63147 Broadband Connection (Coax) Active
Same problem here. Seems to have started after I returned one of my DVR's. Looks like all the port forwarding rules have also been disabled. I went and tried creating my own by forwarding UDP ports 63145 through 63149 to port 63145 on my STB, no luck. Thinking maybe something on the backend is messed up.
Don't know if I even want to try to call tech support and waste my time trying to get this to work.
I am having this issue as well. I upgraded to the 500gb dvr and haven't been able to use remote dvr at all.
I've done a hard reset of my router and reset by stb a few times now and nothing changes.
I figured out a fix: Reset the upnp settings and then enable them; on you router's web page, go to Advanced->Universal Plug And Play, and enable the "Enable Automatic Cleanup of Old Unused UPnP Services" check box; click apply; then do the same and unclick it. That seemed to remove the old IPs for the STBs and set them up in the correct order, and enable port forwarding for port 61345.
yeah!!Thanks the upnp option worked!!!!
Start a new topic or ask questions in the open forum.
