Why Can't I Connect?
“Why Can't I Connect?” makes it easy to diagnose TCP/IP connection problems. It traces through all steps of the process and gives error codes, descriptions, and possible solutions for all TCP/IP errors.
Connect to common servers:
Create a generic client or server
A generic client can connect to any type of server given the right server name / IP and port.
Create a generic server to mimic a server on any port (if available.)
Use the advanced menu options to step through the entire socket process (Bind, Connect / Listen, Send, Shutdown, Close).
You may send text or the contents of files on generic, advanced, and bridged sockets.
Bridging allows you to insert “Why Can't I Connect?” between an existing client and server. You may then trace / analyze / diagnose the conversation between the two.
Open Multiple Servers
Open servers (listening sockets) across a range of ports.
Tracing is in both hexadecimal and ASCII. It may be set to the screen and / or a log file. The amount of tracing may be set to 'All', 'Headers And Errors Only', 'Errors Only', or 'None'.
I've tested on Fedora and Ubuntu Linux. Windows XP, Vista, and Windows 7. I am releasing a source tar, 32 bit rpm, deb, and Windows install exe. The 32 bit Windows executable runs fine in 64 bit Windows systems. 64 bit Linux systems, however, should compile from source.
wxWidgets 2.8.x is required to build. Once statically linked, there are no special requirements.
wxWidgets 2.8.x is required.
Sorry, I currently don't own a Mac to develop on. I'm looking for a used one at a reasonable price. Once found, I'll go ahead and make a Mac release.
Source code can be found at: https://sourceforge.net/projects/wciconnect/files/
The Source Forge main page for this project can be found at: https://sourceforge.net/projects/wciconnect/
Please report any bugs, help requests, and enhancement requests here.
Join the mailing list: https://lists.sourceforge.net/lists/listinfo/wciconnect-discussion