“Why Can't I Connect?” open source socket application.

[cohmstede]

Hi

I've created an open source application I think you might find handy. It's called “Why Can't I Connect?” and as the name implies, it is used primarily to find TCP/IP connectivity problems. I have presets for common server types: Microsoft SQL, MySQL, FTP, SFTP, IMAP, POP3, SMTP, IRC, LDAP, and Usenet. You may also create a generic client to any server and port as well as create a generic server / listening socket on any available port. There is the ability to insert my application between existing clients and servers (bridging.) There is a handy tool for resolving names to IP addresses and IP addresses to names. There is also the ability to create arrays of listening sockets.

The application is released GPLv3 and free to download. I've tested it in Linux, Windows XP, Vista, and 7. I will continually be adding more functionality. Here's the link if you're interested:
http://sourceforge.net/projects/wciconnect/

 

[John Connor]

Can this work to find out WIFI connection issues or is it more for servers and stuff?

Edit Just downloaded it. Looks like it's meant more for servers. Cool app though! Make a great addon to UBCD4WIN.

 

[cohmstede]

You are correct, this is more for finding errors connecting to servers, but it could tell you at what point your WIFI connection is breaking down. You could find this by opening a generic client and trying to connect on any port (listening or not) on a computer on your WIFI network (This could also be an internet address e.g. Google.com on port 80.) The trace will show how far you were able to get. First, the application will try to find a bindable address. If you see the trace:
Could Not Find Bindable Address
you could not reach DHCP and were never assigned an IP address. Otherwise you will see:
Bindable Address Found
the next step is to connect to the named server. If you see the trace:
Could Not Find Address
or
Connect error
getaddrinfo failed
chances are you are not reaching the DNS server. If you get beyond this point, your WIFI is probably OK and you should be looking elsewhere for the error. Here's an example of a successful trace in my application:
http://sourceforge.net/p/wciconnect/wiki/TraceExample/
You can also find this example in the help that comes with the application.

Hope this helps.

 

[cohmstede]

Release 1.6.1 is now available.

http://sourceforge.net/projects/wciconnect/

In this release I've:

1. Improved the find function to search in text or hexadecimal and find across rows in send and receive traces.

2. Added the application preference to set bridge tracing to show send details only, receive details only, or both send and receive details.

3. Fixed a bug that would occasionally lose track of the log file name.

4. Added the application preferences to show line numbers for the viewable and / or log file traces.

5. Narrowed down the error trace possible causes to be more responsive to the returned error code.

 

[Gryz]

If you want to make your tool useful, the first and most important feature would be: make sure that all errors are readable and understandable for low-tech people.

"Could Not Find Bindable Address"

WTF does that mean ?
And how are people supposed to know it means that you don't have an IP address ?
There are a zillion reasons why people can't have an IP address. DHCP problems could be one. But it could also be the simple fact someone didn't plug in an ethernet-cable. Or they used the wrong WiFi password.

I'm capable of fixing my own networking problems. But I know what I'm doing. If you build a tool like this, which could be very useful, you are building it for people who don't know what they're doing. I would be 99% would not be able to google and find out what those cryptic error messages mean. So you need to explain. Explain in detail. Explain in simple words. Explain what could cause the problem. And explain how they could troubleshoot it. And maybe even fix it. That is the only way to make your tool useful. If you do it right, you could become even famous ! 🙂 Good luck.

 

[cohmstede]

Long time since I last posted here but I remembered there was a question about WiFi. I've made too many enhancements to my application to list here but my latest release has a "Check WiFi / Wired Network Login" menu item and button. The most common WiFi error I've found is the login / TOS (Terms Of Service) web page was never called for the WiFi network. The "Check WiFi / Wired Network Login" function resolves the default router login address and launches it in your preferred browser.

https://www.whycanticonnect.com/