blackeneth
New Contributor III
Joined 5 years ago
User Profile
User Widgets
Contributions
Re: 2023 - Change Cable Modem IP Address
Three things to try: 1. Leave cable modem unplugged for 6.5 hours 2. Leave cable modem unplugged for 24.5 hours 3. Call customer service and ask them to "de-provision" your modem. Then have them "provision" your modem. Not sure how changing it enhances your security. Security will come from a good firewall. Then you can add a VPN to that.696Views0likes4CommentsRe: 2023 - Change Cable Modem IP Address
Three things to try: 1. Leave cable modem unplugged for 6.5 hours 2. Leave cable modem unplugged for 24.5 hours 3. Call customer service and ask them to "de-provision" your modem. Then have them "provision" your modem. Not sure how changing it enhances your security. Security will come from a good firewall. Then you can add a VPN to that. Ifind it annoying to have my external IP change -- it messes up some of the rules on my firewall.745Views0likes0CommentsRe: Cox refuses to provide service to my address. Cox is the only cable service provider in my rural area. Homes all around me have Cox service. My home was skipped by the cable company when they laid in the cable. NOW they demand that I pay thousands of doll
How many "thousands of dollars"? I would expect it to cost a $2000 - $3000. You could get your own quote to: 1) dig a 100 foot trench to a depth of 3 feet 2) lay in conduit (1.5" inch -- but check with Cox for their preferred size). 3) pull underground rated coaxial cable through the conduit (although check with Cox -- they may prefer to pull their own cable). If you can get the trench and conduit laid cheaper, I'm sure Cox will work with you to hook you up.77Views1like2CommentsRe: Recurring issue - Burnt Coax Cable
Reading the DSLReports thread referenced below, it appears to be the same problem -- an open neutral on your electrical service. Since your electrical service neutral is open, the coax is serving as the neutral return path and is carrying a lot of current. The only way coax gets that hot is if a lot of current is running through it -- which is not normal (under normal operation, the current is miniscule). This is a life safety issue and requires immediate attention. Call your power company immediately and report you have an open neutral, which is causing your cable coax line to carry current and catch fire. They should respond immediately. Do not touch it. You don't want to become part of the return path for your power service. Don't let a cable technician touch it -- same reason, it's an electrocution hazard. Let us know what happens.127Views1like5CommentsRe: Can't receive emails in my mac's outlook account
This post has my solution for windows:https://forums.cox.com/forum_home/internet_forum/f/internet-forum/24512/i-fixed-my-outlook-email-problem-after-cox-maintenance I don't have a mac, but you could google how to disable TLS 1.0 on the mac.1View1like0CommentsI fixed my Outlook email problem after Cox "maintenance"
Hi all, Like all (?) Outlook users, I lost the ability to receive mail a week ago (I could still send). I use Windows 10 Pro, version 1903 (OS build 18362.746). I am using Outlook Version 1911 (build 12228.20332). I fixed my connection issue by disabling the use of TLS 1.0 by Windows 10.I suspect the "maintenance" was to require TLS 1.2 connections. Our Outlook clients are trying to connect using TLS 1.0 and get rejected. Here's how I did it. The first step may not be required -- I think it was the second step that was definitive. NOTE: These directions are essentially the same as those here:https://windowsreport.com/how-to-disable-tls-1-0/ 1. Disable TLS 1.0 in Internet Settings Press Windows Key + S [This will bring up Search] Type "internet options" into search bar The Internet Properties window pops up Select the "Advanced" tab Scroll down to the bottom, the "Security" section. Uncheck "Use TLS 1.0" Note: I also unchecked TLS 1.1, and I checked Use TLS 1.3 (experimental). You may not need to do that. 2. Edit the Registry to Disable TLS 1.0 Press Windows Key + R [this brings up the "Run" window] type "regedit" in Run to run the registry editor Then, in the left-hand tree view, open up this key path: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols I couldn't see TLS 1.0 and Client subkeys went I arrived at the end of the above key path, so I had to create them. To create them: right-click on Protocols and select New > Key then enter "TLS 1.0" as the key title Next, right click on the TLS 1.0 key you just created, and select New > Key again. Enter "Client" as the title. Then, select the Client key, and in in the empty-space to the right of it, right-click and select New > DWORD (32-bit) Value Enter "Enabled" as the new DWORD's title The default value for this new Enabled DWORD is 0 (zero), which disables TLS 1.0. Finally, restart Windows (reboot). My Outlook IMAP Settings for Cox The above procedure should have restored your prior configuration to a working state. If it's not, here are is my working Outlook configuration. Recall that I am using Windows 10, with OutlookVersion 1911 (build 12228.20332) as part of Office 365. Note that I use IMAP and not POP. It Outlook, select the File menu In the Account Information screen, press the "Account Settings" button, then select "Server Settings" The IMAP Account Settings -- Incoming mail -- window appears: Now press the "Outgoing mail" link in this window. Now the IMAP settings for outgoing mail appears: Good Luck & Merry Christmas!