ESPN app gives error "this channel is not part of your TV package"
I am signed into the ESPN app on my firestick using my COX credentials yet when I try to view a program on ESPN or ESPN2 using the app it tells me that this is "this channel is not part of your subscription". Ive tried uninstalling and reinstalling the app along with trying the app on my phone but continue to get the same error. Note - Same as earlier persons topic but the solution is not in the reply thread. Note 2 - I’ve also tried logging into espn with my espn account which works fine on my phone and I’m able to watch directly on my phone... This has been an issue for 2 months now and I’m tired of driving to a local bar just to watch a football game please help.11KViews0likes2CommentsInteresting issue with my Netflix streaming.....
I started having trouble with my Netflix streaming to my smart tv tonight so I began investigating and found something very interesting... Initially I tried a ping to netflix.com and every request timed out. I figured maybe their servers don't accept incoming pings so I tried a tracert next and this is what came back..... Tracing route to netflix.com [107.20.154.246] over a maximum of 30 hops: 1 7 ms 7 ms 7 ms 10.51.0.1 - My modem 2 7 ms 7 ms 7 ms 172.21.0.180 - Cox 3 42 ms 29 ms 29 ms 70.169.77.248 - Cox 4 44 ms 59 ms 45 ms dalsbprj01-ae1.0.rd.dl.cox.net [68.1.2.109] - Cox 5 31 ms 31 ms 32 ms 68.105.30.10 - Cox 6 72 ms 66 ms 65 ms 54.240.229.102 - AMAZON?? 7 66 ms 67 ms 67 ms 54.240.229.12 - AMAZON?? 8 79 ms 79 ms 79 ms 54.240.229.164 - AMAZON?? 9 66 ms 67 ms 65 ms 54.240.229.125 - AMAZON?? 10 73 ms 73 ms 73 ms 205.251.244.22 - AMAZON?? 11 66 ms 67 ms 68 ms 205.251.245.11 - AMAZON?? 12 65 ms 67 ms 67 ms 205.251.245.123 - AMAZON?? 13 * * * Request timed out. 14 * * * Request timed out. 15 * * * Request timed out. 16 69 ms 69 ms 74 ms 216.182.224.197 - AMAZON?? 17 * * * Request timed out. 18 * * * Request timed out. 19 * * * Request timed out. 20 * * * Request timed out. 21 * * * Request timed out. 22 * * * Request timed out. 23 * * * Request timed out. 24 * * * Request timed out. 25 * * * Request timed out. 26 * * * Request timed out. 27 * * * Request timed out. 28 * * * Request timed out. 29 * * * Request timed out. 30 * * * Request timed out. Trace complete. So what I am wondering is why my internet connection is being routed through AMAZON connections to get to Netflix. The last time I checked, Amazon didn't own Netflix, nor are they an ISP and they certainly don't own Cox. As soon as my connection moves from the Cox network over to Amazon you can see that all of the connection times go up, or even time out. Here's a tracert to Yahoo..... Tracing route to yahoo.com [98.138.253.109] over a maximum of 30 hops: 1 8 ms 7 ms 7 ms 10.51.0.1 - my modem 2 7 ms 7 ms 7 ms 172.21.2.180 - Cox 3 36 ms 19 ms 19 ms 70.169.77.248 - Cox 4 41 ms 42 ms 44 ms sanjbprj01-ae0.0.rd.sj.cox.net [68.1.5.184] - Cox 5 160 ms 43 ms 43 ms 68.105.31.47 - Cox 6 95 ms 109 ms 99 ms ae-9.pat2.dnx.yahoo.com [216.115.96.113] - Yahoo 7 80 ms 79 ms 79 ms ae-6.pat1.nez.yahoo.com [216.115.104.118] - Yahoo 8 80 ms 79 ms 79 ms ae-0.msr1.ne1.yahoo.com [216.115.100.1] - Yahoo 9 79 ms 79 ms 79 ms UNKNOWN-98-138-97-X.yahoo.com [98.138.97.3] - Yahoo 10 81 ms 79 ms 79 ms UNKNOWN-98-138-97-X.yahoo.com [98.138.97.47] - Yahoo 11 81 ms 79 ms 79 ms po-17.bas1-7-prd.ne1.yahoo.com [98.138.240.20] - Yahoo 12 80 ms 81 ms 80 ms ir1.fp.vip.ne1.yahoo.com [98.138.253.109] - Yahoo Trace complete. So in this we can see that my traffic takes a different route and jumps directly from the Cox network on to the Yahoo network and then connects. I ran a tracert to a website that I run next.... Tracing route to azcheermixes.com [192.0.78.24] over a maximum of 30 hops: 1 6 ms 7 ms 7 ms 10.51.0.1 - my modem 2 7 ms 7 ms 7 ms 172.21.0.180 - Cox 3 28 ms 22 ms 39 ms 70.169.77.248 - Cox 4 20 ms 21 ms 19 ms langbprj02-ae2.rd.la.cox.net [68.1.1.19] - Cox 5 20 ms 22 ms 21 ms ae-7.r00.lsanca19.us.bb.gin.ntt.net [129.250.194.165] - NTT America 6 34 ms 34 ms 34 ms ae-17.r04.lsanca03.us.bb.gin.ntt.net [129.250.6.202] - NTT America 7 21 ms 21 ms 25 ms ae-6.r21.lsanca03.us.bb.gin.ntt.net [129.250.5.69] - NTT America 8 30 ms 29 ms 31 ms ae-12.r22.snjsca04.us.bb.gin.ntt.net [129.250.4.150] - NTT America 9 32 ms 31 ms 31 ms ae-36.r02.snjsca04.us.bb.gin.ntt.net [129.250.5.242] - NTT America 10 29 ms 29 ms 29 ms xe-0-6-0-8.r02.snjsca04.us.ce.gin.ntt.net [128.241.1.150] - NTT America 11 30 ms 30 ms 29 ms 192.0.78.24 - Wordpress (my site host) Trace complete. Low connection times, no timeouts and NO AMAZON. Does anyone know why Cox traffic to Netflix is being routed through Amazon??6.1KViews0likes1Commentcox homelife - enhancement request for google home and amazon alexa
It would be nice to unlock or lock my cox homelife system with my google home system. I think people would enjoy using this with their system as well. You guys should add integration to google home and amazon alexa.5.2KViews2likes1CommentData Use
Not so much a question but more of a discovery of sorts. When I connected the Amazon Fire TV box, which is great, I found that after turning off the receiver and tv more often than not the Amazon Fire device stays on. Since I use a series of photos for screen savers, these continue to download which ramps up the data use quite a bit. I have the latest firmware in the Amazon device, but my low tech solution is to unplug it when I'm not using it, which makes sense anyway. Found this out after several days of 40 gigabyte use.2KViews0likes1CommentContour 2 Amazon Prime Video Problem
We have been a Cox customer for over 25 years. We have had Contour for a long time. We have watched video content on Prime Video for years. About 6 months ago, we started encountering a problem where the video freezes up, and then either one of two things happens: 1) it freezes for about 3 minutes and then kicks back out to cable tv or.... the most common occurrence is 2) it freezes for about 3 minutes, we get an error message" Sorry there seems to be some trouble. Please tighten your cable connections, and then restart your TV box. This can often fix common issues. RDK-03033". Then the cable box/DVR automatically reboots itself after several more minutes. We try to watch a video again, and it happens again. Every. Single. Night. Every. Single. Night. Over. And. Over. Again. Every. Single. Night. We have a second problem when watching regular cable tv. It gets stuck, and will not accept any input. Then the cable box/DVR reboots. We have replaced the DVR 3 times. We have called technical support sooooooooooo many times over the last 6 months at 877-269-2778 and talked to many different customer service reps who give us many different reasons why this could be happening, but all reasons are NOT Cox's issue. It's the surge protector. It's a lack of a surge protector. it's the wrong surge protector. It's Amazon. It's an outage happening that is not even affecting me. We ask for what error code 03033 means, and no rep can tell us what that means. Then amazingly, the customer service rep disconnects. Every. Single. Time. When we replaced the cable box/DVR the third time, the Cox Solutions Store rep told us that if we continue to have problems, to call 877-269-2778. There is no one who can help us. We have wasted countless hours on the phone and in store for the last 6 months. We have no resolution. We have no where to go. There is something wrong with Cox' Contour service. We pay hundreds of dollars for cable, tv and phone. And the cable is not reliable. I am hoping that the forum experts have a quality response to FIX THIS. Please help.1.3KViews0likes2Comments