Joined
·
31 Posts
I received my 2nd USB-ethernet adapter today and shortly afterward Zipper'ed my 2nd DTivo. All went well in that process. I excitedly brought up the Now Playing List on the Family Room DTivo (DTivo A at IP 192.168.1.130) and tried to view the newly listed NP List of the Living Room DTivo (DTivo B at IP 192.168.1.120). No luck. I got the msg (abbreviated) "The Living Room DVR could not be reached because a connection could not be established."
Well, I know that DTivo B is available and on-line: I can ping it, TivoWebPlus it, and telnet to it. I thought that maybe it was because I had (incorrectly) chosen to install the USB 2.0 drivers when I ran tweak.sh. So I ran tweak_uninstall.sh on both boxes, re-tweak'ed (answering "n" to "Install USB 2.0 drivers?"), and re-booted. Still no luck w/MRV.
Then I telneted to DTivo B and ran "speed" to DTivo A. Here are the results:
Living Room-TiVo# speed
TCP STREAM TEST to 192.168.1.130
netperf: receive_response: no response received. errno 0 counter 0
This didn't look good. So I then telneted to DTivo A and ran "speed" the other way around:
Family Room-TiVo# speed
netperf: receive_response: no response received. errno 0 counter 0
Both are connected to the same switch (Linksys BEFSR41b running firmware version 1.46.02, Aug 03 2004) using generic USB 1.1 to ethernet adapters that I got from Weaknees. Admittedly the ethernet cables are homemade (i.e. I crimped the end connectors on myself), but they seemed to work fine for the initial run of telnet/tweak.sh on each box. So I decided to try PINGing one box from the other:
Here is from DTivo A to DTivo B:
Family Room-TiVo# ping 192.168.1.120
PING 192.168.1.120 (192.168.1.120): 56 data bytes
64 bytes from 192.168.1.120: icmp_seq=7 ttl=64 time=10.7 ms
64 bytes from 192.168.1.120: icmp_seq=20 ttl=64 time=3.7 ms
--- 192.168.1.120 ping statistics ---
62 packets transmitted, 2 packets received, 96% packet loss
round-trip min/avg/max = 3.7/7.2/10.7 ms
And from DTivo B to DTivo A:
Living Room-TiVo# ping 192.168.1.130
PING 192.168.1.130 (192.168.1.130): 56 data bytes
64 bytes from 192.168.1.130: icmp_seq=8 ttl=64 time=3.2 ms
64 bytes from 192.168.1.130: icmp_seq=15 ttl=64 time=3.5 ms
--- 192.168.1.130 ping statistics ---
30 packets transmitted, 2 packets received, 93% packet loss
round-trip min/avg/max = 3.2/3.3/3.5 ms
Interestingly enough, I can USUALLY ping both DTivos without problem from a Windows XP Pro box:
C:\>ping 192.168.1.120
Pinging 192.168.1.120 with 32 bytes of data:
Reply from 192.168.1.120: bytes=32 time=1ms TTL=64
Reply from 192.168.1.120: bytes=32 time=1ms TTL=64
Reply from 192.168.1.120: bytes=32 time=2ms TTL=64
Reply from 192.168.1.120: bytes=32 time=1ms TTL=64
Ping statistics for 192.168.1.120:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 2ms, Average = 1ms
C:\>ping 192.168.1.130
Pinging 192.168.1.130 with 32 bytes of data:
Reply from 192.168.1.130: bytes=32 time=2ms TTL=64
Reply from 192.168.1.130: bytes=32 time=1ms TTL=64
Reply from 192.168.1.130: bytes=32 time=1ms TTL=64
Reply from 192.168.1.130: bytes=32 time=1ms TTL=64
Ping statistics for 192.168.1.130:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 2ms, Average = 1ms
Admittedly I do have intermittent problems accessing the DTivos from the same PC (i.e. ping will reply inconsistently or the telnet session will die).
C:\Documents and Settings\Administrator>ping 192.168.1.130
Pinging 192.168.1.130 with 32 bytes of data:
Reply from 192.168.1.130: bytes=32 time=2ms TTL=64
Reply from 192.168.1.130: bytes=32 time=2ms TTL=64
Reply from 192.168.1.130: bytes=32 time=1ms TTL=64
Reply from 192.168.1.130: bytes=32 time=1ms TTL=64
Ping statistics for 192.168.1.130:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 2ms, Average = 1ms
C:\Documents and Settings\Administrator>ping 192.168.1.130
Pinging 192.168.1.130 with 32 bytes of data:
Request timed out.
Request timed out.
Reply from 192.168.1.130: bytes=32 time=1ms TTL=64
Reply from 192.168.1.130: bytes=32 time=1ms TTL=64
Ping statistics for 192.168.1.130:
Packets: Sent = 4, Received = 2, Lost = 2 (50% loss),
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 1ms, Average = 1ms
I can successfully use the HMO (Photos and Music) option to stream photos and music from one of my PCs to either DTivo A or DTivo B. That has exhibited no problems.
So...I seem to have some kind of connectivity problem. It seems to be worse between the 2 DTivos than between the DTivos and other PCs on my home LAN, but it does exist in both places. I have never had connectivity or noticeable data speed problems with the computers on my home LAN. I realize that this may be more of an ethernet hardware question than a TiVo/MRV question, but I wanted to pick the TCF group-brain first - since it is always very helpful.
Any ideas on next steps to take to debug this? Given the success that others have had with The Zipper, I have a hard time believing it is anything related to that and must be something hardware related.
Thanks.
Well, I know that DTivo B is available and on-line: I can ping it, TivoWebPlus it, and telnet to it. I thought that maybe it was because I had (incorrectly) chosen to install the USB 2.0 drivers when I ran tweak.sh. So I ran tweak_uninstall.sh on both boxes, re-tweak'ed (answering "n" to "Install USB 2.0 drivers?"), and re-booted. Still no luck w/MRV.
Then I telneted to DTivo B and ran "speed" to DTivo A. Here are the results:
Living Room-TiVo# speed
TCP STREAM TEST to 192.168.1.130
netperf: receive_response: no response received. errno 0 counter 0
This didn't look good. So I then telneted to DTivo A and ran "speed" the other way around:
Family Room-TiVo# speed
netperf: receive_response: no response received. errno 0 counter 0
Both are connected to the same switch (Linksys BEFSR41b running firmware version 1.46.02, Aug 03 2004) using generic USB 1.1 to ethernet adapters that I got from Weaknees. Admittedly the ethernet cables are homemade (i.e. I crimped the end connectors on myself), but they seemed to work fine for the initial run of telnet/tweak.sh on each box. So I decided to try PINGing one box from the other:
Here is from DTivo A to DTivo B:
Family Room-TiVo# ping 192.168.1.120
PING 192.168.1.120 (192.168.1.120): 56 data bytes
64 bytes from 192.168.1.120: icmp_seq=7 ttl=64 time=10.7 ms
64 bytes from 192.168.1.120: icmp_seq=20 ttl=64 time=3.7 ms
--- 192.168.1.120 ping statistics ---
62 packets transmitted, 2 packets received, 96% packet loss
round-trip min/avg/max = 3.7/7.2/10.7 ms
And from DTivo B to DTivo A:
Living Room-TiVo# ping 192.168.1.130
PING 192.168.1.130 (192.168.1.130): 56 data bytes
64 bytes from 192.168.1.130: icmp_seq=8 ttl=64 time=3.2 ms
64 bytes from 192.168.1.130: icmp_seq=15 ttl=64 time=3.5 ms
--- 192.168.1.130 ping statistics ---
30 packets transmitted, 2 packets received, 93% packet loss
round-trip min/avg/max = 3.2/3.3/3.5 ms
Interestingly enough, I can USUALLY ping both DTivos without problem from a Windows XP Pro box:
C:\>ping 192.168.1.120
Pinging 192.168.1.120 with 32 bytes of data:
Reply from 192.168.1.120: bytes=32 time=1ms TTL=64
Reply from 192.168.1.120: bytes=32 time=1ms TTL=64
Reply from 192.168.1.120: bytes=32 time=2ms TTL=64
Reply from 192.168.1.120: bytes=32 time=1ms TTL=64
Ping statistics for 192.168.1.120:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 2ms, Average = 1ms
C:\>ping 192.168.1.130
Pinging 192.168.1.130 with 32 bytes of data:
Reply from 192.168.1.130: bytes=32 time=2ms TTL=64
Reply from 192.168.1.130: bytes=32 time=1ms TTL=64
Reply from 192.168.1.130: bytes=32 time=1ms TTL=64
Reply from 192.168.1.130: bytes=32 time=1ms TTL=64
Ping statistics for 192.168.1.130:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 2ms, Average = 1ms
Admittedly I do have intermittent problems accessing the DTivos from the same PC (i.e. ping will reply inconsistently or the telnet session will die).
C:\Documents and Settings\Administrator>ping 192.168.1.130
Pinging 192.168.1.130 with 32 bytes of data:
Reply from 192.168.1.130: bytes=32 time=2ms TTL=64
Reply from 192.168.1.130: bytes=32 time=2ms TTL=64
Reply from 192.168.1.130: bytes=32 time=1ms TTL=64
Reply from 192.168.1.130: bytes=32 time=1ms TTL=64
Ping statistics for 192.168.1.130:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 2ms, Average = 1ms
C:\Documents and Settings\Administrator>ping 192.168.1.130
Pinging 192.168.1.130 with 32 bytes of data:
Request timed out.
Request timed out.
Reply from 192.168.1.130: bytes=32 time=1ms TTL=64
Reply from 192.168.1.130: bytes=32 time=1ms TTL=64
Ping statistics for 192.168.1.130:
Packets: Sent = 4, Received = 2, Lost = 2 (50% loss),
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 1ms, Average = 1ms
I can successfully use the HMO (Photos and Music) option to stream photos and music from one of my PCs to either DTivo A or DTivo B. That has exhibited no problems.
So...I seem to have some kind of connectivity problem. It seems to be worse between the 2 DTivos than between the DTivos and other PCs on my home LAN, but it does exist in both places. I have never had connectivity or noticeable data speed problems with the computers on my home LAN. I realize that this may be more of an ethernet hardware question than a TiVo/MRV question, but I wanted to pick the TCF group-brain first - since it is always very helpful.
Any ideas on next steps to take to debug this? Given the success that others have had with The Zipper, I have a hard time believing it is anything related to that and must be something hardware related.
Thanks.