Path failures silently ignored, should display reason

[dbareis]

Not 100% sure of the reason but probably permissions I entered a path such as "\\SomeComputer\c$", the program would not go there but also didn't display any error messages to state that (1) and error had occured and (2) the reason for the error.

[Mathias (Author)]

Yes you shown have gotten an error.

If you go to that path in windows explorer. Do you get an error then ?

I will have a look at it.

[Jungle]

When trying to enter existing but inaccessible share via Windows Explorer, standard dialog appears (see pic).
MC just doesn't connect without any message

[Mathias (Author)]

Strange.  I get a login dialog here.

I will do some more testing and investigate why that could happen.

[dbareis]

I will have another go tomorrow, this was at work connecting to another computer (highly secured) in the domain. If I remember correctly I didn't start the program under an admin account, in a similar situation explorer would normally have prompted me for userid/password.

[dbareis]

With my non-admin account on WINXP SP3 I tried "\\NoSuchComputer\c$" and  "\\PingableButSecureComputer\c$" and both of these failed, the first after an extended period of time (would be nice if the app pinged it first), the second quickly.  No error messages were displayed. No prompts for credentials. 

Just to clarify it its needed (I just started using the app)  I am typing this into the Address Tab's field. Is there any logging I can turn on? I tried to turn on the "logging" core setting, but if its logging i don't know where, tried looking for a log file in "%TEMP%" as well as the app tree.

[Jungle]

I tried to turn on the "logging" core setting, but if its logging i don't know where, tried looking for a log file in "%TEMP%" as well as the app tree.

On WinXP non-portable MC holds log files in the %userprofile%\Application data\MultiCommander\Logs

[Mathias (Author)]

I done some test it it looks like sometimes to fails silently. and sometime you get a login dialog. Don't know why you don't get a login dialog evertime. However it if it fails it should not to it silently. So that is something I will change.

Activating logging does not do anything. There is not logging around the network connection code. Might be a good to also implement that.

I will take a look at the entire network thing. And make sure it handles errors better.