ContributionsMost RecentMost LikesSolutionsRe: Cannot send email via Outlook - Constantly asks for password to send Unfortunately, none of the Cox communications (email or the link you provided) mentions changing the account's password after the server port changes. One of my family members has been having issues with Windows XP and Outlook 2003 where her email SEND or RECEIVE keeps asking for her password. Then, after the Security Settings effective 1/25/18, she kept getting this prompt and an Internet Security yes/no prompt for the server that was being used (smtp.cox.net). Sometimes her email would send and receive and sometimes they didn't. I changed her password on her account (used the same password) and will see if this fixes her password prompt, Internet Security prompt and issues with Send/Receive. Her email server settings are: pop.cox.net - port 995 SSL enabled smtp.cox.net - port 587 SSL enabled (tried 465 with SSL but kept getting errors) Re: Delivery Failure code 535 - authentication reject using gmail to import from cox UPDATE: Changed the smtp.cox.net port to 587 SSL enabled on both family member's email clients. Will try out and see what happens. Tests for outgoing/incoming from non-Cox email addresses were successful, but I'm not convinced this is a permanent fix. Re: Delivery Failure code 535 - authentication reject using gmail to import from cox Similar issues for family members using Windows 10 and XP. One person using XP and Outlook 2003 keeps getting prompted to enter their Cox mail password to receive/send or they get an Internet Security windows about Cox trusted servers. Clicking YES removes this until the next time which is intermittent. Another person using Windows 10 and its Mail client has issues sending email. Sometimes it works - sometimes the mail sits in the Outgoing box. Cox points the finger at Microsoft and I'm sure Microsoft will point the finger at Cox. Server settings for the XP person are: pop.cox.net - port 995, smtp.cox.net - port 465 (with SSL set on for both) Server settings for the Windows 10 person are: imap.cox.net:993:1 (port and SSL on), smtp.cox.net:465:1 (port and SSL on) Re: Apple Airport Extreme Base Station and Time Capsule Firmware Updates Trying again. As of yesterday (5/27), my connection has been stable for 24 hours with IPv6 enabled. Here's a link from a post in the DSLR Forum that discusses the fixes in the firmware releases. Re: Router losing connection to Cable Modem @Tecknowhelp Thanks for the link. If there were truly fixes for IPv6 and DNS in the firmware releases, they might be working for me (Chandler, AZ). I posted in another post about the firmware releases and that it didn't seem to help. I went back to using IPv6 yesterday and have had a stable connection for 24 hours and counting. I'm not sure why the previous test didn't work, but it appears to be working now. Time will tell. Re: Apple Airport Extreme Base Station and Time Capsule Firmware Updates @ChrisL So far I'm stable (Chandler, AZ) after 13 hours of using Cox's DNS and IPv6 DNS servers with IPv6 Configuration: Automatically. We'll see if this continues. EDIT: Well, it lasted 19 hours before I started having issues again. Back to Link-local only. Apple Airport Extreme Base Station and Time Capsule Firmware Updates Link for 802.11n units https://support.apple.com/kb/DL1880?locale=en_US Link for 802.11ac units (tower) https://support.apple.com/kb/DL1708?viewlocale=en_GB&locale=en_GB Maybe the above will help fix the IPv6 issues we've been facing. Re: Omaha IPv6 for airport extreme Here's a better fix that might work for you AND give you IPv6 connectivity. I'm trying the Google DNS servers (8.8.8.8, 8.8.4.4) now. In the Internet tab on your Extreme, change the DNS servers (not IPv6 DNS servers) from Cox's to Google's public servers previously mentioned. Click the Internet Options and change the IPv6 Configuration back to Automatically. So far, here in Arizona the above fix is working great. I never had any speed loss using the Link-local only and I'm still not losing any speed with the above. I also just ran a test of IPv6 fromtest-ipv6.comand received a 10/10 score with the Google DNS servers. Prior to the change when I used Cox's DNS servers I got a 0/10 score. From what I was told by Cox Internet support, IPv6 has been in my area (Phoenix, AZ) since December 2015. I'll stick with this andifCox fixes their DNS servers, then I'll go back to theirs. More from Apple regarding Cox IMAP and Apple Mail I received this today from Apple engineering regarding the slow receipt of incoming mail from Cox IMAP accounts. Unfortunately, it looks like Cox does not support the IDLE command, which explains why customers have to wait until the fetch timer triggers. CAPABILITY IMAP4rev1 UIDPLUS NAMESPACE QUOTA I would like to hear from Cox Engineering regarding this reply from Apple as to Cox's position. Thanks! Re: Paying for Premier, but getting Preferred speeds, even after upgrading my modem and router. Call Cox and have them check the line as there is a code they have to enter on their end for you to get DOCSIS 3.0 speed. I had the same issue after updating and the agent I talked to knew exactly what the issue was, changed a code, restarted my SB6141 modem and I was getting the Premier speeds.