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

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

<channel>
<title>Topic &#x27;Re: [Modem] Arris S33 Issue&#x27; in forum &#x27;Cox&#x27; - dslreports.com</title>
<link>http://www.dslreports.com/forum/Re-Modem-Arris-S33-Issue-33377839</link>
<description></description>
<language>en</language>
<pubDate>Sat, 23 Apr 2022 11:58:49 EDT</pubDate>
<lastBuildDate>Sat, 23 Apr 2022 11:58:49 EDT</lastBuildDate>

<item>
<title>Re: [Modem] Arris S33 Issue</title>
<link>http://www.dslreports.com/forum/Re-Modem-Arris-S33-Issue-33385861</link>
<description><![CDATA[ccsprague posted : taffeys, has it continued to try and update after odog’s team fixed it? I miss that S33 and if low latency is a future item, I want to go pick one back up. ]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-Modem-Arris-S33-Issue-33385861</guid>
<pubDate>Fri, 22 Apr 2022 02:15:16 EDT</pubDate>
</item>
<item>
<title>Re: [Modem] Arris S33 Issue</title>
<link>http://www.dslreports.com/forum/Re-Modem-Arris-S33-Issue-33381670</link>
<description><![CDATA[Mike Wolf posted : From the log, it looks like the upstream diplexer was switched to 5-85 mode for mid-split rollout prep. Very cool.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-Modem-Arris-S33-Issue-33381670</guid>
<pubDate>Sat, 16 Apr 2022 01:26:24 EDT</pubDate>
</item>
<item>
<title>Re: [Modem] Arris S33 Issue</title>
<link>http://www.dslreports.com/forum/Re-Modem-Arris-S33-Issue-33381669</link>
<description><![CDATA[Mike Wolf posted : <div class="bquote"><said>said by <a href="/profile/445048" onClick="this.blur(); return popup(event,'/uidpop?ajh=1&uid=445048');">odog</a>:</said><p>Can one of you send me a MAC via DM?  We're actually testing a new S33 firmware right now, which is an optimistic sign.<br></p></div>Is testing still being performed for rollout or has the urgency been slowed since the looping issue was resolved? I’m curious what changes that update brings. I know the release notes are confidential so you can’t tell us unfortunately.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-Modem-Arris-S33-Issue-33381669</guid>
<pubDate>Sat, 16 Apr 2022 01:24:37 EDT</pubDate>
</item>
<item>
<title>Re: [Modem] Arris S33 Issue</title>
<link>http://www.dslreports.com/forum/Re-Modem-Arris-S33-Issue-33381506</link>
<description><![CDATA[lilstone87 posted : Honestly the whole password thing some people want to make a big deal about is silly. Because guess what? Mostly everyone also has a router, which also requires a password on setup. Overall a non issue, some people want to mention. You're right there's many docsis modems that have this included in the firmware now.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-Modem-Arris-S33-Issue-33381506</guid>
<pubDate>Fri, 15 Apr 2022 18:49:38 EDT</pubDate>
</item>
<item>
<title>Re: [Modem] Arris S33 Issue</title>
<link>http://www.dslreports.com/forum/Re-Modem-Arris-S33-Issue-33381439</link>
<description><![CDATA[Mike Wolf posted : Yup. As you well know, the password requirement has been in place since at least 2019 and so far the SB6190, SB8200, S33, and T25 have since received firmware updates to bring them into compliance.<br><br>SB6190 &raquo;<A HREF="https://arris.secure.force.com/consumers/articles/General_FAQs/SB6190-Web-Manager-Access/?l=en_US&fs=RelatedArticle" >arris.secure.force.com/c &middot;&middot;&middot; dArticle</A><br>SB8200 &raquo;<A HREF="https://arris.secure.force.com/consumers/articles/General_FAQs/SB8200-Web-Manager-Access/?l=en_US&fs=RelatedArticle" >arris.secure.force.com/c &middot;&middot;&middot; dArticle</A><br>S33 &raquo;<A HREF="https://arris.secure.force.com/consumers/articles/General_FAQs/S33-Web-Manager-Access/?l=en_US&fs=RelatedArticle" >arris.secure.force.com/c &middot;&middot;&middot; dArticle</A><br>T25 &raquo;<A HREF="https://arris.secure.force.com/consumers/articles/General_FAQs/T25-Web-Manager-Access/?l=en_US&fs=RelatedArticle" >arris.secure.force.com/c &middot;&middot;&middot; dArticle</A>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-Modem-Arris-S33-Issue-33381439</guid>
<pubDate>Fri, 15 Apr 2022 16:08:39 EDT</pubDate>
</item>
<item>
<title>Re: [Modem] Arris S33 Issue</title>
<link>http://www.dslreports.com/forum/Re-Modem-Arris-S33-Issue-33381270</link>
<description><![CDATA[nope22 posted : Just manually rebooted.<br>I see some entries in the event log that I haven't seen before the new firmware.<br>I am on the Cox preferred plan that recently got the free bump from 150Mbps to 250Mbps.  With the previous firmware I got around 290Mbps down/10Mbps with really stable jitter and almost no packet loss.  Jitter and packet loss were jumping all around today but it may be unrelated to the firmware.<br><br>I have orange RG11 from Cox to grounded demarc, then about 50ft of RG6 outdoor to a coupler (splitter removed, no more TVs on coax) to in-house wall jack to modem.<br><br><pre class="brush: text">31/12/1969&#012;20:00:16	3	CMSTATUS:US_Diplexer_Mode_Change:Init, 5-42MHz.&#012;31/12/1969&#012;20:00:19	3	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;&#012;31/12/1969&#012;20:00:22	3	CMSTATUS:DS_Diplexer_Mode_Change_Ignored:TLV-21.2, 108MHz.&#012;31/12/1969&#012;20:00:22	3	CMSTATUS:DS_Diplexer_Mode_Change_Ignored:TLV-21.3, 1002MHz.&#012;31/12/1969&#012;20:00:22	3	CMSTATUS:US_Diplexer_Mode_Change_Ignored:TLV-21.1, 42MHz.&#012;31/12/1969&#012;20:00:29	6	Honoring MDD; IP provisioning mode = IPv4&#012;31/12/1969&#012;20:00:31	5	DHCP WARNING - Non-critical field invalid in response ;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=f8:b7:e2:05:81:cb;CM-QOS=1.1;CM-VER=3.1;&#012;15/4/2022&#012;12:14:39	3	CMSTATUS:US_Diplexer_Mode_Change:Other, 5-85MHz.&#012;15/4/2022&#012;12:14:39	6	TLV-11 - unrecognized OID;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=f8:b7:e2:05:81:cb;CM-QOS=1.1;CM-VER=3.1;&#012;15/4/2022&#012;12:14:44	6	DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=f8:b7:e2:05:81:cb;CM-QOS=1.1;CM-VER=3.1;&#012;15/4/2022&#012;12:14:50	5	REG-RSP-MP Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=f8:b7:e2:05:81:cb;CM-QOS=1.1;CM-VER=3.1;&#012;15/4/2022&#012;12:16:52	3	Successful LAN WebGUI login from xx.xx.xx.xx on 22/04/15 at 12:16 PM.&#012; &#012;</pre><!--end code block--><br><pre class="brush: text">Downstream Bonded Channels&#012;Channel ID	Lock Status	Modulation	Frequency	Power	SNR/MER	Corrected	Uncorrectables&#012;29	Locked	QAM256	843000000 Hz	-7 dBmV	36 dB	0	0&#012;1	Locked	QAM256	675000000 Hz	-5 dBmV	37 dB	0	0&#012;2	Locked	QAM256	681000000 Hz	-5 dBmV	37 dB	0	0&#012;3	Locked	QAM256	687000000 Hz	-5 dBmV	37 dB	0	0&#012;4	Locked	QAM256	693000000 Hz	-5 dBmV	37 dB	0	0&#012;5	Locked	QAM256	699000000 Hz	-5 dBmV	37 dB	0	0&#012;6	Locked	QAM256	705000000 Hz	-5 dBmV	38 dB	0	0&#012;7	Locked	QAM256	711000000 Hz	-4 dBmV	38 dB	0	0&#012;8	Locked	QAM256	717000000 Hz	-4 dBmV	38 dB	0	0&#012;9	Locked	QAM256	723000000 Hz	-4 dBmV	38 dB	0	0&#012;10	Locked	QAM256	729000000 Hz	-4 dBmV	38 dB	0	0&#012;11	Locked	QAM256	735000000 Hz	-4 dBmV	38 dB	0	0&#012;12	Locked	QAM256	741000000 Hz	-5 dBmV	38 dB	0	0&#012;13	Locked	QAM256	747000000 Hz	-4 dBmV	38 dB	0	0&#012;14	Locked	QAM256	753000000 Hz	-5 dBmV	37 dB	0	0&#012;15	Locked	QAM256	759000000 Hz	-5 dBmV	38 dB	0	0&#012;16	Locked	QAM256	765000000 Hz	-5 dBmV	38 dB	0	0&#012;17	Locked	QAM256	771000000 Hz	-5 dBmV	37 dB	0	0&#012;18	Locked	QAM256	777000000 Hz	-6 dBmV	37 dB	0	0&#012;19	Locked	QAM256	783000000 Hz	-6 dBmV	37 dB	0	0&#012;20	Locked	QAM256	789000000 Hz	-6 dBmV	37 dB	0	0&#012;21	Locked	QAM256	795000000 Hz	-6 dBmV	37 dB	0	0&#012;22	Locked	QAM256	801000000 Hz	-6 dBmV	37 dB	0	0&#012;23	Locked	QAM256	807000000 Hz	-6 dBmV	37 dB	0	0&#012;24	Locked	QAM256	813000000 Hz	-6 dBmV	36 dB	0	0&#012;25	Locked	QAM256	819000000 Hz	-6 dBmV	36 dB	0	0&#012;26	Locked	QAM256	825000000 Hz	-6 dBmV	36 dB	0	0&#012;27	Locked	QAM256	831000000 Hz	-6 dBmV	36 dB	0	0&#012;28	Locked	QAM256	837000000 Hz	-6 dBmV	36 dB	0	0&#012;30	Locked	QAM256	849000000 Hz	-7 dBmV	37 dB	0	0&#012;31	Locked	QAM256	855000000 Hz	-7 dBmV	37 dB	0	0&#012;32	Locked	QAM256	861000000 Hz	-7 dBmV	37 dB	0	0&#012;159	Locked	OFDM PLC	288000000 Hz	0 dBmV	40 dB	4561136	0&#012; &#012;Upstream Bonded Channels&#012;Channel ID	Lock Status	US Channel Type	Frequency	Width	Power&#012;1	Locked	SC-QAM	17400000 Hz	6400000	42.8 dBmV&#012;2	Locked	SC-QAM	23900000 Hz	6400000	43.3 dBmV&#012;3	Locked	SC-QAM	30300000 Hz	6400000	44.3 dBmV&#012;4	Locked	SC-QAM	36700000 Hz	6400000	42.8 dBmV&#012; &#012;Current System Time:Fri Apr 15 12:25:40 2022&#012; &#012;</pre><!--end code block-->]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-Modem-Arris-S33-Issue-33381270</guid>
<pubDate>Fri, 15 Apr 2022 12:42:05 EDT</pubDate>
</item>
<item>
<title>Re: [Modem] Arris S33 Issue</title>
<link>http://www.dslreports.com/forum/Re-Modem-Arris-S33-Issue-33381231</link>
<description><![CDATA[odog posted : The looping should be resolved.  It was repeatedly attempting to push firmware over and over due to misconfiguration.  I had the deployment team fix that.<br><br>The password issue is Arris implementing a California law that requires unique or on first boot password changes.  Arris should be aware of that since every product has that "feature" or will in the near future.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-Modem-Arris-S33-Issue-33381231</guid>
<pubDate>Fri, 15 Apr 2022 11:47:01 EDT</pubDate>
</item>
<item>
<title>Re: [Modem] Arris S33 Issue</title>
<link>http://www.dslreports.com/forum/Re-Modem-Arris-S33-Issue-33381076</link>
<description><![CDATA[nope22 posted : I just got TB01.03.001.10_012022_212.S3. Now IPv6 is broken.<br>Is this some beta version of firmware that was not meant to be put into production?]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-Modem-Arris-S33-Issue-33381076</guid>
<pubDate>Fri, 15 Apr 2022 05:07:18 EDT</pubDate>
</item>
<item>
<title>Re: [Modem] Arris S33 Issue</title>
<link>http://www.dslreports.com/forum/Re-Modem-Arris-S33-Issue-33380204</link>
<description><![CDATA[Mike Wolf posted : Cox really messed up giving you the blatantly wrong information and honestly there’s no excuse for it. I don’t know what else you would have expected from Arris. They don’t push out firmware updates to their modems directly and they were right for pointing the finger at Cox. They stopped responding to you because there was literally nothing else for them to say.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-Modem-Arris-S33-Issue-33380204</guid>
<pubDate>Thu, 14 Apr 2022 01:14:19 EDT</pubDate>
</item>
<item>
<title>Re: [Modem] Arris S33 Issue</title>
<link>http://www.dslreports.com/forum/Re-Modem-Arris-S33-Issue-33380179</link>
<description><![CDATA[ccsprague posted : <div class="bquote"><said>said by Anoncc163 :</said><p>“Oh just avoid the issue by getting a different modem” 🙄<br></p></div>Considering I spent nearly a week going back and forth between Cox and Arris being their middleman? And the fact that the arris tech simply stopped responding to me? Yeah no. They’re on my shitlist for the foreseeable future. ]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-Modem-Arris-S33-Issue-33380179</guid>
<pubDate>Wed, 13 Apr 2022 23:40:01 EDT</pubDate>
</item>
<item>
<title>Re: [Modem] Arris S33 Issue</title>
<link>http://www.dslreports.com/forum/Re-Modem-Arris-S33-Issue-33380162</link>
<description><![CDATA[anon posted : Please let us know the cause of the issue. Is it a problem on the Cox CMTS, or is it a problem with the modem software, or is it a configuration issue between the two?  Want to make sure it’s not going to affect Comcast customers as well, and if it does that we can notify their engineers.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-Modem-Arris-S33-Issue-33380162</guid>
<pubDate>Wed, 13 Apr 2022 23:08:01 EDT</pubDate>
</item>
<item>
<title>Re: [Modem] Arris S33 Issue</title>
<link>http://www.dslreports.com/forum/Re-Modem-Arris-S33-Issue-33380154</link>
<description><![CDATA[anon posted : “Oh just avoid the issue by getting a different modem” 🙄]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-Modem-Arris-S33-Issue-33380154</guid>
<pubDate>Wed, 13 Apr 2022 22:55:41 EDT</pubDate>
</item>
<item>
<title>Re: [Modem] Arris S33 Issue</title>
<link>http://www.dslreports.com/forum/Re-Modem-Arris-S33-Issue-33379957</link>
<description><![CDATA[taffeys posted : Done.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-Modem-Arris-S33-Issue-33379957</guid>
<pubDate>Wed, 13 Apr 2022 18:30:42 EDT</pubDate>
</item>
<item>
<title>Re: [Modem] Arris S33 Issue</title>
<link>http://www.dslreports.com/forum/Re-Modem-Arris-S33-Issue-33379605</link>
<description><![CDATA[odog posted : Can one of you send me a MAC via DM?  We're actually testing a new S33 firmware right now, which is an optimistic sign.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-Modem-Arris-S33-Issue-33379605</guid>
<pubDate>Wed, 13 Apr 2022 12:35:40 EDT</pubDate>
</item>
<item>
<title>Re: [Modem] Arris S33 Issue</title>
<link>http://www.dslreports.com/forum/Re-Modem-Arris-S33-Issue-33378360</link>
<description><![CDATA[taffeys posted : I didn't see that thread. Yes, it is the same firmware and I have experienced some of the same issues reported there. However, Cox did approve it and pushed it. In my book that makes Cox responsible for any and all new issues. ]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-Modem-Arris-S33-Issue-33378360</guid>
<pubDate>Mon, 11 Apr 2022 22:21:09 EDT</pubDate>
</item>
<item>
<title>Re: [Modem] Arris S33 Issue</title>
<link>http://www.dslreports.com/forum/Re-Modem-Arris-S33-Issue-33378330</link>
<description><![CDATA[ccsprague posted : &raquo;<A HREF="/forum/r33357605-Firmware-Arris-S33-New-firmware">[Firmware] Arris S33 - New firmware?</A><br><br>They’ve got the same firmware we’ve got.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-Modem-Arris-S33-Issue-33378330</guid>
<pubDate>Mon, 11 Apr 2022 21:38:00 EDT</pubDate>
</item>
<item>
<title>Re: [Modem] Arris S33 Issue</title>
<link>http://www.dslreports.com/forum/Re-Modem-Arris-S33-Issue-33378322</link>
<description><![CDATA[taffeys posted : <div class="bquote"><said>said by <a href="/profile/2003473" onClick="this.blur(); return popup(event,'/uidpop?ajh=1&uid=2003473');">ccsprague</a>:</said><p>So this is definitely something on Cox’s end? How could that be when it’s the same firmware and the Comcast guys aren’t having any issues? Maybe an issue where it keeps checking to see if a modem has an updated firmware?<br></p></div>How do you know it's the same firmware now on Cox and Comcast? Arris (CommScope) provided the new S33 firmware to Cox for testing/evaluation and Cox had to approve it for use on their network before they pushed it to customer's S33 modems.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-Modem-Arris-S33-Issue-33378322</guid>
<pubDate>Mon, 11 Apr 2022 21:28:27 EDT</pubDate>
</item>
<item>
<title>Re: [Modem] Arris S33 Issue</title>
<link>http://www.dslreports.com/forum/Re-Modem-Arris-S33-Issue-33378150</link>
<description><![CDATA[ccsprague posted : So this is definitely something on Cox’s end? How could that be when it’s the same firmware and the Comcast guys aren’t having any issues? Maybe an issue where it keeps checking to see if a modem has an updated firmware?]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-Modem-Arris-S33-Issue-33378150</guid>
<pubDate>Mon, 11 Apr 2022 17:45:05 EDT</pubDate>
</item>
<item>
<title>Re: [Modem] Arris S33 Issue</title>
<link>http://www.dslreports.com/forum/Re-Modem-Arris-S33-Issue-33378140</link>
<description><![CDATA[taffeys posted : <div class="bquote"><said>said by <a href="/profile/2003473" onClick="this.blur(); return popup(event,'/uidpop?ajh=1&uid=2003473');">ccsprague</a>:</said><p>Definitely an Arris issue.<br></p></div>Nope, it isn't Arris' fault that a Cox first-line rep didn't have a clue about modem firmware updates in general and how they get implemented. I chatted with an Arris rep this morning and he confirmed the new firmware but said Arris has no involvement in it's implementation by ISPs.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-Modem-Arris-S33-Issue-33378140</guid>
<pubDate>Mon, 11 Apr 2022 17:34:06 EDT</pubDate>
</item>
<item>
<title>Re: [Modem] Arris S33 Issue</title>
<link>http://www.dslreports.com/forum/Re-Modem-Arris-S33-Issue-33378077</link>
<description><![CDATA[ccsprague posted : Yep. Just got one of Netgear's CM1200s and I'm up and running with no issues now. Definitely an Arris issue.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-Modem-Arris-S33-Issue-33378077</guid>
<pubDate>Mon, 11 Apr 2022 16:23:54 EDT</pubDate>
</item>
<item>
<title>Re: [Modem] Arris S33 Issue</title>
<link>http://www.dslreports.com/forum/Re-Modem-Arris-S33-Issue-33377991</link>
<description><![CDATA[taffeys posted : Yup. Cox first said it was an Arris problem and contact them. I said it was Cox's responsibilty because they pushed the update to which Cox said it was Arris that actually updated the modem. When I asked how Arris got on the Cox network and to my modem she deflected to telling me I had to pay for Cox Advanced Support to "fix the problem". What idiots.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-Modem-Arris-S33-Issue-33377991</guid>
<pubDate>Mon, 11 Apr 2022 15:15:37 EDT</pubDate>
</item>
<item>
<title>Re: [Modem] Arris S33 Issue</title>
<link>http://www.dslreports.com/forum/Re-Modem-Arris-S33-Issue-33377980</link>
<description><![CDATA[ccsprague posted : Same issue here in Gainesville, FL! Arris is blaming Cox, Cox is blaming Arris.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-Modem-Arris-S33-Issue-33377980</guid>
<pubDate>Mon, 11 Apr 2022 15:01:22 EDT</pubDate>
</item>
<item>
<title>[Modem] Arris S33 Issue</title>
<link>http://www.dslreports.com/forum/Modem-Arris-S33-Issue-33377839</link>
<description><![CDATA[taffeys posted : I haven’t contacted Cox help in years but I did yesterday morning after I experienced repeated loss of connectivity. I looked at my router log and saw the S33 was in some sort of reboot loop. Tried to login to the S33 Web Manager but when I could access it it would report my logon username or password was incorrect. Tried a hardware reset but the modem wouldn’t respond. Finally, I just pulled the power and left it alone for 10 minutes. Upon powering it back up it rebooted a few times and then finally became stable. But I still could not login to see if I could determine what had happened. Contacted Cox online help and after a few back-and-forths a human script reader intervened. I said I suspected a new firmware was pushed to the modem by Cox, which was adamantly rejected by the rep. I was told no such update had occurred.  I was finally told I would have to pay for Cox Advanced Support which I said was ridiculous and exited the chat and went out for the rest of the day. Today I was able to confirm the firmware version is TB01.03.001.10_012022_212.S3, which appears to be new. How do I know? Because now the default password is the last 8 digits of the serial number and no longer “password”. Wish I had another option than Cox but I do not at this time. At least I no longer have Cox TV.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Modem-Arris-S33-Issue-33377839</guid>
<pubDate>Mon, 11 Apr 2022 12:32:59 EDT</pubDate>
</item>
</channel>
</rss>
