Problems with more than one tivo on network

[petestrash]

Also, now having trouble getting the 'new' tivo to complete the first program call - can't get a connection. It will get through a test call, I can telnet in, but it won't complete the first program call.

Try turning the other TiVo off and rebooting the problem one again.

Your setup files look fine, I starting to think it may be a wierd router issue.

Peter.

[petestrash]

Can you also try the ifconfig command on both TiVo's to check the settings

Peter.

[MMooney]

ifconfig results:

'old tivo':

-------------------
lo Link encap:Local Loopback
inet addr:127.0.0.1 Bcast:127.255.255.255 Mask:255.0.0.0
UP BROADCAST LOOPBACK RUNNING MTU:3584 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 coll:0

eth0 Link encap:Ethernet HWaddr 00:05:5D:F1:05:3E
inet addr:192.168.0.25 Bcast:192.168.0.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 coll:0
Interrupt:29
----------------------

'new tivo' :

-------------------
lo Link encap:Local Loopback
inet addr:127.0.0.1 Bcast:127.255.255.255 Mask:255.0.0.0
UP BROADCAST LOOPBACK RUNNING MTU:3584 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 coll:0

eth0 Link encap:Ethernet HWaddr 00:09:5B:33:4C:E6
inet addr:192.168.0.30 Bcast:192.168.0.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 coll:0
Interrupt:29

-----------------------

I have a netgear g router - pretty new, about three months old

[Wibble]

Have you just change your setup, in a previous message you mention the following setup for your old tivo:
ip=192.168.0.20

Yet the ifconfig show
inet addr:192.168.0.25

also

all your RX/TX packets are 0 whic is a bit strange.

Can you from both tivo's ping the router and the other tivos, then do an "arp -an" on both tivo's.

This will tell you what the mac address of the router is and what each tivo thinks the other's mac address is.

You should get something like this
[TiVo [p0] ~]# arp -an
Address HWtype HWaddress Flags Mask Iface
192.168.12.1 ether 00:13:F7:07:3C:E4 C * eth0
192.168.12.2 ether 00:16:E6:56:5C3 C * eth0
192.168.12.51 ether 00:00:00:00:00:00 MP * *

You can ignore the line with a mac address of all 0's.

(Got to love that smiley)

[MMooney]

yeah, did change the IP address when did nic_config to make sure that something was happening!

arp -an result for the good tivo (.0.5 is my laptop):

192.168.0.1 ether 00:1B:2F:07:6E:5A C * eth0
192.168.0.5 ether 00:18E:B8:F4:44 C * eth0
192.168.0.30 ether 00:09:5B:33:4C:E6 C * eth0
192.168.0.25 ether 00:00:00:00:00:00 MP * *

and for the bad tivo
Address HWtype HWaddress Flags Mask Iface
192.168.0.5 ether 00:18E:B8:F4:44 C * eth0
192.168.0.25 ether 00:05:5D:F1:05:3E C * eth0
192.168.0.30 ether 00:00:00:00:00:00 MP * *



I am thinking it is something to do with the router - when I look for the tivos as attahced devices, the router lists the MAC addresses without IP addresses unless I go into the Tivoweb and make a call, or telnet into the tivo and ping the router

[Wibble]

On both tivo's can you do a "route", you should get identical results.

Also do a "traceroute -n 210.48.107.133" on both and see how far the bad one goes.

[petestrash]

Sorry been away.

Wibbles suggestions are good.

I'm still leaning towards a router setup issue of some kind.

One further suggestion I have is to enable DHCP on your router and set the "bad" TiVo to use DHCP. Then see how it comes up.

Peter.

[MMooney]

route on the good tivo

--------------

Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.0.0 * 255.255.255.0 U 32767 0 0 eth0
default 192.168.0.1 0.0.0.0 UG 0 0 0 eth0
------------------

route on the bad tivo

------------
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.0.0 * 255.255.255.0 U 32767 0 0 eth0
default 192.168.0.1 0.0.0.0 UG 0 0 0 eth0
------------


not sure how to interpret these results:
traceroute for the good tivo
----------
traceroute to 210.48.107.133 (210.48.107.133), 30 hops max, 40 byte packets
1 192.168.0.1 6.156 ms 2.503 ms 2.862 ms
2 * * *
3 125.237.192.1 47.291 ms 47.982 ms 50.104 ms
4 202.50.245.194 160.671 ms 54.875 ms 80.615 ms
5 202.50.245.193 56.333 ms 47.700 ms 59.317 ms
6 210.55.202.49 46.077 ms 44.843 ms 43.691 ms
7 210.55.202.52 46.584 ms 47.742 ms 49.511 ms
8 192.203.154.44 47.299 ms 48.212 ms 48.978 ms
9 210.48.5.69 46.334 ms 44.748 ms 47.645 ms
10 210.48.5.2 47.407 ms 45.407 ms 44.625 ms
11 210.48.5.102 45.549 ms 47.785 ms 44.934 ms
12 210.48.5.62 44.338 ms 45.567 ms 45.912 ms
---------------------
and for the bad one
----------
traceroute to 210.48.107.133 (210.48.107.133), 30 hops max, 40 byte packets
1 192.168.0.1 8.188 ms 3.770 ms 3.366 ms
2 * * *
3 125.237.192.1 47.109 ms 50.352 ms 47.644 ms
4 202.50.245.194 138.200 ms 244.105 ms 223.784 ms
5 202.50.245.193 55.620 ms 58.049 ms 52.843 ms
6 210.55.202.49 45.834 ms 48.482 ms 48.120 ms
7 210.55.202.52 44.291 ms 50.040 ms 44.152 ms
8 192.203.154.44 51.598 ms 45.702 ms 53.308 ms
9 210.48.5.69 47.007 ms 50.058 ms 44.117 ms
10 210.48.5.2 46.619 ms 47.477 ms 47.997 ms
11 210.48.5.102 46.138 ms 48.284 ms 54.770 ms
12 210.48.5.62 47.943 ms 48.694 ms 45.447 ms
------------------

beyond line 12 both just gave me ***

[MMooney]

have just configured the bad tivo to dhcp - will report on results

also just did a firmware upgrade on my router (hoping that might have some effect) - will see what happens

[MMooney]

Finally able to set aside a few hours today. Re-imaged the new tivo, swapped around some hardware .... and it would seem that there is some sort of connectivity issue between one of my network cards (the one in the bad tivo) and the router. it works intermittantly -and only when I have the other tivo turned off. When I try to ping this card, it responds about half the time. When I try to run GS with it, it can make the test call, but fails at the first real attempt to get data.

For the sake of all the hassle, unless anyone has an idea as to what might be causing this particular card to operate so oddly, I think I just need to get a new card (so would gladly take any thoughts on where I might find one in NZ - my supply is generally from the states).

thanks for the help - sorry took me so long to start swapping hardware around to be able to find the issue.