One Tivo sees the other but not vice versa

2753 Views 17 Replies 7 Participants Last post by doyling, Dec 28, 2011

britdiver

Discussion Starter · Nov 29, 2011

Hi,

I have two S3 HD Tivos and have had them for a while. Both have wireless adapters and both can get on my network and get online to get the tivo service info. And until recently the other tivo showed up on the Now Playing list just fine and I could transfer shows, and the other unit could do the same. So everything worked just fine. However, recently although they can both still see the network and both get online to get to the tivo service, one unit does not show the other on the Now Playing list, even though from the other unit I can see the first unit just fine. It will appear very briefly every now and again but then disappear from the Now Playing list.

Any ideas?

1 - 18 of 18 Posts

steve614

· #2 · Nov 29, 2011

Assign a static IP address to each of your Tivos. Can't hurt, might help.

Once you do that reboot your Tivo network. Unplug your Tivos and your router. Restart the router first, then restart the Tivos.

CraigK

· #3 · Nov 30, 2011

We have three TiVos and have had the same symptoms over the last month or so. On Thanksgiving we had a three hour power outage that turned off the router and TiVos. Since the power came back everything is fine.

Sounds like Steve's advice is perfect. I might try static IP addresses to see if that fixes it for good.

unitron

· #4 · Nov 30, 2011

CraigK said:
We have three TiVos and have had the same symptoms over the last month or so. On Thanksgiving we had a three hour power outage that turned off the router and TiVos. Since the power came back everything is fine.

Sounds like Steve's advice is perfect. I might try static IP addresses to see if that fixes it for good.

Sometimes you have to reboot the entire network, modem, router(s), computers, TiVos, game consoles, whatever.

But yeah, anything that don't travel, give it a fixed IP and set the router's DHCP pool of possibles to a range into which none of those fixed numbers fall.

britdiver

Discussion Starter · #5 · Dec 2, 2011

Thanks guys. I will give it a try.

lillevig

· #6 · Dec 2, 2011

britdiver said:
Hi,

I have two S3 HD Tivos and have had them for a while. Both have wireless adapters and both can get on my network and get online to get the tivo service info. And until recently the other tivo showed up on the Now Playing list just fine and I could transfer shows, and the other unit could do the same. So everything worked just fine. However, recently although they can both still see the network and both get online to get to the tivo service, one unit does not show the other on the Now Playing list, even though from the other unit I can see the first unit just fine. It will appear very briefly every now and again but then disappear from the Now Playing list.

Any ideas?

+1 on the reboot and static addresses. I've had this problem specifically after going online to rename one of the Tivos. Had to reboot that Tivo, even though the new name showed up on it, to get the other one to see it again.

dougdingle

· #7 · Dec 5, 2011

I occasionally have my TiVo farm (two S3, two S2, one S1) lose sight of each other. It's almost always the S3's that go brain dead. I used to do a full reboot of all TiVos and the network itself to get everything working again.

I've since discovered that going into S3 network setup and simply reselecting DHCP to get a fresh IP works in a matter of seconds, and is a LOT less hassle than waiting for everything to reboot.

I have to do this about once a month, and haven't had additional issues since.

unitron

· #8 · Dec 5, 2011

dougdingle said:
I occasionally have my TiVo farm (two S3, two S2, one S1) lose sight of each other. It's almost always the S3's that go brain dead. I used to do a full reboot of all TiVos and the network itself to get everything working again.

I've since discovered that going into S3 network setup and simply reselecting DHCP to get a fresh IP works in a matter of seconds, and is a LOT less hassle than waiting for everything to reboot.

I have to do this about once a month, and haven't had additional issues since.

Or you could give everything on the network that doesn't travel a fixed IP address, and save yourself all of that.

britdiver

Discussion Starter · #9 · Dec 11, 2011

Well I have just made both Tivos have a static IP on my router. So lets see if that fixes it. I will report back. Thanks again.

britdiver

Discussion Starter · #10 · Dec 11, 2011

But I did not change anything on the Tivo units. Is that ok?

unitron

· #11 · Dec 11, 2011

britdiver said:
But I did not change anything on the Tivo units. Is that ok?

The TiVo is where you give that TiVo a fixed IP address.

Messages and Settings, Settings, Phone and Network, Change network settings

britdiver

Discussion Starter · #12 · Dec 11, 2011

But won't it always get the same IP if I set it in the router too?

unitron

· #13 · Dec 11, 2011

britdiver said:
But won't it always get the same IP if I set it in the router too?

I'm guessing maybe your router let's you assign an IP address based on the TiVo's MAC, but that introduces the variable of is it the TiVo's MAC or the wireless adapter's MAC.

Going into the settings on the TiVo and giving the TiVo a fixed IP address eliminates the router having to make any decisions about it, which eliminates one of the many things that can go wrong. Granted, most of the time it probably won't go wrong, but why take the chance unneccessarily?

Let's say for the sake of discussion that your router defaults to an address for itself of 192.16.1.1

That means 192.168.1.255 gets reserved as the broadcast address for everything on the router and individual devices have the range of 192.168.1.2 to 192.168.1.254 in which to locate themselves or be located by the router.

Give everything on the network that doesn't travel a fixed IP address.

Start the computers at 192.168.1.101 and the TiVos at .201

Set the router's DHCP range to be from .251 to .254

If you have more than 4 devices which have to be dynamically assigned, lower the .251 accordingly.

When you go into the TiVo menu to set the IP, the subnet mask gets set at 255.255.255.0 and the gateway IP is the same as the router, 192.168.1.1, and the first DNS server the same as the router as well.

See less See more

britdiver

Discussion Starter · #14 · Dec 12, 2011

OK. I have now set both Tivos to fixed IP too. Obviously setting them to the corresponding static IPs that the router has set for them. So after restarting both Tivos, lets see if that works. Thanks again.

unitron

· #15 · Dec 12, 2011

britdiver said:
OK. I have now set both Tivos to fixed IP too. Obviously setting them to the corresponding static IPs that the router has set for them. So after restarting both Tivos, lets see if that works. Thanks again.

The only reason you should have to tell the router anything about them is to either place special restrictions of some sort on them, or exempt them from special restrictions placed on other things on your network.

As long as the first three sets of three numbers in the TiVo IP addresses are the same as the first three sets of three numbers in the router's IP address (the address it shows your network, not the address it uses on the cable/DSL modem side, which is usually assigned to it by the modem), then they're members of that network, and the router will automatically accept them as such.

britdiver

Discussion Starter · #16 · Dec 17, 2011

So far so good. Both machines seeing each other. Thanks

unitron

· #17 · Dec 17, 2011

britdiver said:
So far so good. Both machines seeing each other. Thanks

Always good to hear good news.

doyling

· #18 · Dec 28, 2011

I have one S3 on G WiFi, while my other is on 1GB LAN. I have static IP assigned already but have found that disconnecting the USB from the G card and back in will allow it to link back up. I have been toying with the idea of an N adapter for that unit, but not in the mood to drop money on a possible solution.

1 - 18 of 18 Posts

This is an older thread, you may not receive a response, and could be reviving an old thread. Please consider creating a new thread.