Page 2 of 5

Re: Connecting to mapped network drive after Windows has booted

Posted: 07 Dec 2009 19:14
by jayfischer
Same thing with .0011 - nothing - sorry. :(

Re: Connecting to mapped network drive after Windows has booted

Posted: 07 Dec 2009 19:41
by jacky
I just tried quickly: seems the lognetworkaccess trick only works when one changes path by clicking on the Tree if you have a Locked Tree. If you use another way (List, Go To, Favorites, etc) then nothing happens. Maybe that's the problem, or maybe that event isn't triggered when the path isn't reached or something...

Re: Connecting to mapped network drive after Windows has booted

Posted: 07 Dec 2009 20:18
by jayfischer
I tried all those ways including the tree. I just tried locking the tree as suggested and selecting the mapped drive (and other drives). Same thing no dialog or message.

Re: Connecting to mapped network drive after Windows has booted

Posted: 07 Dec 2009 20:37
by admin
jayfischer wrote:I tried all those ways including the tree. I just tried locking the tree as suggested and selecting the mapped drive (and other drives). Same thing no dialog or message.
OK thanks, this result made me see something at last... maybe I'm on the right track...

Re: Connecting to mapped network drive after Windows has booted

Posted: 07 Dec 2009 22:03
by jayfischer
I saw that you have a .0012 update to fix this.

I now get the dialog you were talking about - but still no access.

This is what I get.

Proc: IsShareAccessDenied

Path = \\srv1\tera
Accessible = True
AccessDenied = False
Error = 0

XY ver 8.70.0012
OS Windows 7
Date 12/7/2009 2:54:39 PM

Re: Connecting to mapped network drive after Windows has booted

Posted: 07 Dec 2009 22:10
by jayfischer
Sorry to be a pain - but now when I get the "location not available" when I try to navigate away from that location ALL the tabs including the original "network" one give me that message with the folder name of where I was going trying to go to.

I have to restart xy then its back to good. It looks like some flag is getting set and not reset.

Re: Connecting to mapped network drive after Windows has booted

Posted: 07 Dec 2009 22:22
by PeterH
Maybe you could try stop debugging with ::lognetworkaccess 0

But, as it's a test, you maybe must end it by restarting XY. 8)

Re: Connecting to mapped network drive after Windows has booted

Posted: 07 Dec 2009 22:40
by admin
jayfischer wrote:I saw that you have a .0012 update to fix this.

I now get the dialog you were talking about - but still no access.

This is what I get.

Proc: IsShareAccessDenied

Path = \\srv1\tera
Accessible = True
AccessDenied = False
Error = 0

XY ver 8.70.0012
OS Windows 7
Date 12/7/2009 2:54:39 PM
OK, we made a little step. Now this is the problem:
Accessible = True

I thought we are talking about password protected shares which should pop a logon dialog. Or not?

Re: Connecting to mapped network drive after Windows has booted

Posted: 07 Dec 2009 22:41
by jayfischer
Sorry, I wasn't clear in my explanation. The message/error I'm getting is not the ::lognetworkaccess popup dialog but the message in the list "Location not available" for all tabs for all folders.

Re: Connecting to mapped network drive after Windows has booted

Posted: 07 Dec 2009 22:42
by admin
PeterH wrote:Maybe you could try stop debugging with ::lognetworkaccess 0

But, as it's a test, you maybe must end it by restarting XY. 8)
::lognetworkaccess 0 should indeed stop debugging.

Re: Connecting to mapped network drive after Windows has booted

Posted: 07 Dec 2009 22:44
by admin
jayfischer wrote:Sorry, I wasn't clear in my explanation. The message/error I'm getting is not the ::lognetworkaccess popup dialog but the message in the list "Location not available" for all tabs for all folders.
You say the situation got worse than before even without ever using the ::lognetworkaccess method?

@ others. Is jayfischer the only one having these problems? Come on, there must be somebody out there using mapped network drives...

Re: Connecting to mapped network drive after Windows has booted

Posted: 07 Dec 2009 22:45
by jayfischer
I thought we are talking about password protected shares which should pop a logon dialog. Or not?
Yes this is a password protected share. Windows explorer has access to it without a login dialog. My old file explorer (x2) does not - but it pops up a login dialog. XY does not.

Re: Connecting to mapped network drive after Windows has booted

Posted: 07 Dec 2009 22:50
by admin
jayfischer wrote:
I thought we are talking about password protected shares which should pop a logon dialog. Or not?
Yes this is a password protected share. Windows explorer has access to it without a login dialog. My old file explorer (x2) does not - but it pops up a login dialog. XY does not.
Strange. I fixed issues with logon on mapped drives in v6.80.0110 - 2008-03-14 13:42. Since then I had no complaints. Anything special about those shares?

Re: Connecting to mapped network drive after Windows has booted

Posted: 07 Dec 2009 22:51
by jayfischer
You say the situation got worse than before even without ever using the ::lognetworkaccess method?
I think so. I just tried it again without running ::lognetwork access and I got this.

Image

Re: Connecting to mapped network drive after Windows has booted

Posted: 07 Dec 2009 22:54
by jayfischer
Anything special about those shares?
Just that it is a domain network (win2003). Win7 64bit client.