How do I use "Why Can't I Connect?"
To use Bridging you want to:
1. Configure your client to connect to the Bridge Server.
2. Open the Bridge Server.
3. Connect the client to the Bridge Server.
4. Connect the Bridge Client to the server.
This will work for most circumstances, in some cases you may need to connect the Bridge Client to the server first.
I like my privacy. I don't want my personal data showing up in normal traces and sniffers. By setting “Why Can't I Connect?” tracing to “Headers And Errors Only”, only the TCP/IP conversation send / receive sizes, frequencies, and errors will show up in the trace. The actual data of the conversation will be excluded. This can often be enough to resolve the problem you're chasing without compromising customer data.
Are you developing a client or server? These are handy tools to send an entered message or the contents of a file without having to re-author or recompile your project. This was my original reason for writing this feature. It saved me a lot of development time.
Release 1.12.0
In this release
1. Added SSL / TLS support for IMAP, POP3, SMTP, LDAP, Usenet, and Generic Client connections.
2. Added a trace showing the SSL / TLS certificate information after a connection.
3. Fixed a bug when connecting a Generic Client that expects a response.
Warning: this application links to the openssl libraries. Do not download this application if this is illegal in your country.
The SSL / TLS certificate information trace shows the valid date range and subject information if the trace detail level is set to Medium. The trace additionally shows the issuer information if the trace detail level is set to High.