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

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

<channel>
<title>Topic &#x27;Suddenlink network issues?&#x27; in forum &#x27;Suddenlink&#x27; - dslreports.com</title>
<link>http://www.dslreports.com/forum/Suddenlink-network-issues-23253518</link>
<description></description>
<language>en</language>
<pubDate>Fri, 10 Feb 2012 15:28:02 EDT</pubDate>
<lastBuildDate>Fri, 10 Feb 2012 15:28:02 EDT</lastBuildDate>

<item>
<title>Suddenlink network issues?</title>
<link>http://www.dslreports.com/forum/Suddenlink-network-issues-23253518</link>
<description><![CDATA[autosync posted : I had a customer call this morning complaining that the internet connection was down at their office. I had him unplug the cable modem from power and reboot the firewall to fix. In the mean time, I drop out and do a tracert to their IP and I get 10.17.***.*** as my second hop and nothing but timeouts beyond that.  I could still access the internet as could he now after rebooting the above. I had him test and he received the same response.  Why are we seeing the internal addresses assigned to the cable modems on suddenlinks network? <br><br>I could even access the cable modems through that whole subnet using the browser.  What's going on?]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Suddenlink-network-issues-23253518</guid>
<pubDate>Wed, 28 Oct 2009 09:56:05 EDT</pubDate>
</item>

</channel>
</rss>

