US Telco Support > Verizon > Verizon FIOS TV > No channel guide for days on end

No channel guide for days on end

You tinkered with the router and now you wonder why the guide doesnt work. Is that the jist of your question?

reply to ThereYouAre
The STBs like to start at .100 so I'd get them assigned in that range first and arrange the rest of your network/assignments around that.

reply to joe01880
If you have a complicated network of COURSE you're going to tinker with the router and there certainly isn't any reasons NOT to -- you just need to understand the quirks of the STBs etc.

And when you run into problems, this is a good place to ask for help

reply to darcilicious
My main question is what does an STB expect from the router in order to work. Verizon doesn't seem to indicate things like "if you modify default router settings, make sure you..." and that's the sort of information I need.

I'll change the DHCP range to .100 to .150 and see if that solves it. Unfortunately there doesn't appear to be a menu on the STB to refresh the DHCP and then provide any information, such as getting an address not in the range expected, etc.

reply to ThereYouAre

Re: No channel guide for days on end

There's still something not right. I changed the DHCP range and cycled power on the router, then double-checked. .100 to .150 is the range. Cycled power on the STB that isn't working. The other STB has 192.168.1.100.

Waited and kept checking the "bad" STB and it still has no IP. The Actiontek stats show only one STB on the network.

I can't seem to find any logs on the Actiontek that shows attempts to get DHCP addresses. I'm beginning to wonder if I'm chasing the wrong problem and it has nothing to do with the DHCP setup.

Reset your Actiontec to the OEM settings and print/write them out. Now when you change them you will have some "blueprints" to work with.
Lee

I should have done that.

But, both STBs are now assigned IPs and have all the program guide info! I'll see if this sticks or fails again, but maybe it just took a while for things to get back in sync. I cycled power on both STBs and they came back on-line in a few minutes.

Thanks for all the suggestions!

reply to darcilicious

said by darcilicious:

If you have a complicated network of COURSE you're going to tinker with the router and there certainly isn't any reasons NOT to -- you just need to understand the quirks of the STBs etc.

And when you run into problems, this is a good place to ask for help

reply to ThereYouAre
whats the class of business?? static or dynamic??

I've had a business account with static IPs for several years now. Prior to this, I had both DSL (fixed IP) and cable (dynamic, higher speed). My LAN has 4 servers (which also have WAN ports using static IPs), 5 UPS SNMP units, a number of statically assigned machines, print servers, WAP, etc.

Back in 1994 I ran an ISP, and did IP stack programming. My background is network programming. So while there are some implications that maybe I shouldn't be changing default settings, I'm quite capable of making changes once there is sufficient information and the behavior of the network devices is known. Now I know that the DHCP server must server only .100 to .150. Maybe that's not entirely true, which is why I was asking for additional information.

I had originally changed the DHCP range since my servers were around 100-110, but I moved them to different addresses, fixed the DNS tables, etc. I'm looking for any additional info that might warn me of things to do or not to do with FiOS TV on the same LAN.

BTW, there doesn't seem to be a Forum dedicated to conflicts with LAN settings and TV service. Since the LAN was still running fine but TV wasn't, it seemed like this was the right forum.

reply to ThereYouAre

My AT is set to give out DHCP IPs from 192.168.1.91 to 115, and I've seen no issues, so I doubt that it's the range. I only have a HD DVR on it, but it quite happily resides at 192.168.1.100 in the range I describe.

If you had enough devices to pull IPs up into the range where the STBs want to be (.100, .101, .102 ...) from your start of 192.168.1.80, it could interfere.

From your last post, the 100-110 IPs may not have been free to the STBs. When they released, the STBs may have moved down to 100, 101, and the one that hung just needed a reboot.

reply to ThereYouAre
The STBs have a "strong affinity" for DHCP addresses starting at .100, but as far as I have been able to determine, and from what other posters have reported, the STBs seem to be well behaved DHCP clients.

•Is it always the same STB that is losing or not getting a DHCP address?

•I'm assuming that you have created the DHCP pool large enough to accommodate all your dynamic devices.

•Have you tried creating DHCP reservations for the STBs under ADVANCED->IP ADDRESS DISTRIBUTION->Connection List->New Static Connection?

It took a few days to get back to this. One STB is always the problem for the past two weeks. We had a program guide yesterday morning, but it was gone by night and hasn't returned.

The DHCP pool is much larger than the maximum number of devices that will use it. Most systems on the LAN have static IPs.

I hadn't created the static DHCP reservations but did this morning. Cycled power on the STB but it's still not showing up and doesn't have an IP assigned.

The TV reception is fine, but I will trace the coax from the STB all the way back to the router and see if there are lose connections, uni-directional amps or other devices that could be causing a signal problem next.

reply to ThereYouAre
FWIW, my two boxes pull IPs in the 100+ range from the router.

QIP-6416 = 191.168.1.194
QIP-2500 = 191.168.1.161

I use a Linksys WRT54GS with a NIM 100 and set the DHCP range to .100 through .200 because when I first set the system up using the Actiontec, the two IPs above are what the boxes seemed to want. They never obtain IPs that are different from the ones listed - it seems they individually have preferred numbers.

For the heck of it, I disconnected both the boxes from the AC and powered down the router for about an hour. I reconnected the router, cleared the DHCP client table and then reconnected the STBs. They both pulled the same IPs they had before.

You might try expanding the DHCP range upward to accommodate higher addresses.
--
Never raise your hands to your kids. It leaves your groin unprotected. -- Red Buttons

reply to ThereYouAre
swap the box in the other room? Maybe a box issue ?