Outlook 2003 Can Not Connect To SSL Servers
RF
I am running Outlook 2003 on top of Vista Home Premium with Windows Live One
Care for security.
Over last year, AT&T (ex SBC)/Yahoo directed all of their users to change
port settings on e-mail servers to SSL connections (ports 995 and 465).
For last few months no problems, then I began receiving error "0x800CCC7D"
and could no longer connect to outgoing SMTP server; according to MS
article kb/289967 this is allegedly an error on server side.
After extended discussion with AT&T tech support, they advise that there is
no general fault on their server; their Tier 2 ran diagnostic on their end
and confirmed that server can accept outgoing e-mails from my account. They
also confirmed all of my client settings are correct (as indeed they have
worked fine in past). They claim it is client issue.
With some advise on broadband discussion boards I have attempted following:
1) turned off both Firewall and e-mail scanning in One Care;
2) booted in Safe Mode with Networking
3) bypassed router with direct connection to modem (I am using DSL service)
4) launched "detect and repair"
None have worked. As a temporary fix, I have reset ports to prior non-SSL
server, but this has triggered stream of warnings from AT&T that I am not
allowed to keep using these servers and they will soon be disconnected.
Can anyone provide any insight as to why client is suddenly unable to
connect via SSL?
Unless anyone can suggest other alternatives, my next step is to uninstall
and reinstall Outlook client. I have several GBs of e-mail in various *.pst
folders, as well as contacts, etc. Can anyone point me to comprehensive
step by step plan for doing so that will not risk my data?
Is it possible to uninstall just Outlook and reinstall without disturbing
entire MS Suite, or is better to do global reinstall?
Thanks for your interest,
RF
![neo [mvp outlook]'s profile photo](https://lh3.googleusercontent.com/a/default-user=s40-c)
neo [mvp outlook]
make sure have have Office 2003 Service Pack 3 installed.
"RF" <rob...@vistawire.net> wrote in message
news:w4UBk.1020$x%.47@nlpi070.nbdc.sbc.com...
RF
Thanks Neo:
Yes, I have SP3 installed. No, the ISP insists I use port 465 for their SSL
server. Could this be a client issue?
"neo [mvp outlook]" <n...@discussions.microsoft.com> wrote in message
news:u41Wp$PHJHA...@TK2MSFTNGP02.phx.gbl...
neo [mvp outlook]
software. Do you think they would be receptive to looking at this thread?
"RF" <rob...@vistawire.net> wrote in message
news:0RVBk.1110$be....@nlpi061.nbdc.sbc.com...
RF
Neo:
Nope, they're too busy proving it isn't their problem:
http://www.dslreports.com/forum/r21141780-Re-General-SBCATT-SSL-Server-Alert
"neo [mvp outlook]" <n...@discussions.microsoft.com> wrote in message
news:eqtrAOXH...@TK2MSFTNGP05.phx.gbl...
N. Miller
> Out of curiosity, do they support port 587 for message submission? If yes,
> make sure have have Office 2003 Service Pack 3 installed.
While 'smtp.att.yahoo.com:587' does work, it will also result in a warning
about using an "insecure" port (Yahoo! does not require TLS on port 587).
The only port Yahoo! wants their customers (including their 'at&t Yahoo!
HSI' customers) to use is port 465 w/SSL.
--
Norman
~Oh Lord, why have you come
~To Konnyu, with the Lion and the Drum
neo [mvp outlook]
have to use netsh to turn off tcp's auto-tuning. Whether or not this is
actually playing a role with your connection issue is anyone's guess w/out
taking a network trace.
Have you tried turning off the global auto-tuning feature?
How to:
Start an elevated command prompt session (e.g. right click on command prompt
and select run as administrator since we need to bypass UAC)
Type:
netsh interface tcp set global autotuninglevel=disabled
To undo,
Start an elevated command prompt session
Type:
netsh interface tcp set global autotuninglevel=normal
"RF" <rob...@vistawire.net> wrote in message
news:7FhCk.1248$ZP4...@nlpi067.nbdc.sbc.com...
neo [mvp outlook]
mention that the IANA has changed their mind that port 465 should be used
for something else. In any event, I was surprised that they didn't go with
port 587 since that is the "new" port for e-mail clients to submit messages
to mail servers.
So out of curiosity, does 587 work with the SSL/TLS option turned on in
Outlook 2003 SP2 or newer?
"N. Miller" <anon...@msnews.aosake.net> wrote in message
news:17jyuk47...@msnews.aosake.net...
RF
Negative. port 587 will not connect to Yahoo/AT&T/SBC's SSL server. It
only allows an unauthenticated connection, which Yahoo is migrating away
from (and warning users to discontinue).
Looks like I will have to clear my desk and try a reinstall of my Outlook
client. Hopefully, tomorrow AM.
Thanks for the interest and I will let you know whether the reinstall is
successful.
"neo [mvp outlook]" <n...@discussions.microsoft.com> wrote in message
news:uAqANpi...@TK2MSFTNGP03.phx.gbl...
RF
To any way interested in this issue:
I have completely reinstalled my Office 2003 Suite (including Outlook 2003)
all the way back to SP3, and I still not connect to the AT&T/SBC/Yahoo smtp
SSL server via port 465.
There seems to be no explanation or solution for this issue.
"RF" <rob...@vistawire.net> wrote in message
news:w4UBk.1020$x%.47@nlpi070.nbdc.sbc.com...
neo [mvp outlook]
other list and posted the Outlook 2003 troubleshooting log for POP3/SMTP.
The log file clearly shows that Outlook tried to secure the port two
different ways and couldn't. Hence me saying that it might not be a desktop
issue, but a server issue.
I quickly scanned your posts again and probably missing it, but did you try
Windows Mail works to see if it works?
"RF" <rob...@vistawire.net> wrote in message
news:sSQCk.1586$YU2....@nlpi066.nbdc.sbc.com...
N. Miller
One 'at&t Yahoo! HSI' customer has reported a solution to his problem, here:
http://www.dslreports.com/forum/r21143256-Cant-send-Email
Last post in the thread; user claims he is using MS Outlook 2003.