"connect to server" should try to connect the server before creating the icon for it

Thanks for your bug report. Which version of Ubuntu are you using? I cannot reproduce the bug on the latest Dapper.

When I create an invalid windows share it creates the icon on the desktop (which can be removed by right-clicking and choosing unmount volume) and a dialog box says "[...] is not a valid location. Check your spelling and try again."

Then you are still seeing at least part of this bug. The icon on the desktop should not be created -- what is the point?

I am on 5.10.

You might want to create a bookmark for a box not running at the moment. As pointed before you can remove the icon by using the umount option from the menu. Please describe one issue by bug. I'm rejecting that one because that's not really a bug but a feature

But the dialog clearly says 'not valid'.
If this is by design, at least match up the meaning of the dialog and the result!
Or provide two buttons in the dialog, an OK and a Mount it anyway.

That's why you should open a bug by issue. It's not possible easy to track several point on one page. I've rejected the "The icon on the desktop should not be created -- what is the point?" part of the issue. What would you like to get changed? The error message only? Having the icon created and the window trying to browse the share and saying it's not connected at the moment seems fine to me

I don't know about you, but trying to connect up to a share is always a long and tedious process. I would end up with about a dozen icons on my desktop before I got anywhere, either because one system isn't set up properly or because I get the exact address wrong. (For example, I have never managed to get OS X to connect to an Ubuntu share, possibly because I have not properly understood how to set Ubuntu up to allow this.)

It doesn't say 'not connected', it says 'not valid'.
My point is quite simply that creating an icon for something that's not valid is crazy.

I'm letting the bug closed so. It's not crazy to bookmark machines you are not connect to at the moment. An administrator may want to set up places when installing the machine before connection to the network by example

It's like adding a wrong number to your address book!
I'm not saying there isn't a use case for doing this, but it shouldn't be the default, and the behaviour is inconsistent with the messages. Can you not SEE this?

I can see that but I don't agree with you. The number analogy, because there is no point to add a wrong number. That's not the same with a computer, not being connected on the computer when you do that doesn't mean that the number is not correct. Anyway reopening and setting low priority for the message which can be confusing probably

I'm still not entirely sure why someone would want to add a location when they have had no confirmation that it's correct. Even admins make typos!

I suggest the following:

"{...} is not a valid location. You may have made an error typing the address, or the remote computer may not currently be available.

[ ] Add this location anyway.

[OK]"

The checkbox for adding the location would be off by default, but the dialog should remember its state.
This should satisfy admins who add locations blind ;) and klutzes like me who just make mistakes.

I agree, it's quite frequent for me to have to delete and recreate a remote folder because of a typo. A confirmation box in that particular case is a good idea.

I've forwarded that request upstream: http://bugzilla.gnome.org/show_bug.cgi?id=350243

the issue is fixed in hardy