Outlook Anywhere no longer working after dissabling ssl 2.0
We are using Outlook 2007 and exchange 2003, with outlook anywhere up untill tonight. It was suggested that we dissable ssl 2.0 to make our exchange server more secure, I went in and made the following registry changes
(1.Click Start, click Run, type regedt32 or type regedit, and then click OK.
2. In Registry Editor, locate the following registry key: HKey_Local_Machine \ System \ CurrentControlSet \ Control \ SecurityProviders \ SCHANNEL \ Protocols \ SSL 2.0 \ Server
3. On the Edit menu, click Add Value.
4. In the Data Type list, click DWORD.
5. In the Value Name box, type Enabled, and then click OK. Note If this value is present, double-click the value to edit its current value.
6. Type 00000000 in Binary Editor to set the value of the new key equal to “0¿.)
and now we are having trouble sending and recieveing when using laptops off site. (they work fine on our network) also I don't know if this is related or not but there is a signifcant delay in sending emails out.
After noticing these problems, I went back and undid the registry edits but the problems still persist.
You need SSL for off site secure connection. Is this SBS 2003 sever?
0
Administration of Active Directory does not have to be hard. Too often what should be a simple task is made more difficult than it needs to be.The solution? Hyena from SystemTools Software. With ease-of-use as well as powerful importing and bulk updating capabilities.
SSL 1.0, 2.0 and 3.0The SSL protocol was originally developed by Netscape. Version 1.0 was never publicly released; version 2.0 was released in February 1995 but "contained a number of security flaws which ultimately led to the design of SSL version 3.0" (Rescorla 2001). SSL version 3.0 was released in 1996.
You may want to re-clarify for all here. Your original Post says: " We are using Outlook 2007 and exchange 2003" There is a huge difference between Exchange 2003 and Exchange 2007. And yes, there is a huge difference between disabling SSL and preventing users from connecting using an older revision of the protocol.
I appologize to all, It is in fact Exchange 2007. I'm not trying to dissable ssl entirely. I'm only trying to disable SSL 2.0 as it is know for having security issues.
I should add a few things. OWA has been working fine both ways, it only seems to affect Using Outlook from outside of our network (using outlook anywhere). When I try to do a send/receive I get a error (0x8004011d)
I mentioned a delay in outgoing e-mail, it is only affecting some domains, I'm pretty sure this issue is not related to the ssl issue.
sorry for the errors, I was up pretty late last night scratching my head.
well, it passed. I went and expanded all and found this in the auto discover section.
Attempting each method of contacting the Autodiscover service. The Autodiscover service was tested successfully. Test Steps Attempting to test potential Autodiscover URL https://parkdental.com/AutoDiscover/AutoDiscover.xml Testing of this potential Autodiscover URL failed. Test Steps Attempting to resolve the host name mycompany.com in DNS. The host name resolved successfully. Additional Details IP addresses returned: 9.9.9.9 -my companies wesite address Testing TCP port 443 on host mycompany.com to ensure it's listening and open. The specified port is either blocked, not listening, or not producing the expected response. Tell me more about this issue and how to resolve it Additional Details A network error occurred while communicating with the remote host.Exception details:Message: No connection could be made because the target machine actively refused it 9.9.9.9:443Type: System.Net.Sockets.SocketExceptionStack trace:at System.Net.Sockets.TcpClient.Connect(String hostname, Int32 port)at Microsoft.Exchange.Tools.ExRca.Tests.TcpPortTest.PerformTestReally()
Has the server been 'bounced' since the offending reg key was removed? Try restarting all the Exchange and IIS services - or quick and dirty => reboot the Exchange servers.
If that doesn't work, you may need to play around with the Outlook Anywhare config on the server. Make sure it's setup correctly, or reset it up again.
Tried turing off cached exchange, getting the same error. I really don't think that this is a client side issue as the only change that has been made was to the Server. I do appreciate the suggestions. untitled.JPG
This is the error you reported earlier whereas in the screenshot you have:
8004011D
Which is MAPI_E_FAILONEPROVIDER, which means it can't connect to Exchange, so forget about what I am saying about OSTs and sizes.
When you said in your post 35149171 "well, it passed..." did you mean to say "well, it failed"?
go to www.canyouseeme.org and see if it says port 443 is open to your address...
Have a look in the IIS logs and see what it is saying for your test connection. Maybe have a look in the HTTPErr#.log first to see if that is recording any errors for you. The HttpErr.log files can be found under C:\windows\system32\logfiles\HTTPErr. More details about increasing the detail in the httperr#.log http://support.microsoft.com/kb/832975
IIS logs should be under C:\Windows\system32\logfiles\W3SVC1 if you can't see your usernames then you might need to make the server log it by going into IIS Manager, Default Web Site-->Properties-->"Web Site" tab-->Properties button under "Enable Logging"-->Advanced tab-->then select all the options
Did toy have to make any change son IIS after disabling TLS 1.0? I have disabled TSL 1.0 now outlook anywhere and owa does not work on external devices.
0
Question has a verified solution.
Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.