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

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

<channel>
<title>Re: Odd... in </title>
<link>http://www.dslreports.com/forum/r22486344</link>
<description></description>
<language>en</language>
<pubDate>Sat, 28 Nov 2009 16:49:35 EDT</pubDate>
<lastBuildDate>Sat, 28 Nov 2009 16:49:35 EDT</lastBuildDate>

<item>
<title>Re: Odd...</title>
<link>http://www.dslreports.com/forum/remark,22486344</link>
<description><![CDATA[<A HREF="/useremail/u/1387637"><b>44402812</b></A> : <div class="bquote"><small>said by  ptrowski <A HREF="/useremail/u/1173383"><IMG SRC="http://i.dslr.net/bb/profile.gif" ALT="See Profile" BORDER=0 WIDTH=16 HEIGHT=11></A> :</small><br><br>You removed the part about how the adapter died and they had to send you a new device?<br> </div>Yeah because the HT-502 was not the issue if you look in this thread:<br>&raquo;<A HREF="/forum/r22415712-Update-caused-HT502-to-go-down">Update caused HT-502 to go down</A><br>you will see how I mentioned it is Verizon causing the issues by cycling my dynamic IP so often thus invalidating my registration.  Which was causing my hardware to lockup sporadically when the device pulls a profile every week.  However without the new HT-502 to troubleshoot the issues we could not eliminate it as a problem.  Verizon wants me to pay 70.00 for a business account.  So instead I'm working on my own fix to develop a mechanism which will reboot the HT-502 when the internet goes down. ]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,22486344</guid>
<pubDate>Tue, 02 Jun 2009 22:21:49 EDT</pubDate>
</item>

<item>
<title>Odd...</title>
<link>http://www.dslreports.com/forum/remark,22486198</link>
<description><![CDATA[<A HREF="/useremail/u/1173383"><b>ptrowski</b></A> : You removed the part about how the adapter died and they had to send you a new device?]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,22486198</guid>
<pubDate>Tue, 02 Jun 2009 21:55:23 EDT</pubDate>
</item>

</channel>
</rss>
