What's new in Why Can't I Connect? 1.12.1
Dec 30, 2015
- Added SSL / TLS support for Microsoft SQL server, MySql server, FTP, and IRC.
New in Why Can't I Connect? 1.12.0 (Dec 12, 2015)
- Added SSL / TLS support for IMAP, POP3, SMTP, LDAP, Usenet, and Generic Client connections.
- Added a trace showing the SSL / TLS certificate information after a connection.
- Fixed a bug when connecting a Generic Client that expects a response.
New in Why Can't I Connect? 1.11.3 (Sep 14, 2015)
- Added a cancel button to the connecting progress dialog.
- Moved the acquiring local address, binding, and acquiring server address functions to their own thread. Added a progress / cancel dialog for this thread.
- Added detection of system logout / shutdown signals to close the application, destroy temporary files, and flush the trace file.
New in Why Can't I Connect? 1.11.2 (Jul 31, 2015)
- Fixed an occasional crash primarily in Linux systems.
- In the WiFi / wired login check, test that the expected router login page is listening on port 80 before launching it in a browser.
- Fixed various small bugs.
New in Why Can't I Connect? 1.11.0 (Jun 15, 2015)
- Added the "Check WiFi / Wired Network Login" menu item to the tools menu and button to the toolbar. This function launches the default router login / TOS (Terms Of Service) IP address in your preferred browser.
- Added a check to see if the error pattern of a possible incomplete WiFi / wired network login is detected on any connection and ask if you would like to launch the default router login.
- Added some minor optimizations.
- Fixed some minor bugs.
New in Why Can't I Connect? 1.10.3 (May 25, 2015)
- 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.
- 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.
- 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.
- Switched the "Ports In Use" default port type to listening.
- Fixed a bug in the "Script Save As" to include the script run time parameters.
New in Why Can't I Connect? 1.10.2 (Apr 20, 2015)
- Optimized the "Ports In Use" and the "Neighbors" tools. The "Ports In Use" tool runs significantly faster. Both the "Ports In Use" and "Neighbors" tools' "Cancel" buttons are quicker to respond to a user request.
New in Why Can't I Connect? 1.10.1 (Jan 30, 2015)
- Added a major enhancement to the Neighbors Tool. The tool will now search by port connections as well as ICMP echo requests and the socket function getnameinfo. 15 common ports have been predefined as well as the ability to add additional ports. There is also the ability to search by ports exclusively. For example, search a range of IP address that are listening on http (port 80).
- Added a question dialog in preferences after changing the application language to synchronize the trace language.
- Now showing the currently open trace file in the status line while hovering over the 'Create / Change The Log File' menu option.
New in Why Can't I Connect? 1.10.0 (Jan 6, 2015)
- I've upgraded wxWidgets to 3.0.x
- Added host name reformatting which removes errors from an entered host name.
- Added a trace to show the original and the reformatted host name.
New in Why Can't I Connect? 1.9.1 (Nov 8, 2014)
- I changed the URL of the Knowledge Base to match the website redesign. (https://www.whycanticonnect.com/?q=knowledge-base
- A minor cosmetic change.
- A minor bug fix.
New in Why Can't I Connect? 1.9.0 (Oct 14, 2014)
- I've added the neighbors tool. This identifies all the named devices within a
- range of IP addresses. Note: The neighbors tool uses the socket function getnameinfo
- and, depending on your operating system, ICMP echo requests. These inquiries may be
- blocked by a firewall and I do NOT try to circumvent these security measures.
- I've added the MAC address in the bind trace when the trace detail level is set
- to high.
New in Why Can't I Connect? 1.8.5 (Sep 3, 2014)
- I've added a task parameters trace at the beginning of the connection tests. For example, an FTP connection test will start with the trace "Connect to an FTP Server" and display the name / IP address and the port.
- I've added the ability to select the trace detail level in the trace menu. A high detail level shows all traces. A medium detail level shows the trace elements useful to a typical user and is the default setting. A low detail level shows socket functions only. The default trace detail level may be set in the application preferences.
New in Why Can't I Connect? 1.6.3 (Jan 23, 2014)
- This version fixes a very annoying bug which lost the selected language when re-entering the Preferences Dialog.
- The language can now be selected for the application language and the trace language.
- Users can now run the application in their native language and still create and send the author a trace in his native language.