<?xml version="1.0" encoding="UTF-8"?>

<rss version="2.0" xmlns:blogChannel="http://backend.userland.com/blogChannelModule">

<channel>
<title>A cautionary tale: NEVER ASSUME! in Covad / covad.net</title>
<link>http://www.dslreports.com/forum/r22086298</link>
<description></description>
<language>en</language>
<pubDate>Wed, 10 Feb 2010 00:58:08 EDT</pubDate>
<lastBuildDate>Wed, 10 Feb 2010 00:58:08 EDT</lastBuildDate>

<item>
<title>Re: A cautionary tale: NEVER ASSUME!</title>
<link>http://www.dslreports.com/forum/remark,22106788</link>
<description><![CDATA[<A HREF="/useremail/u/372021"><b>Doctor Olds</b></A> : I did <A HREF="http://www.dslreports.com/forum/r22088333-">mention</a> to look for chew marks. ;)]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,22106788</guid>
<pubDate>Sat, 21 Mar 2009 15:12:08 EDT</pubDate>
</item>

<item>
<title>Re: A cautionary tale: NEVER ASSUME!</title>
<link>http://www.dslreports.com/forum/remark,22105853</link>
<description><![CDATA[<A HREF="/useremail/u/436079"><b>DrStrange</b></A> : Update:<br><br>I replaced the 'home run' yesterday.  Either it got shredded by wind stress where it ran in an attic vent or something was chewing on it.  I replaced the CAT3 with CAT5 and re-routed the run to minimize wind stress and possible critter-chewing. We'll see what happens. If anything messes with the CAT5 I'll have to have a CAT1 [furry, four paws, pointed ears, long tail, nice sharp carnivore teeth...] deal with it.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,22105853</guid>
<pubDate>Sat, 21 Mar 2009 11:07:53 EDT</pubDate>
</item>

<item>
<title>A cautionary tale: NEVER ASSUME!</title>
<link>http://www.dslreports.com/forum/remark,22086298</link>
<description><![CDATA[<A HREF="/useremail/u/436079"><b>DrStrange</b></A> : I came home this afternoon to no Internet. It looked exactly the same as the infamous botched hardware migration last year.<br><br>I called my ISPs [Stephouse Networks] Tech support [waited about 5 seconds for a US-based tech to answer]. He checked my port status and started a trouble ticket with Covad.<br><br>What did I forget to do here? In my considerable agitation at losing sync, I jumped over conclusions and ASSUMED that since nothing had [apparently] changed on my end, the trouble must be external. I ASSUMED that there was a hardware problem at the CO [Gods forfend, another botched migration!] or trouble with the NYC access concentrator as there apparently was in California, or trouble with a DSLAM as there was in Chicago. I ASSUMED the trouble was external and didn't do the first thing I would have done if a customer reported a DSL outage: Before you call the ISP, CHECK FOR SYNC AT THE NID!<br><br>It was after I'd called Stephouse and heard that there were no other issues reported in my area [or in NYC] that I thought to check for sync at the NID. Lo and behold, there was sync!  I called them back, cancelled the trouble ticket, and wiped the egg off my face.<br><br>Since I had working voice and DSL at the NID, I went back outside with a surface mount phone jack, some alligator clips and a $6 phone. I checked for dialtone at the data terminals of the splitter. Yes, we had dialtone. I went inside and checked at the DSL jack [shame on me for not testing this either!] and there was no dialtone. It turned out that the one of the wires in my 'home run' connection had failed. I switched the data wiring from GR to BY and voil&agrave;! On came the green light!<br><br>The moral of this story:<br><br>Just because you didn't touch any of your home wiring doesn't mean it won't pick some time when you least expect it to mysteriously and unobtrusively fail.<br><br>PS: Very special thanks to Stephouse for having US-based support with patience to deal with slightly neurotic IT consultants.<br><br>I think I'll go shower and get the rest of that egg off now.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,22086298</guid>
<pubDate>Tue, 17 Mar 2009 22:11:39 EDT</pubDate>
</item>

</channel>
</rss>
