Go Premium for a chance to win a PS4. Enter to Win

x
?
Solved

Exchange Server 2013 SP1 (KB3184736) Problem

Posted on 2016-09-15
4
Medium Priority
?
686 Views
Last Modified: 2016-09-20
Hello EE,

I've installed Security Update For Exchange Server 2013 SP1 (KB3184736) on a Windows 2012 R2 Server via Microsoft Windows Update (unfortunately a Domain Controller).

Outlook 2013 (with last Servicepack) can't connect to Exchange Server which have worked before MS Update. (always prompt for User-login)
OWA ist working without any Problems.

If I want to start Exchange 2013 - Powershell I got the message:
similar (translated from German Server)
In Connection of "FQDN-ofExchange-Server" occurs following Error: The Win-RM Client has return a http Status-code "307" from Remote-WS-Services.

I don't know where to start to isolate the Problem.

OWA, Exchange console via Webbrowser, IIS works properly.

Do you track with this KB3184736 Problem or have some tips for me?

Thanks in advance!

reredok
0
Comment
Question by:reredok
  • 2
  • 2
4 Comments
 
LVL 44

Expert Comment

by:Amit
ID: 41799890
One option is to remove this KB and check again. I skipped this KB for my system. Microsoft is known for releasing bad patches. So, I wait minimum 3 months, before installing it. Or last option to give a call to MS.
0
 
LVL 4

Accepted Solution

by:
reredok earned 0 total points
ID: 41801069
this temporary workaround works for me:

1. In Outlook Profile set AUTH to NTLM
2. Disable Cache Mode if active
3. Disable coded communication between Exchange and Client
4. Disable XPhone or any other telephon software (outlook addins)
5. Reconfigure outlook profile from MAPI/HTTP to RPC/HTTP (Exchange Server IP Address, AD Account resolving. Set AD Account in EXchange Management console to user@domain.local = internal eMail address)
6. Start Outlook - with success edit AD Account to external eMail Address
7. Send and recieve eMail Test

nastily bargains have happened : First the MS Exchange Update; a never known external Exchange certificate and a silly telephon software... as if I did not deal already enough ....
0
 
LVL 44

Expert Comment

by:Amit
ID: 41801528
Thanks for sharing work around.
0
 
LVL 4

Author Closing Comment

by:reredok
ID: 41806215
no other solution found
0

Featured Post

Free Tool: IP Lookup

Get more info about an IP address or domain name, such as organization, abuse contacts and geolocation.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

The main intent of this article is to make you aware of ‘Exchange fail to mount’ error, its effects, causes, and solution.
Mailbox Corruption is a nightmare every Exchange DBA wishes he never has. Recovering from it can be super-hectic if not entirely futile. And though techniques like the New-MailboxRepairRequest cmdlet have been designed to help with fixing minor corr…
This video discusses moving either the default database or any database to a new volume.
Exchange organizations may use the Journaling Agent of the Transport Service to archive messages going through Exchange. However, if the Transport Service is integrated with some email content management application (such as an antispam), the admini…
Suggested Courses

927 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question