Rebop2015, I figured you're chances of updating Outlook 2003 would be slim to none, just wanted to point out something you may not have been aware of. Your situation is dicey given that only 1 of 7 of your accts don't work. I would say you're right that it's not likely an Outlook or IE update issue, sounds more like an acct config issue. But I'm sure you've checked the acct and matched its config to your working accts, which kind of sets your issue apart from most. Maybe the acct's config data was corrupted, might be worth temporarily disabling the acct and creating a new acct using the same config info, if you can do that in Outlook.
Peggy, all I can suggest is to see if you're using a secure connection (TLS/SSL). When I switched from port 110 to 995 that option was disabled by default, I had to tic a checkbox to enable it.
Good luck to both of you.
Someone posted in another thread to use 184.108.40.206. Not sure where that was found as the server appeared to be 220.127.116.11. But it works. Throws a certicate message which I allowed and here we are. For a few days at least until they break it again with no notice
Let me correct that. I had tried 18.104.22.168 as that is what shows when pinging pop3.comcast.net. Unsure where the other user found that IP address.
OK. Got rid of the Certificate Error by adding this to my hosts file then using pop3.comcast.net as the pop3 server:
Working - for now.
I have Outllok 2003 also and stopped being able to retrieve messages
last Wednesday night.
Did the changes you made to the POP server (adding the IP address)
Anything else you learned that might be useful?
Comcast Tier 2 tech support basically told me I'm SOL and to call Microsoft. Yeah right.
Gotta love tech support, eh?
Did you change to IP address for pop3 server? Did it work port 995? If so, add as I have a above to the hosts file then go back to pop3.comcast.net and it all should work with no certificate error. If not, you have some setting wrong.
This is a follow-up to my other posts on this thread. I am, for now, sticking to the less confusing, and working,
. My other settings, including the port number 995, are not changed.
Posters on this thread using local hosts file workarounds could be in for additional rude surprises if Comcast makes even relatively gentler changes than the one causing all this trouble.