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.9.1
Release 1.9.1 is now available.
In this release:
1. Changed the url of the Knowledge Base to match the website redesign.
2. A minor cosmetic change.
3. A minor bug fix.
The new website design is friendlier but required a remapping of the pages.
I removed the border around the visible trace list.
If loading the dll for ICMP fails, I disabled the neighbors tool. I now only disable the use of ICMP echo requests. ICMP is only available in Windows installs.