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.0
In this release:
1. Upgraded wxWidgets to 3.0.x
2. Added host name reformatting which removes errors from an entered host name.
3. Added a trace to show the original and the reformatted host name.
wxWidgets to 3.0.x:
Windows users should notice little if any differences. Linux users may see many user interface changes depending on the GTK+ theme they are using. There are problems with some controls while using certain themes (Oxygen-gtk for example.) As these are known problems for other applications, I haven't made any changes as of yet.
Check the Information section of the Knowledge Base for detailed release notes.