<div>
You can try to use <strong>curl -v URL -o some-file&nbsp;</strong> where your URL is obviously used. -v will show debug info on the connection&nbsp; (the -o to have the output not interfere with debug log).
</div>


<div>
No comment has been added to this question in more than 21 days, so it is now classified as abandoned.<br />
<br />
I have recommended this question be closed as follows:<br />
<br />
Accept: 'Michael B. Smith' (<a href="https:#a43303328" rel="ugc">https:#a43303328</a>)<br />
<br />
If you feel this question should be closed differently, post an objection and the moderators will review all objections and close it as they feel fit. If no one objects, this question will be closed automatically the way described above.<br />
<br />
seth2740<br />
Experts-Exchange Cleanup Volunteer
</div>


<div>
<div class="content wysiwyg-content fr-view">
For instance on 36875 events, the clients IP address and the requested certificate would be very useful.
</div>
</div>



For instance on 36875 events, the clients IP address and the requested certificate would be very useful.

How do I get more verbose schannel warnings on a server detailing client connection attempts information?

Exchange is the server side of a collaborative application product that is part of the Microsoft Server infrastructure. Exchange's major features include email, calendaring, contacts and tasks, support for mobile and web-based access to information, and support for data storage.