How do I use "Why Can't I Connect?"
Sockets are asynchronous so there is no way to accurately predict the order of events. I will go ahead and list all the possible traces here in alphabetical order.
This trace is issued when a server accepts a connection request.
This trace is issued when an error occurs on a server during a connection request.
This trace is issued when a server rejects a connection request.
This trace is issued when I resolve an IP address to a name.
This trace is called when the 'Force a socket close command after a socket shutdown command' is set in the Application Preferences and a forced close socket command is called.
This trace is called when the 'Force a socket shutdown command before a socket close command' is set in the Application Preferences and a forced shutdown socket command is called.
This trace is issued when I bind an address to a port.
This trace is issued when I have found an available TCP/IP address.
This trace is issued when I check that an address is TCP/IP.
This trace is issued when a connection is closed.
This trace is issued on a successful connection.
This trace is issued on a connection error.
This trace is issued when a name can't be resolved to an IP address
This trace is issued when there is no TCP/IP address that can be used to bind.
This trace is issued when an end of file message is received. The peer has probably shutdown.
This trace is issued when a test of a server type that generally responds with a message on connecting does not respond.
This trace is issued when the socket function getaddrinfo returns an error. getaddrinfo is the function mainly used to resolve a name to an IP address.
This trace is issued when the socket function gethostname returns an error. gethostname is mainly used to resolve the local machine name from the IP address.
This trace is issued when the socket function getpeername returns an error. getpeername is used to resolve the machine name of the peer in a connection.
This trace is issued when I resolve the local machine name.
Errors were found in the host name and the invalid characters have been removed. The original and the reformatted host name are shown in the trace.
This trace is issued when a generic server starts listening (is prepared to accept connections.)
This trace is issued when the socket function listen returns an error. Listen sets a server ready to accept connections.
This trace is issued when a connection is attempted on a server in an array of servers but the accept fails.
This trace is issued when all the servers in the array have closed.
This trace is issued when a connection is attempted on a server in an array of servers.
This trace is issued when all the servers in the array have opened.
This trace is issued when a connection is attempted on a server in an array of servers but the peer IP address and port are unavailable.
This trace is issued when a message is received.
This trace is issued when the socket function setsockopt returns an error while setting the receive buffer size.
This trace is issued when an error occurs while receiving a message.
This trace is issued when the receive timeout is set for a connection.
This trace is issued when the socket function setsockopt returns an error while setting the receive timeout.
This trace shows the resolution of an IP address to a name.
This trace is issued when the resolution of an IP address to a name fails on an error.
This trace is issued when the resolution of an IP address to a name fails on an invalid IP address.
This trace shows the resolution of a name to an IP address.
This trace is issued when the resolution of a name to an IP address can not be resolved.
This trace is issued when the resolution of a name to an IP address fails on an error.
This trace is issued when the socket function select returns an error. This should never happen.
This trace is issued when you send a message.
This trace is issued when the socket function setsockopt returns an error while setting the send buffer size.
This trace is issued when an error occurs while sending a message.
This trace is issued when the send timeout is set for the connection.
This trace is issued when the socket function setsockopt returns an error while setting the send timeout.
This trace is issued when a connection is shutdown.
This trace is issued when an error occurs during a connection shutdown.
This trace is called when I close a connection that hasn't completed shutting down.
This trace is issued when a socket exception is detected (an out of band message has been received.)
Release 1.12.4
In this release:
1. Fixed a bug where the "Server Send" dialog and the "Server Shutdown" dialog where clipping the display of the connected socket handle.
2. Removed the WiFi connect option. Lacking time and hardware to support this in all operating systems for all routers, I will reintroduce this option when possible (check the README file to restore this option at it’s current state while compiling.)
3. Updated the MinGW compiler, wxWidgets, and OpenSSL versions for the Windows binary release (this and all future releases are no longer compatible with Windows XP.)
4. Added a Raspbian / armhf debian binary release.