Rattler
join:2001-04-13
Havertown, PA
 ·Verizon Online DSL
 ·Verizon FIOS
1 edit | reply to John97
Re: FIOS TV Central website access with Non AT Router?
Well, I just checked mine and there is one thing I can say for Verizon: They are consistent only in their inconsistency! 
I can log on to FiOS TV Central and see the DVR but any attempt to communicate with it just hangs the app or I get the error message that the DVR is not responding. Happens with FireFox or IE. This is after having it work just fine for a couple of weeks...
I can poll and reset it from "My Account".
--
Never raise your hands to your kids. It leaves your groin unprotected. -- Red Buttons |
|
Onedollar
join:2001-08-27
Pomona, CA | Mine still working... hopefully i dont jinx it like last time. Im thinking if nothing in the config has changed and it stops working, then its something on the vz side that is causing this. |
|
ps851112
join:2009-06-01
Keller, TX
| reply to Psyclone
DNS screen info | 
Port Forward info |
www36.verizon.com to 198.23.16.154. After he did this everything on the westell started working. I have not configured my personal router yet but plan on it in the next few mins and will update on my result. |
|
ps851112
join:2009-06-01
Keller, TX
2 edits | reply to Psyclone
Okay, my setup is
DIR-655 connected from lan to lan on westell verizon router. Verizon westell router has been setup as a bridge.
The DIR-655 is running the latest firmware Version 1.31NA
My DIR-655 is on 192.168.1.x scheme. The DVR is using 192.168.1.100 which i setup in the DIR-655 DHCP tables. I have verified communication by pinging 192.168.1.100 and also by running a diag on the box.
I have setup my tcp and udp 63145 and 1659(saw 1659 in the log of the westell) to 192.168.1.100.
Currently no success with Remote DVR access. :uhh:
Guide, Widgets, and VOD work fine.
I think this has to do with the DNS, like i posted earlier the verizon tech I worked with on the phone manually input www36.verizon.com to refer to 198.23.16.154 in the westell.
If you type in 198.23.16.154/fiostv/web/ in your browser you'll get to the FiOS TV Central page.
I tried pinging www36.verizon.com from command prompt on my computer with my DIR-655 in place and get something completely different and cant do the same thing I did with the other address.
So with the results you take 96.6.32.181/fiostv/web/ into my web browser and get nothing.
This is the part that has me scratching my head
"Pinging e155.g.akamaiedge.net [96.6.32.181]"
refers to this page »www.akamai.com/
I have also watched the "internet sessions" link under "status" of my DIR-655 and can see that ip address 192.168.1.100 is trying to talk out bound with a bunch of different places. Some of the ip address appear to route to something similar to this Akamai.
So now I'm stuck, I'm not able to link this address www36.verizon.com to this ip address: 198.23.16.154 if someone know how to do this on a DLINK please let me know as I cannot figure out how. I have emailed DLINK support with this question but I am currently awaiting their response.
Tomorrow evening I'm going to try switching back to the Westell and try pinging www36.verizon.com and see what happens before adding in this different DNS route and after I add it.
I really wanna try now but I'm suppose to be getting up for work in 4 hours and have to roll out some new servers, so my phone will be ringing off the hook. Its gonna be a bad day tomorrow. :( |
|
More Fiber
Premium,MVM
join:2005-09-26
West Chester, PA
·Bay Area Internet ..
| said by ps851112  :I think this has to do with the DNS, like i posted earlier the verizon tech I worked with on the phone manually input www36.verizon.com to refer to 198.23.16.154 in the westell. Do you have the same DNS servers configured in both routers?
i.e. Obtain automatically vs. use OpenDNS or some some non-VZ DNS service?
In the LAN-to-LAN configuration, have you tried enabling DHCP on the Westell and disabling DHCP in the D-Link?
I'm assuming you have a cat5 connection to the ONT, and your objective is to run the D-Link as primary router. |
|
ps851112
join:2009-06-01
Keller, TX
1 edit | Oops, Double post... |
|
ps851112
join:2009-06-01
Keller, TX
| reply to More Fiber
The DIR-655 is using the DNS verizon provides, Ive tried a few others but same result.
I have the westell turned into a bridge, basically a layer 2 switch, so there is not DNS server entries in the westell.
It appears that the issue is with any DNS server (absurd that verizon wouldn't get that fixed. A tier 1 tech from verizon knows about this then I'm sure the guys at the C/O would know).
Reason i say this, Ive been to several web sites that do some of the following tests using their DNS and not mine. Ive done ping, tracert, nslookup, etc from these sites and get similar problems.
The DNS settings is held locally in the Westell router when its acting as a router. So if I had the westell up with the DNS setting, if I did nslookup or ping from my computer i should always get the same result which is 198.23.16.154
I have not messed with much as I just got the service working on the verizon supplied router last night and probably wont do any testing tonight since I didn't get much sleep and need to catch up, ill try different configs Friday and maybe over the weekend.
my current setup which is working for Guide, Widgets, and VOD but not for remote DVR.
::ONT::--Cat5e--::DLINK::--::Westell Bridged Mode::--Coax--::VerizonDVR:: |
|
ps851112
join:2009-06-01
Keller, TX | reply to Psyclone
Well.... Its working... I didn't do a dang thing either. Same setup as last time I replied. |
|
uspino
join:2008-11-08
Chevy Chase, MD | ps851112, could you provide a detailed account of your setup? My ONT-DLINK-Actiontec-Coax-DVR stopped working after a few week of flawless Remote DVR.
Thanks. |
|
Rattler
join:2001-04-13
Havertown, PA
·Verizon Online DSL
·Verizon FIOS
| Ditto! A couple of weeks of flawless operation with my Linksys and NIM, then blotto...
I just checked my daughter's Remote DVR and it is working fine - she uses the A/T router with an Ethernet feed.
--
Never raise your hands to your kids. It leaves your groin unprotected. -- Red Buttons |
|
ps851112
join:2009-06-01
Keller, TX
| reply to Psyclone
|
|
ps851112
join:2009-06-01
Keller, TX
2 edits | reply to Psyclone
Below is what I see when I'm accessing the DVR, this only appears when accessing the DVR. I haven't noticed it while inactive. I have attached the same info in a excel document to make it easier to look at (I recommend looking at the excel doc since the formatting is way off on the page and I don't want to take the time to re-format it). I will post the steps I went through on the Westell soon.
I'll take some photos and post those for physical reference if someone request for them.
Local Local Port Nat Port Internet Protocol State Dir Priority Time Out
192.168.1.100 42408 42408 96.6.32.181:443 TCP CL Out 128 230
192.168.1.100 58119 58119 96.6.32.181:443 TCP CL Out 128 229
192.168.1.100 33281 33281 68.238.96.12:53 UDP - Out 128 18
192.168.1.100 6346 6346 174.136.255.144:50689 TCP CL In 128 195
192.168.1.100 63145 63145 198.23.16.154:3333 TCP EST Out 128 7790
I have a Motorola NIM100 on its way and we will see what happens with that device.
After closer inspection, looks like it set the DVR to the DMZ, must have been when I was falling over in my chair from lack of sleep.
I will try removing it from the DMZ and see what happens.
I currently have the DHCP range set to 192.168.1.10 - 192.168.1.150
I also have my DVR MAC reserved to 192.168.1.100.
So just to remind my current setup is
ONT to DLINK DIR-655 via Ethernet. from DIR-655 LAN port to Westell LAN port. Westell setup to bridge mode, so it is acting as a network switch. |
|
ps851112
join:2009-06-01
Keller, TX
| reply to Psyclone
Okay, took the DVR off the DMZ and right away, stopped working. After turning the DMZ back on, not responding.
I do see in the network activity that 192.168.1.100 is talking to the outside but its not talking to 198.23.16.154:3333 like it was doing before.
If you looked at the ports info excel I attached you will also see that the box was talking to 63145 on TCP and not UDP.
So I added a Virtual Server for public port 3333 to transfer to 63145 on both TCP and UDP, no response. Also tried 3333 to 3333 for both TCP and UDP, no response.
Just checked the Active Connections and now see
But it has now dissapeared and still not working.
Also I see this
Hope this helps a bit, I may see if I can play around with the ICMP, I think the box talks to the Verizon servers to let it know its alive and available for connection through ICMP or a few different protocols perhaps. |
|
ps851112
join:2009-06-01
Keller, TX | reply to Psyclone
So, Working again...
Everything is the same except the DVR is not on the DMZ. |
|
John97
Over The Hills And Far Away
Premium
join:2000-11-14
Southampton, PA
1 edit | Once you get your NIM100, you can get rid of all of that port-fowarding, etc. I have none of that stuff setup and have full Remote and Mobile DVR functionality with a DIR-655/NIM100.
UPDATE: I have discovered that if I turn off DNS Relay in the configuration of my DIR-655 - Remote DVR stops working.
I turned it off to address another issue only to find Remote DVR no longer worked a day later. So, I turned it back on, rebooted the router, now it works again.
--
So put me on a highway, and show me a sign.
And take it to the limit one more time... |
|
Vamp9190
join:2002-02-11
Chantilly, VA
| said by John97 : I have none of that stuff setup and have full Remote and Mobile DVR functionality with a DIR-655/NIM100. You have the Home Media DVR service in order to get Mobile functionaliity, right? By mobile you mean setting up recordnigs on a mobile phone, correct? (either a VZ phone, or other carrier -- but with other carriers you lose being able to delete shows from the phone I think)
BTW
I have read this entire thread and it is really fascinating with all the different configs. and trials/testing. |
|
John97
Over The Hills And Far Away
Premium
join:2000-11-14
Southampton, PA
| said by Vamp9190 :You have the Home Media DVR service in order to get Mobile functionaliity, right? By mobile you mean setting up recordnigs on a mobile phone, correct? (either a VZ phone, or other carrier -- but with other carriers you lose being able to delete shows from the phone I think) BTW I have read this entire thread and it is really fascinating with all the different configs. and trials/testing. Yes. We have the Home Media DVR and have accessed it via my wife's Verizon mobile phone.
--
So put me on a highway, and show me a sign.
And take it to the limit one more time... |
|
jhearn
join:2003-01-02
Leesburg, VA
| John 97
I looked at your posts hoping to find the process you used to get remote DVR working using DLink router.
I have the original FIOS DI-624 connected by ethernet to the ONT and using a NIM from the DI-624 to provide guide data. Do I have to use the Verizon DNS addresses? And could you give me some clues on how to get this combination to work with remote DVR funtionality?
Thanks
Jack |
|
John97
Over The Hills And Far Away
Premium
join:2000-11-14
Southampton, PA
| said by jhearn :John 97 I looked at your posts hoping to find the process you used to get remote DVR working using DLink router. I have the original FIOS DI-624 connected by ethernet to the ONT and using a NIM from the DI-624 to provide guide data. Do I have to use the Verizon DNS addresses? And could you give me some clues on how to get this combination to work with remote DVR funtionality? Thanks Jack I don't have any DNS entries in my router, the fields are blank. Somewhere in this thread I posted the exact steps I went through to make my setup work. I didn't add any entries for port-forwarding or anything like that.
--
So put me on a highway, and show me a sign.
And take it to the limit one more time... |
|
Rattler
join:2001-04-13
Havertown, PA
·Verizon Online DSL
·Verizon FIOS
| reply to jhearn
Jack:
FWIW, I am running a Linksys WRT54GS router, running Tomato firmware, with a NIM-100. I have static DNS servers set into the router (4.2.2.2 and 4.2.2.3) At first, Remote DVR would not initialize since V* seemed to detect that I did not have their router (an Actiontec, in my case) installed. However, several weeks after initializing Remote DVR, it started to work without any further input from me. I have no port forwarding or any other special services programmed in the router.
At the moment, my DVR still responds to commands and polling from FiOS TV Central - I can check free space, look at and delete recordings and set new scheduled recordings as well as remove others from the schedule.
A week or so ago, Remote DVR stopped working but then, after a few days, it came back on line. I don't know if this has anything to do with the fact that I am not using their router or that I have my own DNS servers keyed in.
You also have to make sure that Remote DVR service is enabled in the DVR or it will not respond. Occasionally, V* sends a specific sort of reset that seems to turn off Remote DVR in the STB so you have to check to make sure it's still enabled in the box.
--
Never raise your hands to your kids. It leaves your groin unprotected. -- Red Buttons |
|
