Comment 5 for bug 1400772

#3

Here is how I see things.

1) don't display two different error message for the same error

2) try to connect to the server before displaying a message (to fix #4).
Of course, the connection must not bock the ui thread

As for the error message, I have no idea.
It depends on what SAMBA gives us as error: are those codes? Or full fledged string that one must have to translate?

And about the button, I would stay with connect.
The button performs the same action, it should have the same label.
Changing it because there is an error ranges from confusing and borders to nagging.