I have Xfinity internet, now at lowest speed for $29.99 per month for 1 year. I want to upgrade this to 60mbps for $39.99 per month. Is there anyway I can get 2 years term for this upgrade price? Who should I call and what is the telephone number? Thanks

I have seen many 'xfinitywifi' hotspots around that are open, which when you connect to are prompted to enter your Xfinity username/password. However, there is one near me currently that requires a password to connect to. Is there a way to receive that password? Or, is it maybe someone who named their AP 'xfinitywifi' to mess with people...

I heard to get the gigabit pro to install fiber pole thing in your home you need to be close to the tower how do you find how far are you from it as this not my address it from a restaurant there 3936 W 31st St, Chicago, IL 60623? What requirement do you need at your homes or any rules do I need to follow?

As mentioned in this recent DSLR news item https://www.dslreports.com/shownews/Comcast-Prepares-For-Mid2017-Wireless-Service-Launch-139048 , Comcast is planning a mid-year launch of their wireless service. Comcast announced today that they will be providing the details on this new service on Thursday: Comcast to Host Analyst Event to Discuss Launch of Mobile Initiative Comcast press release, Business Wire - April 3, 2017 http://www.businesswire.com/news/home/20170403005198/en/Comcast-Host-Analyst-Event-Discuss-Launch-Mobilequote:On Thursday, April 6, 2017, Comcast will host an analyst event to discuss the details of its previously announced mobile initiative, which utilizes an existing MVNO agreement. Senior members of the Comcast leadership team will participate in the event. ...There is also this FierceCable article today about it: Comcast sets Thursday meeting with investors to discuss wireless launch By Daniel Frankel, FierceCable - April 3, 2017 http://www.fiercecable.com/cable/comcast-sets-thursday-meeting-investors-to-discuss-wireless-launchquote:Some of the telecom industry’s most closely guarded secrets could finally be revealed Thursday, when Comcast hosts what it calls an “analyst event to discuss the details of its previously announced mobile initiative.” : Comcast confirmed plans to launch a wireless service combining the strengths of its vast Wi-Fi network and its MVNO deal with Verizon back in September. The launch has been slated for sometime later this year. : Last week, FierceWireless reported that Comcast is quietly partnering with Apple as it prepares to launch wireless service under the brand Xfinity Mobile: http://www.fiercewireless.com/wireless/comcast-quietly-taps-iphone-ahead-launch-xfinity-mobile The cable giant’s name has been added to behind-the-scenes - but publicly available - code that lists carrier bundles for the iPhone. The list of carrier bundles is used by iTunes and iPhones to determine whether the iPhone’s SIM is supported by a service provider with whom Apple has an agreement, then provisions the phone accordingly. The iPhone's latest list of carrier bundles includes "Verizon_Comcast_LTE_US," and mentions the service "Xfinity Mobile." A source pointed out the reference to FierceWireless, and a different source with knowledge of the matter confirmed that Comcast has indeed partnered with Apple ahead of the launch of Xfinity Mobile. EDIT: Also an article on Light Reading: http://www.lightreading.com/mobile/services-apps-mobile/new-comcast-wireless-details-drop-this-week-/d/d-id/731786 EDIT2: Karl has a news item up now about this https://www.dslreports.com/shownews/Comcast-to-Reveal-Details-on-Wireless-Service-on-Thursday-139284

I had a Technicolor 1 Gbit gateway installed about a month ago. About 2 weeks ago, the connectivity started acting weird. My connection would go up and down about every few minutes sometimes short, sometimes long. I had Comcast come out and replace the gateway. The tech measured the signal at the drop and found some errors on some frequencies. He escalated it to maintenance. They came back and said there was no problem and to replace the drop. The tech came back and replaced the drop and said the signal looked solid. I am still having the same issue. Anybody have something similar or resolved something similar?

Open my front door this afternoon and a service paper was placed in my door from Xfinity stating they are installing fiber in my neighborhood on 11/12. I live near the Mohgen casino.... All I have to say YAHOO I hope I can lower my bill from what the other cable company is charging me....

Hi all, I'm really bummed to be losing my CenturyLink symmetrical gigabit fiber service when I move towards the end of the year. I work at home and take advantage of all that upstream when I'm pushing around Docker images. I'd like to find the Comcast tier with the most upstream I can get for a reasonable amount. Is http://www.dslreports.com/faq/15643 still the most up-to-date listing of plan/tier upstreams? Thanks!

https://www.anandtech.com/show/13325/netgear-announces-nighthawk-rax80-rax120 Should make a nice pair for the new, I think MB or CM cablemodem, the one with the two 1GbE ports that can be bonded? Now Comcast Gig DOCSIS 3.1 customers can get their over-provisioning speeds now, thanks to bonding.

We've been trying to cut the bills lately and my mother is 62 (going to be 63 in February) and I'm wondering if Comcast offers a senior bundle (we live together). We switched the cell phones into my mother's name and found out that Verizon has a 55+ plan and we've decided that anything that has a senior discount mom wants to take advantage of. The cost of living in this part of the country is insane. As for Verizon I have my Galaxy S9+ and she has her iPhone 6.

Hey everyone, Anyone ever had this issue? When looking online at deals, xfinity’s website redirects us to the business.comcast website and states our records shows your address is a business address ... If not click on residential link. Well after clicking on the link it goes back to xfinity, prompts to for an address and the cycle starts over again.. Anyone know how to remove my address from the business side of Comcast? We do have residential internet which is why it’s odd this is happening.

I recently moved down and for simplicity opted for the Xfinity modem/router in 1 device. In the past I was in NYC and they only ever gave the modem so I do have my own older Asus rtn66 I could reuse. Anyways after about 5 days or so our devices on wifi randomly drop. Saying ssid isnt there, and then it pops back up. Sometimes nothing loads saying no connection, and I have to disconnect and reconnect. And now the other day using the reddit app on my phone pics wouldnt load. I turn off wifi and go to cellular and everything loaded up quick. I dont think cellular should ever beat home wifi. So I have blast, I believe 150mpbs because I also had tv bundled in which seems to make the higher speed options just disappear. What modem do you guys suggest I get? I game a lot and recall something, puma, that was an issue with latency. And on that note any suggestions on a router? Ive typically bought $50-80 so not sure I need more power. I tend not to trust wifi much as being in NYC apartment buildings there would be 40+ ssids to contend with so I ended up putting cheapo wireless N's in each room and hardwired where I could. Now I'd like to maybe get something with more kick. At some point play around with pi-hole or some such.

At seemingly random intervals computer screens go black momentarily while audio stays on. It happens on my Chromebook, ThinkPad T480, Asus HB1M-Plus as well as our Samsung 55" smart TV. I think it only happens during YouTube videos, regular broadcast cable shows and Netflix streaming. Operating system are Chrome, Windows 10 Pro and Windows 10 Home. The Xfinity router is a "Dual-Band WiFi 802.11ac XB3" The PCs are cabled to the modem, the Chrome book and Samsung TV are connected by Wifi. I would say it has been happening for the past year but the blackouts seem more frequent now. The blackouts may last for 1 or 2 seconds. I am not positive but I think it happens individually, and not all screens at once. Is anyone familiar with this phenomenon? Cause? Is it Comcast" modem (my best guess) or the Comcast/Xfinity network? If not, any ideas how to test or or eliminate causes?

Comcast has now opened its Wi-Fi hotspots in Northern California’s Yuba and Butte counties to help residents and emergency personnel during the wildfires there: https://california.comcast.com/2018/11/08/comcast-opens-wifi-hotspots-in-northern-californias-yuba-and-butte-counties-to-aid-residents-and-emergency-personnel-during-the-camp-fire/ Also: Frequently Asked Questions for Fire-Impacted Customers https://california.comcast.com/2018/11/09/frequently-asked-questions-for-fire-impacted-customers/

Got a length of what I hope is the right cable, to go from pedestal to house. The old RG6 is 30 years old, and needs to go. I got this cable https://www.ebay.com/itm/RG6-DIRECT-BURIAL-UNDERGROUND-COAXIAL-CABLE-WEATHER-SEAL-TRISHIELD-BLACK-ORANGE/152908118475?ssPageName=STRK%3AMEBIDX%3AIT&var=452668468444&_trksid=p2057872.m2749.l2649 And hope it was Commscope, but it's Amphenol BBS TFC-T10 China ShieldX No other info on the cable itself, so does anyone know if it's tri shield, and proper for going through conduit, for my application? Thanks!

Yesterday and today, for two different chat sessions about starting a new service for GF, I requested a copy of the chat be emailed by pushing the provided button and filling in an email address. Neither session copy was received at that address, nor in the spam folder. Not good. :(

Are the channel frequencies that are used by the cable modem used for the TV set top boxes also, or is the TV side a completely different configuration or method used to choose the frequencies?

I have been checking my modem logs and noticed T3 timeouts almost constantly. This is a new modem, Arris SB6183. I never noticed this on my old SB 6121. The weird thing, at least to me, is that I don't seem to have any noticeable problems. From what I have read, This seems to sometimes be corrected by having a new line run. I will post the log if anyone wants to weigh in. I did a chat with comcast/xfinity and that was pretty much a waste of time. Should I be concerned or just let it go since I don't seem to have any other issues, at least none I am aware of. Event Log The table below contains the log of events that the SB6183 has detected. This log can be important to the service provider to help diagnose and correct problems, if any should occur. Time Priority Description Sat Nov 03 11:26:30 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=f8:a0:97:b7:b5:ad;CMTS-MAC=00:01:5c:69:3e:5e;CM-QOS=1.1;CM-VER=3.0; Sat Nov 03 11:23:03 2018 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 3;CM-MAC=f8:a0:97:b7:b5:ad;CMTS-MAC=00:01:5c:69:3e:5e;CM-QOS=1.1;CM-VER=3.0; Sat Nov 03 11:23:03 2018 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=f8:a0:97:b7:b5:ad;CMTS-MAC=00:01:5c:69:3e:5e;CM-QOS=1.1;CM-VER=3.0; Sat Nov 03 11:23:03 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=f8:a0:97:b7:b5:ad;CMTS-MAC=00:01:5c:69:3e:5e;CM-QOS=1.1;CM-VER=3.0; Sat Nov 03 11:22:54 2018 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 2;CM-MAC=f8:a0:97:b7:b5:ad;CMTS-MAC=00:01:5c:69:3e:5e;CM-QOS=1.1;CM-VER=3.0; Sat Nov 03 11:22:54 2018 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=f8:a0:97:b7:b5:ad;CMTS-MAC=00:01:5c:69:3e:5e;CM-QOS=1.1;CM-VER=3.0; Sat Nov 03 11:22:54 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=f8:a0:97:b7:b5:ad;CMTS-MAC=00:01:5c:69:3e:5e;CM-QOS=1.1;CM-VER=3.0; Sat Nov 03 11:22:43 2018 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 1;CM-MAC=f8:a0:97:b7:b5:ad;CMTS-MAC=00:01:5c:69:3e:5e;CM-QOS=1.1;CM-VER=3.0; Sat Nov 03 11:22:43 2018 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=f8:a0:97:b7:b5:ad;CMTS-MAC=00:01:5c:69:3e:5e;CM-QOS=1.1;CM-VER=3.0; Sat Nov 03 11:22:43 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=f8:a0:97:b7:b5:ad;CMTS-MAC=00:01:5c:69:3e:5e;CM-QOS=1.1;CM-VER=3.0; Sat Nov 03 11:15:50 2018 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 3;CM-MAC=f8:a0:97:b7:b5:ad;CMTS-MAC=00:01:5c:69:3e:5e;CM-QOS=1.1;CM-VER=3.0; Sat Nov 03 11:15:50 2018 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=f8:a0:97:b7:b5:ad;CMTS-MAC=00:01:5c:69:3e:5e;CM-QOS=1.1;CM-VER=3.0; Sat Nov 03 11:15:50 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=f8:a0:97:b7:b5:ad;CMTS-MAC=00:01:5c:69:3e:5e;CM-QOS=1.1;CM-VER=3.0; Sat Nov 03 11:15:41 2018 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 2;CM-MAC=f8:a0:97:b7:b5:ad;CMTS-MAC=00:01:5c:69:3e:5e;CM-QOS=1.1;CM-VER=3.0; Sat Nov 03 11:15:41 2018 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=f8:a0:97:b7:b5:ad;CMTS-MAC=00:01:5c:69:3e:5e;CM-QOS=1.1;CM-VER=3.0; Sat Nov 03 11:15:41 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=f8:a0:97:b7:b5:ad;CMTS-MAC=00:01:5c:69:3e:5e;CM-QOS=1.1;CM-VER=3.0; Sat Nov 03 11:15:31 2018 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 1;CM-MAC=f8:a0:97:b7:b5:ad;CMTS-MAC=00:01:5c:69:3e:5e;CM-QOS=1.1;CM-VER=3.0; Sat Nov 03 11:15:31 2018 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=f8:a0:97:b7:b5:ad;CMTS-MAC=00:01:5c:69:3e:5e;CM-QOS=1.1;CM-VER=3.0; Sat Nov 03 11:15:31 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=f8:a0:97:b7:b5:ad;CMTS-MAC=00:01:5c:69:3e:5e;CM-QOS=1.1;CM-VER=3.0; Sat Nov 03 11:08:38 2018 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 3;CM-MAC=f8:a0:97:b7:b5:ad;CMTS-MAC=00:01:5c:69:3e:5e;CM-QOS=1.1;CM-VER=3.0; Sat Nov 03 11:08:38 2018 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=f8:a0:97:b7:b5:ad;CMTS-MAC=00:01:5c:69:3e:5e;CM-QOS=1.1;CM-VER=3.0; Sat Nov 03 11:08:38 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=f8:a0:97:b7:b5:ad;CMTS-MAC=00:01:5c:69:3e:5e;CM-QOS=1.1;CM-VER=3.0; Sat Nov 03 11:08:29 2018 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 2;CM-MAC=f8:a0:97:b7:b5:ad;CMTS-MAC=00:01:5c:69:3e:5e;CM-QOS=1.1;CM-VER=3.0; Sat Nov 03 11:08:29 2018 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=f8:a0:97:b7:b5:ad;CMTS-MAC=00:01:5c:69:3e:5e;CM-QOS=1.1;CM-VER=3.0; Sat Nov 03 11:08:29 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=f8:a0:97:b7:b5:ad;CMTS-MAC=00:01:5c:69:3e:5e;CM-QOS=1.1;CM-VER=3.0; Sat Nov 03 11:08:19 2018 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 1;CM-MAC=f8:a0:97:b7:b5:ad;CMTS-MAC=00:01:5c:69:3e:5e;CM-QOS=1.1;CM-VER=3.0; Sat Nov 03 11:08:19 2018 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=f8:a0:97:b7:b5:ad;CMTS-MAC=00:01:5c:69:3e:5e;CM-QOS=1.1;CM-VER=3.0; Sat Nov 03 11:08:19 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=f8:a0:97:b7:b5:ad;CMTS-MAC=00:01:5c:69:3e:5e;CM-QOS=1.1;CM-VER=3.0; Sat Nov 03 11:01:26 2018 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 3;CM-MAC=f8:a0:97:b7:b5:ad;CMTS-MAC=00:01:5c:69:3e:5e;CM-QOS=1.1;CM-VER=3.0; Sat Nov 03 11:01:26 2018 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=f8:a0:97:b7:b5:ad;CMTS-MAC=00:01:5c:69:3e:5e;CM-QOS=1.1;CM-VER=3.0; Sat Nov 03 11:01:26 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=f8:a0:97:b7:b5:ad;CMTS-MAC=00:01:5c:69:3e:5e;CM-QOS=1.1;CM-VER=3.0; Sat Nov 03 11:01:17 2018 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 2;CM-MAC=f8:a0:97:b7:b5:ad;CMTS-MAC=00:01:5c:69:3e:5e;CM-QOS=1.1;CM-VER=3.0; Sat Nov 03 11:01:17 2018 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=f8:a0:97:b7:b5:ad;CMTS-MAC=00:01:5c:69:3e:5e;CM-QOS=1.1;CM-VER=3.0; Sat Nov 03 11:01:17 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=f8:a0:97:b7:b5:ad;CMTS-MAC=00:01:5c:69:3e:5e;CM-QOS=1.1;CM-VER=3.0; Sat Nov 03 11:01:06 2018 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 1;CM-MAC=f8:a0:97:b7:b5:ad;CMTS-MAC=00:01:5c:69:3e:5e;CM-QOS=1.1;CM-VER=3.0; Sat Nov 03 11:01:06 2018 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=f8:a0:97:b7:b5:ad;CMTS-MAC=00:01:5c:69:3e:5e;CM-QOS=1.1;CM-VER=3.0; Sat Nov 03 11:01:06 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=f8:a0:97:b7:b5:ad;CMTS-MAC=00:01:5c:69:3e:5e;CM-QOS=1.1;CM-VER=3.0; Sat Nov 03 10:54:13 2018 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 3;CM-MAC=f8:a0:97:b7:b5:ad;CMTS-MAC=00:01:5c:69:3e:5e;CM-QOS=1.1;CM-VER=3.0; Sat Nov 03 10:54:13 2018 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=f8:a0:97:b7:b5:ad;CMTS-MAC=00:01:5c:69:3e:5e;CM-QOS=1.1;CM-VER=3.0; Sat Nov 03 10:54:13 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=f8:a0:97:b7:b5:ad;CMTS-MAC=00:01:5c:69:3e:5e;CM-QOS=1.1;CM-VER=3.0; Sat Nov 03 10:54:04 2018 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 2;CM-MAC=f8:a0:97:b7:b5:ad;CMTS-MAC=00:01:5c:69:3e:5e;CM-QOS=1.1;CM-VER=3.0; Sat Nov 03 10:54:04 2018 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=f8:a0:97:b7:b5:ad;CMTS-MAC=00:01:5c:69:3e:5e;CM-QOS=1.1;CM-VER=3.0; Sat Nov 03 10:54:04 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=f8:a0:97:b7:b5:ad;CMTS-MAC=00:01:5c:69:3e:5e;CM-QOS=1.1;CM-VER=3.0; Sat Nov 03 10:53:54 2018 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 1;CM-MAC=f8:a0:97:b7:b5:ad;CMTS-MAC=00:01:5c:69:3e:5e;CM-QOS=1.1;CM-VER=3.0; Sat Nov 03 10:53:54 2018 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=f8:a0:97:b7:b5:ad;CMTS-MAC=00:01:5c:69:3e:5e;CM-QOS=1.1;CM-VER=3.0; Sat Nov 03 10:53:54 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=f8:a0:97:b7:b5:ad;CMTS-MAC=00:01:5c:69:3e:5e;CM-QOS=1.1;CM-VER=3.0; Sat Nov 03 10:47:01 2018 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 3;CM-MAC=f8:a0:97:b7:b5:ad;CMTS-MAC=00:01:5c:69:3e:5e;CM-QOS=1.1;CM-VER=3.0; Sat Nov 03 10:47:01 2018 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=f8:a0:97:b7:b5:ad;CMTS-MAC=00:01:5c:69:3e:5e;CM-QOS=1.1;CM-VER=3.0; Sat Nov 03 10:47:01 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=f8:a0:97:b7:b5:ad;CMTS-MAC=00:01:5c:69:3e:5e;CM-QOS=1.1;CM-VER=3.0; Sat Nov 03 10:46:52 2018 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 2;CM-MAC=f8:a0:97:b7:b5:ad;CMTS-MAC=00:01:5c:69:3e:5e;CM-QOS=1.1;CM-VER=3.0; Sat Nov 03 10:46:52 2018 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=f8:a0:97:b7:b5:ad;CMTS-MAC=00:01:5c:69:3e:5e;CM-QOS=1.1;CM-VER=3.0; Sat Nov 03 10:46:52 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=f8:a0:97:b7:b5:ad;CMTS-MAC=00:01:5c:69:3e:5e;CM-QOS=1.1;CM-VER=3.0; Sat Nov 03 10:46:42 2018 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 1;CM-MAC=f8:a0:97:b7:b5:ad;CMTS-MAC=00:01:5c:69:3e:5e;CM-QOS=1.1;CM-VER=3.0; Sat Nov 03 10:46:42 2018 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=f8:a0:97:b7:b5:ad;CMTS-MAC=00:01:5c:69:3e:5e;CM-QOS=1.1;CM-VER=3.0; Sat Nov 03 10:46:42 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=f8:a0:97:b7:b5:ad;CMTS-MAC=00:01:5c:69:3e:5e;CM-QOS=1.1;CM-VER=3.0; Sat Nov 03 10:39:48 2018 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 3;CM-MAC=f8:a0:97:b7:b5:ad;CMTS-MAC=00:01:5c:69:3e:5e;CM-QOS=1.1;CM-VER=3.0; Sat Nov 03 10:39:48 2018 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=f8:a0:97:b7:b5:ad;CMTS-MAC=00:01:5c:69:3e:5e;CM-QOS=1.1;CM-VER=3.0; Sat Nov 03 10:39:48 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=f8:a0:97:b7:b5:ad;CMTS-MAC=00:01:5c:69:3e:5e;CM-QOS=1.1;CM-VER=3.0; Sat Nov 03 10:39:39 2018 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 2;CM-MAC=f8:a0:97:b7:b5:ad;CMTS-MAC=00:01:5c:69:3e:5e;CM-QOS=1.1;CM-VER=3.0; Sat Nov 03 10:39:39 2018 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=f8:a0:97:b7:b5:ad;CMTS-MAC=00:01:5c:69:3e:5e;CM-QOS=1.1;CM-VER=3.0; Sat Nov 03 10:39:39 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=f8:a0:97:b7:b5:ad;CMTS-MAC=00:01:5c:69:3e:5e;CM-QOS=1.1;CM-VER=3.0; Sat Nov 03 10:39:29 2018 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 1;CM-MAC=f8:a0:97:b7:b5:ad;CMTS-MAC=00:01:5c:69:3e:5e;CM-QOS=1.1;CM-VER=3.0; Sat Nov 03 10:39:29 2018 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=f8:a0:97:b7:b5:ad;CMTS-MAC=00:01:5c:69:3e:5e;CM-QOS=1.1;CM-VER=3.0; Sat Nov 03 10:39:29 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=f8:a0:97:b7:b5:ad;CMTS-MAC=00:01:5c:69:3e:5e;CM-QOS=1.1;CM-VER=3.0; Sat Nov 03 10:32:35 2018 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 3;CM-MAC=f8:a0:97:b7:b5:ad;CMTS-MAC=00:01:5c:69:3e:5e;CM-QOS=1.1;CM-VER=3.0; Sat Nov 03 10:32:35 2018 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=f8:a0:97:b7:b5:ad;CMTS-MAC=00:01:5c:69:3e:5e;CM-QOS=1.1;CM-VER=3.0; Sat Nov 03 10:32:35 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=f8:a0:97:b7:b5:ad;CMTS-MAC=00:01:5c:69:3e:5e;CM-QOS=1.1;CM-VER=3.0; Sat Nov 03 10:32:27 2018 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 2;CM-MAC=f8:a0:97:b7:b5:ad;CMTS-MAC=00:01:5c:69:3e:5e;CM-QOS=1.1;CM-VER=3.0; Sat Nov 03 10:32:27 2018 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=f8:a0:97:b7:b5:ad;CMTS-MAC=00:01:5c:69:3e:5e;CM-QOS=1.1;CM-VER=3.0; Sat Nov 03 10:32:27 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=f8:a0:97:b7:b5:ad;CMTS-MAC=00:01:5c:69:3e:5e;CM-QOS=1.1;CM-VER=3.0; Sat Nov 03 10:32:17 2018 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 1;CM-MAC=f8:a0:97:b7:b5:ad;CMTS-MAC=00:01:5c:69:3e:5e;CM-QOS=1.1;CM-VER=3.0; Sat Nov 03 10:32:17 2018 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=f8:a0:97:b7:b5:ad;CMTS-MAC=00:01:5c:69:3e:5e;CM-QOS=1.1;CM-VER=3.0; Sat Nov 03 10:32:17 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=f8:a0:97:b7:b5:ad;CMTS-MAC=00:01:5c:69:3e:5e;CM-QOS=1.1;CM-VER=3.0; Sat Nov 03 10:25:23 2018 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 3;CM-MAC=f8:a0:97:b7:b5:ad;CMTS-MAC=00:01:5c:69:3e:5e;CM-QOS=1.1;CM-VER=3.0; Sat Nov 03 10:25:23 2018 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=f8:a0:97:b7:b5:ad;CMTS-MAC=00:01:5c:69:3e:5e;CM-QOS=1.1;CM-VER=3.0; Sat Nov 03 10:25:23 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=f8:a0:97:b7:b5:ad;CMTS-MAC=00:01:5c:69:3e:5e;CM-QOS=1.1;CM-VER=3.0; Sat Nov 03 10:25:15 2018 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 2;CM-MAC=f8:a0:97:b7:b5:ad;CMTS-MAC=00:01:5c:69:3e:5e;CM-QOS=1.1;CM-VER=3.0; Sat Nov 03 10:25:15 2018 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=f8:a0:97:b7:b5:ad;CMTS-MAC=00:01:5c:69:3e:5e;CM-QOS=1.1;CM-VER=3.0; Sat Nov 03 10:25:15 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=f8:a0:97:b7:b5:ad;CMTS-MAC=00:01:5c:69:3e:5e;CM-QOS=1.1;CM-VER=3.0; Sat Nov 03 10:25:04 2018 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 1;CM-MAC=f8:a0:97:b7:b5:ad;CMTS-MAC=00:01:5c:69:3e:5e;CM-QOS=1.1;CM-VER=3.0; Sat Nov 03 10:25:04 2018 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=f8:a0:97:b7:b5:ad;CMTS-MAC=00:01:5c:69:3e:5e;CM-QOS=1.1;CM-VER=3.0; Sat Nov 03 10:25:04 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=f8:a0:97:b7:b5:ad;CMTS-MAC=00:01:5c:69:3e:5e;CM-QOS=1.1;CM-VER=3.0; Sat Nov 03 10:18:11 2018 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 3;CM-MAC=f8:a0:97:b7:b5:ad;CMTS-MAC=00:01:5c:69:3e:5e;CM-QOS=1.1;CM-VER=3.0; Sat Nov 03 10:18:11 2018 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=f8:a0:97:b7:b5:ad;CMTS-MAC=00:01:5c:69:3e:5e;CM-QOS=1.1;CM-VER=3.0; Sat Nov 03 10:18:11 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=f8:a0:97:b7:b5:ad;CMTS-MAC=00:01:5c:69:3e:5e;CM-QOS=1.1;CM-VER=3.0; Sat Nov 03 10:18:02 2018 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 2;CM-MAC=f8:a0:97:b7:b5:ad;CMTS-MAC=00:01:5c:69:3e:5e;CM-QOS=1.1;CM-VER=3.0; Sat Nov 03 10:18:02 2018 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=f8:a0:97:b7:b5:ad;CMTS-MAC=00:01:5c:69:3e:5e;CM-QOS=1.1;CM-VER=3.0; Sat Nov 03 10:18:02 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=f8:a0:97:b7:b5:ad;CMTS-MAC=00:01:5c:69:3e:5e;CM-QOS=1.1;CM-VER=3.0; Sat Nov 03 10:17:52 2018 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 1;CM-MAC=f8:a0:97:b7:b5:ad;CMTS-MAC=00:01:5c:69:3e:5e;CM-QOS=1.1;CM-VER=3.0; Sat Nov 03 10:17:52 2018 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=f8:a0:97:b7:b5:ad;CMTS-MAC=00:01:5c:69:3e:5e;CM-QOS=1.1;CM-VER=3.0; Sat Nov 03 10:17:52 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=f8:a0:97:b7:b5:ad;CMTS-MAC=00:01:5c:69:3e:5e;CM-QOS=1.1;CM-VER=3.0; Sat Nov 03 10:10:58 2018 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 3;CM-MAC=f8:a0:97:b7:b5:ad;CMTS-MAC=00:01:5c:69:3e:5e;CM-QOS=1.1;CM-VER=3.0; Sat Nov 03 10:10:58 2018 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=f8:a0:97:b7:b5:ad;CMTS-MAC=00:01:5c:69:3e:5e;CM-QOS=1.1;CM-VER=3.0; Sat Nov 03 10:10:58 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=f8:a0:97:b7:b5:ad;CMTS-MAC=00:01:5c:69:3e:5e;CM-QOS=1.1;CM-VER=3.0; Sat Nov 03 10:10:49 2018 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 2;CM-MAC=f8:a0:97:b7:b5:ad;CMTS-MAC=00:01:5c:69:3e:5e;CM-QOS=1.1;CM-VER=3.0; Sat Nov 03 10:10:49 2018 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=f8:a0:97:b7:b5:ad;CMTS-MAC=00:01:5c:69:3e:5e;CM-QOS=1.1;CM-VER=3.0; Sat Nov 03 10:10:49 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=f8:a0:97:b7:b5:ad;CMTS-MAC=00:01:5c:69:3e:5e;CM-QOS=1.1;CM-VER=3.0; Sat Nov 03 10:10:39 2018 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 1;CM-MAC=f8:a0:97:b7:b5:ad;CMTS-MAC=00:01:5c:69:3e:5e;CM-QOS=1.1;CM-VER=3.0; Sat Nov 03 10:10:39 2018 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=f8:a0:97:b7:b5:ad;CMTS-MAC=00:01:5c:69:3e:5e;CM-QOS=1.1;CM-VER=3.0; Sat Nov 03 10:10:39 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=f8:a0:97:b7:b5:ad;CMTS-MAC=00:01:5c:69:3e:5e;CM-QOS=1.1;CM-VER=3.0;

I have a coax line coming up into my room then connected to a 2way splitter one line goes to the cable box the other goes to the cable modem.i want to put a 3db attenuator on the modem line.so could I just connect one end of the attenuator to the modem and then connect the coax to the other end of the attenuator?is this ok?

Hello All, I am looking to move out to the Sultan, WA area and need to run cable to my prospective new home. We need roughly 1400ft of aerial cable run down the street. I have been in communication with Comcast in regards to this and have gotten an estimate of around $27,000 to run the cable. While we are willing to pay that price, regardless of how absurdly expensive that is, we would of course love to not have to pay that much if at all possible. I was told by a relative that it might be possible (also faster and cheaper) to hire an independent contractor to run the cable instead of getting Comcast to do it. Comcast, not to my surprise, is dragging their feet on this time sensitive project even though we are willing to pay them for this. My question: Is it legal to hire an independent contractor to run the aerial cable? If so, would it require Comcast to finish the job at the house after the cable is run or can I simply buy\lease a modem and get an IP assigned to it to setup service? Thank you for your help in advance.

My modem has been up and running for a few weeks and I noticed a lot of uncorrectable errors. Is this normal? Here’s my stats. I also checked the event log and see errors. Is this normal or should I put a call into tech support? Only issue I notice notice is connection issues with FaceTime (poor connection at times).