04-13-2012 07:23 PM
Can anyone help? I received Bad Gateway message about a month or two ago, and it was fixed. Now I am getting the same message for both DVRs and cannot access remote DVR online. Why does this keep happening???? I have tried the fixes. Can any Verizon techs please fix the port forwarding issue? Thanks.
Solved! Go to Solution.
04-14-2012 09:12 AM
when you want that fixed, it's best to hit the contact us link that verizon has on this page, and then do a live chat. they fix it pretty fast. these are peer to peer forums, so we are mostly other users, the contact us link takes you straight to verizon and they should be able to fix that, or at least I have had good experience with them fixing that in the past.
04-14-2012 09:28 AM
Things you can try
Reboot router.
Then Reboot DVR boxes.
I bit more complicated
Reboot router
In DVR disable remote DVR
reboot DVR
In DVR reenble remote DVR access
Still not working try opening a online chat with tech support.
04-14-2012 09:30 AM
The gateway problem probably broke your caller ID also. There is now a "fix caller ID" menu option on the STB. You might want to try that and see if it fixes the problem. It has for others on other forums.
04-14-2012 09:51 AM
PJL wrote:The gateway problem probably broke your caller ID also. There is now a "fix caller ID" menu option on the STB. You might want to try that and see if it fixes the problem. It has for others on other forums.
It has never broken my Callerid at the same time. But I suppose it might work in some cases.
04-14-2012 10:00 AM
tns wrote:
PJL wrote:The gateway problem probably broke your caller ID also. There is now a "fix caller ID" menu option on the STB. You might want to try that and see if it fixes the problem. It has for others on other forums.
It has never broken my Callerid at the same time. But I suppose it might work in some cases.
It has been many months since I have gotten the Bad Gateway message, and even back then it fixed itself in a few hours. And I am guessing that my Caller ID on the TV has worked flawlessly for probably a year or so now, and really it has worked very well for the three years or so that I have had it, only a few failures, maybe 3 or 4.
I just don't understand how it can work so well for some and so poorly for others, what is the difference?
__________________________________
Justin
FiOS TV, 25/25 Internet, and Digital Voice user
QIP7232, QIP7100-P2, IMG 1.9
Keller, TX 76248
04-14-2012 12:50 PM
Mine worked flawlessly for 3 years, then got Bad Gateway a few months ago. Anthony from VZ fixed it remotely somehow (path forwarding), and it worked fine until a few days ago. I also cannot log into the router -- my password will not work, but I am a little wary of resetting the router to factory settings. I have never enabled the caller id option, as I think it would be annoying, but I suppose I can try. I am hoping it can be resolved without calling cusotmer support.
04-14-2012 01:13 PM
Suzanne7777 wrote:Mine worked flawlessly for 3 years, then got Bad Gateway a few months ago. Anthony from VZ fixed it remotely somehow (path forwarding), and it worked fine until a few days ago. I also cannot log into the router -- my password will not work, but I am a little wary of resetting the router to factory settings. I have never enabled the caller id option, as I think it would be annoying, but I suppose I can try. I am hoping it can be resolved without calling cusotmer support.
As I understand it, there are two under-the-covers ways that Verizon has used in the past to define the path to your DVR, one is prone to failure, the other tends to be very reliable. You can determine which setup you have by going into the Menu on your STB and running the Self Diagnostics of the In-Home Agent. If the FiOS TV Remote DVR entry says "Listener 1 Started" then you have the "good" reliable path, if it says "Listener 2 Started" you have the less reliable path. The re-map that Verizon tech support can do supposedly changes the path setup to the more reliable one. You might check and see, and get them to change it if needed.
As to logging into the router, have you ever done so succesfully? If not, the login name should be "admin" and the password should be the serial number of your router. You can find the serial number on a label on the router. And just ignore however many characters are displayed when you type the password, just type it correctly, the router displays extra "*" characters as a rather useless security feature but they are not used to verify your password.
If you need to reset the router, should be no issue at all unless you have previously gone in and changed things.
And finally, Caller ID on the TV, I love it! When the phone rings now I immediately look at the TV first, even if I have the phone directly in front of me, or I am in a room where there is no TV.
You can control how long the Caller ID info is displayed - 2, 5, 10, or 15 seconds, so you can make it as intrusive or non-intrusive as you want. And of course if you decide you don't like it, just turn it off.
Hope this helps a little bit.....
__________________________________
Justin
FiOS TV, 25/25 Internet, and Digital Voice user
QIP7232, QIP7100-P2, IMG 1.9
Keller, TX 76248
04-14-2012 01:19 PM - edited 04-14-2012 01:20 PM
Justin wrote:As I understand it, there are two under-the-covers ways that Verizon has used in the past to define the path to your DVR, one is prone to failure, the other tends to be very reliable. You can determine which setup you have by going into the Menu on your STB and running the Self Diagnostics of the In-Home Agent. If the FiOS TV Remote DVR entry says "Listener 1 Started" then you have the "good" reliable path, if it says "Listener 2 Started" you have the less reliable path. The re-map that Verizon tech support can do supposedly changes the path setup to the more reliable one. You might check and see, and get them to change it if needed....
The difference is that UDP is used for Listener 1, and TCP for Listener 2. Has anyone with a "bad gateway" tried to resolve it by running the Caller ID troubleshooter in the STB support menu?
04-15-2012 02:55 AM
Actually yes, I tried it last week and for me it didn't work. In my case Callerid had not stopped working, but showed the bad gateway. Did the reboot technique to get mine back.