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.10.3
In this release:
1. Changed the visible trace to be easier to read. The trace shows in your normal font except for hexadecimal traces which show in a monospace font. Function headers display in blue, errors display in red, and warnings display in green. This matches to the look and feel of the "Why Can't I Connect?" Android companion app.
2. Changed the remembering of a server name to the drop down list from when it is connected to when it's IP address is resolved.
3. Changed the default timeouts from 60 seconds to 20 seconds. This only effects new installs. Previous installs will still need to change the timeouts in the preferences dialog.
4. Switched the "Ports In Use" default port type to listening.
5. Fixed a bug in the "Script Save As" to include the script run time parameters.