<div class="gmail_quote">On Sun, Jan 10, 2010 at 9:36 AM, Brian Wood <span dir="ltr"><<a href="mailto:beww@beww.org">beww@beww.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
I'd also suggest that a visual inspection is not sufficient, you need to make an<br>
electrical test of the cable, and make sure that the proper "natural pairs"<br>
are used properly, merely having continuity does not prove the cable is<br>
"good", you might have split pairs, or even shorts between conductors that<br>
would not show up in a simple continuity test, after all, if all the<br>
conductors were connected to each other you would have "good" continuity.<br>
<br>
Probably the easiest way to test a cable is by substitution with a known good<br>
one.<br>
<div><div></div><div class="h5"><br><br></div></div></blockquote><div><br>Thanks Brian, I did "test" the cable. When I was trying to understand the problem I just moved the cable from the built-in ethernet port to the USB-to-ethernet device and got no errors with it this way and the myth content was smooth. At this point and with the help of mythtv-users I think we've proved that the network port was bunged up.<br>
<br>-Greg<br></div></div><br>