Connecting to mapped network drive after Windows has booted

Things you’d like to miss in the future...
Forum rules
When reporting a bug, please include the following information: your XYplorer version (e.g., v27.90.0047), your Windows version (e.g., Win 11), and your screen scaling percentage (e.g., 125%). We recommend adding your Windows version and screen scaling percentage to your profile or signature. This will make debugging much easier for us.
jayfischer
Posts: 61
Joined: 22 Nov 2009 21:28

Re: Connecting to mapped network drive after Windows has booted

Post by jayfischer »

Same thing with .0011 - nothing - sorry. :(

jacky
XYwiki Master
Posts: 3106
Joined: 23 Aug 2005 22:25
Location: France
Contact:

Re: Connecting to mapped network drive after Windows has booted

Post 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...
Proud XYplorer Fanatic

jayfischer
Posts: 61
Joined: 22 Nov 2009 21:28

Re: Connecting to mapped network drive after Windows has booted

Post 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.

admin
Site Admin
Posts: 64862
Joined: 22 May 2004 16:48
Location: Win8.1, Win10, Win11, all @100%
Contact:

Re: Connecting to mapped network drive after Windows has booted

Post 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...

jayfischer
Posts: 61
Joined: 22 Nov 2009 21:28

Re: Connecting to mapped network drive after Windows has booted

Post 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

jayfischer
Posts: 61
Joined: 22 Nov 2009 21:28

Re: Connecting to mapped network drive after Windows has booted

Post 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.

PeterH
Posts: 2826
Joined: 21 Nov 2005 20:39
Location: DE W11Pro 24H2, 1920*1200*100% 3840*2160*150%

Re: Connecting to mapped network drive after Windows has booted

Post 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)

admin
Site Admin
Posts: 64862
Joined: 22 May 2004 16:48
Location: Win8.1, Win10, Win11, all @100%
Contact:

Re: Connecting to mapped network drive after Windows has booted

Post 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?

jayfischer
Posts: 61
Joined: 22 Nov 2009 21:28

Re: Connecting to mapped network drive after Windows has booted

Post 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.

admin
Site Admin
Posts: 64862
Joined: 22 May 2004 16:48
Location: Win8.1, Win10, Win11, all @100%
Contact:

Re: Connecting to mapped network drive after Windows has booted

Post 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.

admin
Site Admin
Posts: 64862
Joined: 22 May 2004 16:48
Location: Win8.1, Win10, Win11, all @100%
Contact:

Re: Connecting to mapped network drive after Windows has booted

Post 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...

jayfischer
Posts: 61
Joined: 22 Nov 2009 21:28

Re: Connecting to mapped network drive after Windows has booted

Post 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.

admin
Site Admin
Posts: 64862
Joined: 22 May 2004 16:48
Location: Win8.1, Win10, Win11, all @100%
Contact:

Re: Connecting to mapped network drive after Windows has booted

Post 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?

jayfischer
Posts: 61
Joined: 22 Nov 2009 21:28

Re: Connecting to mapped network drive after Windows has booted

Post 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

jayfischer
Posts: 61
Joined: 22 Nov 2009 21:28

Re: Connecting to mapped network drive after Windows has booted

Post by jayfischer »

Anything special about those shares?
Just that it is a domain network (win2003). Win7 64bit client.

Post Reply