[not possible] Useful error messages

[Alumian]

Ok so,
I'm sitting here trying to connect to my guild Teamspeak server, and it just keeps on saying "Failed to connect to server". Apart from being one of the absolute worst practices in programming, using this nondescript message prevents us from diagnosing the problem and actually getting stuff done.
My suggestion is actually putting in USEFUL error messages so that we can actually fix problems!

[jjackman]

Client cant know what is wrong with the connection. It could be firewall, wrong server address/port or other network problem. It is something between server and client and they cant print any better message.

[Alumian]

Well ventrilo did it, and it is actually possible to diagnose the problem. Even error messages as simple as, connection timed out is helpful. But by giving such a generic message, it provides absolutely no troubleshooting feedback what so ever.

[dante696]

Alumian go on Tools > client Log and you will get every information about, where it does not work.
But you can not say if it is a client or server problem, when you can not conenct to a server.