login to network share

[poloshock]

Synchronization with password-protected network share will always fail, if
user didn't manually login before.
Do you plan to add default OS login fire event, if user is not logged already?
I handle it by batch file now, but it would be great if I, and anybody else,
didn't have to.. :)

Thanks,
Polo

[Zenju]

Here you go: I've made FFS show the password prompt in case a mapped network
connection is available but not logged into. In order to not jeopardize batch
scenarios, this prompt will only be shown if error handling is set to "show
popup" in batch mode, but always when running in GUI mode.
Please give me a short feedback if this works for you - I would expect it to:

[404, Invalid URL: http://ifile.it/7wos0jl/FreeFileSync_v4.1_beta2_setup.exe]

-Zenju

[poloshock]

Thanks for super-fast answer!
I installed your new beta version, but it seems not working for me. Maybe
because I actually have not mapped network drive - I am using "\\NETWORKNAME\"
prefix. Is it supported too?

[Zenju]

You're correct, the logon prompt will only come up if you had previously
mapped the network share to a drive letter. It will then use your default name
and (cached) password if available and only if this fails show the prompt.
In my tests I was kind of surprised to even "accidentally" gain access to
mapped shares, where Windows annoyingly rejected name and password probably
due to some typos on my side.

I'll make some more tests and see if I can make the prompt show even without
requiring a mapped drive.

[Zenju]

Here is the updated version: I will always show the prompt for both mapped
network shares and those refered to by UNC syntax. I've integrated it into
asynchronous directory existence checking to prevent the app from stalling in
case a network directory is not existing.
Please inform me, if you find any issues with the new version:
[404, Invalid URL: http://ifile.it/8wndirj/FreeFileSync_v4.1_beta3_setup.exe]

[poloshock]

It is still not working for me, maybe I am doing something wrong:
- boot system
- launch FFS
- on left side i type \\MYBOOKWORLD\dir; on right side C:\dir
- click compare, but only error notification shows, telling me "Directory does not exist"

If I copy left side path to explorer, it fires me login prompt, so there is no
typo. What do you think?

One more thing: I am sometimes on VPN instead of being physically at home, so
I am using "\\192.168.1.6\" path, is it not problem? Both paths don't prompt
me for any credentials with FreeFileSync_v4.1_beta3 version.

[Zenju]

> maybe I am doing something wrong:
Not necessarily. The new algorithm probably needs some fine-tuning.
I've prepared a new version which will show a messagebox, if it encounters any
errors regarding logging onto the share.
You can ignore the message boxes if they refer to a local drive, but please
send me a screenshot if you see a messagebox in combination with a network
path. I'll need the full message text for analysis.

[404, Invalid URL: http://ifile.it/raeowiz/FreeFileSync_v4.1_network_test_setup.exe]

[poloshock]

Ok, it throws this error, twice for one comparison.

[Zenju]

Are you sure the network resource is available? Error 67 is "The network name
cannot be found.". For an existing, but not connected network resource calling
"WNetGetResourceInformation" should succeed.
In case you get different error message boxes I would be interested in the
others as well.

[poloshock]

> Are you sure the network resource is available?


Yes, as I said:

> If I copy left side path to explorer, it fires me login prompt, so there is
no typo.



> Error 67 is "The network name cannot be found."


It is very strange, since in explorer it works. I also tried NET command - it
throws access denied, so it is obviously existing resource. However, if I put
non-existing network share name, it throws same error as FFS, which is correct
at this case..
Here is log from my NET command test:


C:\Users\PoloShock>net view \\MYBOOKWORLD
System error 5 has occurred.

Access is denied.


C:\Users\PoloShock>net view \\NOEXISTINGNAME
System error 53 has occurred.

The network path was not found.




> In case you get different error message boxes I would be interested in the
others as well.


No different error, just 67 one - twice times.

[poloshock]

> if I put non-existing network share name, it throws same error as FFS


sorry, almost same error.. :) But I think 53 means pretty much the same as 67
in our case?

[Zenju]

Strange, in this case we have to assume that WNetGetResourceInformation
doesn't always tell the truth. It has been working in my network setup fwiw.
The only option left, is to unconditionally always try to connect to a network
resource without any pre-existence-checking at all.
Just as the last time, I'm interested in the sequence of different messages
(if any):
[404, Invalid URL: http://ifile.it/gby17fq/FreeFileSync_v4.1_network_test_2_setup.exe]

[poloshock]

First, sorry for possible confuse-named folder Public. It is accessible
through public username and pass, so it is not quite as public as one might
think..

Now error sequence:
1. Error calling WNetGetResourceInformation: 67 for directory \\MYBOOKWORLD\Public
2. Error calling WNetAddConnection2: 1326 for directory \\MYBOOKWORLD\Public
3. Error calling WNetGetResourceInformation: 67 for directory \\MYBOOKWORLD\Public
now login is prompted...
- when I cancel it:
4. Error calling WNetAddConnection2: 1223 for directory \\MYBOOKWORLD\Public
- when I fill in correct credentials
Comparison is launched successfuly

[Zenju]

Good, the approach from the last test version shall then be the final
solution, pure and simple, unconditional connecting. With
WNetGetResourceInformation not working properly, we don't have another option
anyway.

[404, Invalid URL: http://ifile.it/cbzdvn1/FreeFileSync_v4.1_beta5_setup.exe]

[poloshock]

Great work!
I wonder if it is not against RealTimeSync philosophy, but what about
implement it there too? Maybe create some checkbox there, if not natively..?
I use RTS a lot, on desktop I have 10 instances on startup, so still, I can't
remove login through batch here.

[Zenju]

It's probably against RTS's philosophy to implement network login. Main
problem is to manage the password prompt dialog. RTS is supposed to run in the
background without needing manual intervention. With FFS's new login
capability the solutions could then be to simply have the FFS batch job run
one time outside of RTS, or set "remember password" option, in which case RTS
will login automatically since it doesn't require user interaction.