Help. Zippered DTiVo stopped talking to network

[Jonathan_S]

I have a pair of zippered DTiVos, which had been working fine for almost a year now. But a few days ago the house lost power for a few minutes, and one of the DTiVos wouldn't connect to the network after power was restored. (Unfortunately that DTiVo wasn't hooked up to a UPS)

They both have Netgear FA-120 adaptors, and the DTiVo that won't connect to the network otherwise appears to be working fine. On that DTiVo's FA-120 the power and link lights are on, and I tried swapping it out for a spare FA-120 and also tried using the other USB port, but didn't have any luck.



Yesterday I hooked up the serial cable, and checked out the boot log.
When I compared it to the log on the DTiVo that still is on the network I noticed some significant differences.

The networked DTiVo had numerous lines from 'usb.c', 'ehci_hcd', 'hub.c', 'usb-ohci.c', 'eth0' all appearing to more or less relate to finding the USB, finding the FA-120, and initializing the network.
The DTiVo that won't get on the network had only 1 line from 'usb.c' and no lines from 'ehci_hcd', 'hub.c', 'usb-ohci.c', or 'eth0'.
That suggests to me that for some reason that DTiVo isn't finding the adaptor, and that is why it isn't on the network.

Does anybody have suggestions for how to get that DTiVo to find and use the FA-120 again?

[BTUx9]

is the tivo still hacked? (are 30-second skip and backdoors still enabled?)
can you get a bash prompt with the serial?
have you tried manually using insmod to get the usb/network modules loaded?
what does it say if you type "ifconfig"?

[Jonathan_S]

is the tivo still hacked? (are 30-second skip and backdoors still enabled?)
can you get a bash prompt with the serial?
have you tried manually using insmod to get the usb/network modules loaded?
what does it say if you type "ifconfig"?
Yes, the TiVo is still hacked.
Yes, I was able to get the bash prompt with the serial cable.
No, I didn't try to use insmod. (I'm not sure I even know exactly how to do that)

ifconfig output:
bash-2.02# ifconfig
lo Link encap:Local Loopback
inet addr:127.0.0.1 Bcast:0.0.0.0 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:4 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:380 dropped:4 overruns:0 carrier:0 coll:0

eth0 Link encap:Ethernet HWaddr 00:0F:B5:89:2B:A7
inet addr:192.168.2.52 Bcast:192.168.2.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:3170 dropped:36 overruns:0 carrier:0 coll:0
I assume the loopback part is irrelevant. For eth0 I confirmed that the IP, Bcast, and netmask were correct.

[BTUx9]

can you ping your PC FROM your tivo? (that ifconfig output looks like networking is up, though not receiving properly (and there were xmit errors))

tried rebooting your hub/switch/router?
have you tried replacing the cable?

[Jonathan_S]

Figured out the problem. It wasn't the TiVo at all.

It turns out that one port on the little 5 port switch I'm using failed somehow. Traffic couldn't pass through it (no pings, etc), even though it appeared to have a good 100 mbit connection. (The other ports including the one my 2nd DTiVo was on were working fine)

I don't know why the boot log of the TiVo appeared to show that the adapter hadn't initialized, because I rebooted it and it did detect the FA-120.

Finally realized it after looking at the new boot log, and then hooking up a laptop to the connection to see if that could connect. (And if I hadn't seen what I thought was the failure in that boot log I would have moved on to double-checking the connection before posting here. Oh well)

Anyway, I've temporarily switch that DTiVo to one of the free ports, and as soon as I get a chance I'll swap out the defective switch.


Thanks for the help.

[rlistenb]

Ok... Yes I'm a newbie.

That said... I have successfully zippered my existing drive (and a new one to make sure I wouldn't screw up my existing).

Now the problem is that I can telnet to it to run the scripts! I am using a Netgear MA101 rev.B (which is on the list of working adapters). This is a wireless B adapter.

I can't even ping the static IP I assigned the tivo during the zipper installation. What I've done to try and diagnose so far....

* tried the MA101 on another pc to ensure it works
* checked my wireless router to ensure dhcp is off
* checked my router to ensure wep is off
* checked my router to ensure it IS running in wireless "B" mode only
* restarted my tivo
* restarted my router


This is a Samsung D-Tivo, series 2 with 6.2 software.

ANY ideas . . . Please?

[rbautch]

Ok... Yes I'm a newbie.

That said... I have successfully zippered my existing drive (and a new one to make sure I wouldn't screw up my existing).

Now the problem is that I can telnet to it to run the scripts! I am using a Netgear MA101 rev.B (which is on the list of working adapters). This is a wireless B adapter.

I can't even ping the static IP I assigned the tivo during the zipper installation. What I've done to try and diagnose so far....

* tried the MA101 on another pc to ensure it works
* checked my wireless router to ensure dhcp is off
* checked my router to ensure wep is off
* checked my router to ensure it IS running in wireless "B" mode only
* restarted my tivo
* restarted my router


This is a Samsung D-Tivo, series 2 with 6.2 software.

ANY ideas . . . Please?Is the link light on the adapter lit up? Did you turn off your windows (or other) firewall? Is the IP you chose out of the range of DHCP addresses assigned by your router? Can you get serial bash? Do you have another adapter you can temporarily connect with?

[rlistenb]

The link light is lit, but apparently it lights up when simply powered up and sees the wireless network (connectivity not required).

Windows firewall is OFF. Router firewall is temporarily OFF (just in case).

The IP is in range of DHCP, but I've tried it with DHCP ON and OFF in the router with no luck either way.

I do not have a serial conn (guess I will have to order one now!), nor do I have any other compatible USB Wireless LAN Device.

Thanks for the reply! Any additional thoughts or ideas, from anybody?

Here are the only entries in my router security log having anything to do with my DTivo IP

06/11/2007 22:43:54 sending ACK to 192.168.2.5
06/11/2007 22:43:54 sending OFFER to 192.168.2.5

[JWThiers]

The link light is lit, but apparently it lights up when simply powered up and sees the wireless network (connectivity not required).

Windows firewall is OFF. Router firewall is temporarily OFF (just in case).

The IP is in range of DHCP, but I've tried it with DHCP ON and OFF in the router with no luck either way.

I do not have a serial conn (guess I will have to order one now!), nor do I have any other compatible USB Wireless LAN Device.

Thanks for the reply! Any additional thoughts or ideas, from anybody?

Here are the only entries in my router security log having anything to do with my DTivo IP

06/11/2007 22:43:54 sending ACK to 192.168.2.5
06/11/2007 22:43:54 sending OFFER to 192.168.2.5
A lot of good adice in the wiki (see my sig). Try the troubleshooting page.

[fredfillis]

Figured out the problem. It wasn't the TiVo at all.

It turns out that one port on the little 5 port switch I'm using failed somehow. Traffic couldn't pass through it (no pings, etc), even though it appeared to have a good 100 mbit connection. (The other ports including the one my 2nd DTiVo was on were working fine)

I don't know why the boot log of the TiVo appeared to show that the adapter hadn't initialized, because I rebooted it and it did detect the FA-120.

Finally realized it after looking at the new boot log, and then hooking up a laptop to the connection to see if that could connect. (And if I hadn't seen what I thought was the failure in that boot log I would have moved on to double-checking the connection before posting here. Oh well)

Anyway, I've temporarily switch that DTiVo to one of the free ports, and as soon as I get a chance I'll swap out the defective switch.


Thanks for the help.
Jonathan_S, I just had the exact same problem in the same circumstance!

I have two units and I'd swapped just about everything I could and was about to open the box and "re-customize" when I spotted your post and solution. My switch had also failed, just one port. A trip to Best Buy and $25 later, all is good.

Moral of the story, don't forget to check the obvious!