Connecting to mapped network drive after Windows has booted

Things you’d like to miss in the future...
ltmayonnaise
Posts: 9
Joined: 06 Jul 2007 13:46

Connecting to mapped network drive after Windows has booted

Post by ltmayonnaise »

XYPlorer has a problem connecting to mapped network drives that become available AFTER Windows has booted. For example, if I start my laptop after Windows has booted, or I start a guest OS in Virtualbox and then try to access their mapped network drives, XYPlorer reports them as unavailable. However, if I open Windows Explorer and then click on either mapped network drive they connect without a problem. After accessing them via Windows Explorer they magically become available in XYPlorer as well. This has been a problem for me on Windows XP, Vista and now Windows 7. I figured it's about time to report this as a bug.

Thanks for looking into this as always!
Nathan

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

Re: Connecting to mapped network drive after Windows has booted

Post by admin »

Thanks for reporting. Currently I can't do much about it though. In my setup it always works and I have no idea what could be causing this.

Reve_Etrange
Posts: 91
Joined: 19 Mar 2008 18:15

Re: Connecting to mapped network drive after Windows has booted

Post by Reve_Etrange »

Kinda related problem: I have a NAS with password-protected shares, and I cannot connect from XY. It tells me "Location currently not available", but it won't open the login/passwd popup (I must logon through Explorer).

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

Re: Connecting to mapped network drive after Windows has booted

Post by admin »

Reve_Etrange wrote:Kinda related problem: I have a NAS with password-protected shares, and I cannot connect from XY. It tells me "Location currently not available", but it won't open the login/passwd popup (I must logon through Explorer).
Hm, the login issue was fixed long ago and should work. Can anybody confirm a problem with NAS shares?

Reve_Etrange
Posts: 91
Joined: 19 Mar 2008 18:15

Re: Connecting to mapped network drive after Windows has booted

Post by Reve_Etrange »

I'm on Vista32 logged in as administrator with UAC turned off, it this helps.

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

Re: Connecting to mapped network drive after Windows has booted

Post by jayfischer »

I am having the same problem with a regular mapped drive on a server. I get "Location currently not available". If I go to "Computer" (I am using win7) on the desktop - I can browse the mapped drive.

I've tried closing XY and restarting and I still get the error. I am running XY as administrator.

In doing some more testing - I just ran x2 and it asked for username and password when trying to browse the drive - even after I was able to browse from win7's "explorer". Strange. Now in XY I am able to browse the drive.

This is a domain network - if that helps.

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

Re: Connecting to mapped network drive after Windows has booted

Post by admin »

jayfischer wrote:I am having the same problem with a regular mapped drive on a server. I get "Location currently not available". If I go to "Computer" (I am using win7) on the desktop - I can browse the mapped drive.

I've tried closing XY and restarting and I still get the error. I am running XY as administrator.

In doing some more testing - I just ran x2 and it asked for username and password when trying to browse the drive - even after I was able to browse from win7's "explorer". Strange. Now in XY I am able to browse the drive.

This is a domain network - if that helps.
Please enter

Code: Select all

::lognetworkaccess
into the address bar and ENTER.
Now try to access such a drive (before it is made available via Explorer). Do you get a message box?

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

Re: Connecting to mapped network drive after Windows has booted

Post by jayfischer »

OK I finally rebooted to test this.

After reboot - started XY.
No access to mapped network drive.
type in address bar ::lognetworkaccess <enter> nothing happened.
still no love.
ran explorer - have access to mapped drive - no creds asked for
ran x2
no access to mapped drive - but I get login creds dialog - have access now in x2
back to xy - access to mapped drive.

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

Re: Connecting to mapped network drive after Windows has booted

Post by admin »

jayfischer wrote:OK I finally rebooted to test this.

After reboot - started XY.
No access to mapped network drive.
type in address bar ::lognetworkaccess <enter> nothing happened.
still no love.
ran explorer - have access to mapped drive - no creds asked for
ran x2
no access to mapped drive - but I get login creds dialog - have access now in x2
back to xy - access to mapped drive.
If you have done this:
1 - After reboot - started XY.
2 - No access to mapped network drive.
3 - type in address bar ::lognetworkaccess <enter>
4 - Try to access mapped network drive.

and got no message box after step 4, then I cannot do anything. That was my last idea for the moment. :(

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

Re: Connecting to mapped network drive after Windows has booted

Post by jayfischer »

OK. Thanks.

If I come up with anything new - I'll let you know.

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

Re: Connecting to mapped network drive after Windows has booted

Post by admin »

jayfischer wrote:OK. Thanks.

If I come up with anything new - I'll let you know.
The next BETA version will show an additional msgbox on every location change after

3 - type in address bar ::lognetworkaccess <enter>

Let me know...

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

Re: Connecting to mapped network drive after Windows has booted

Post by jayfischer »

After installing the latest beta (to get mixed sorting - thank you!!) - I did as you wanted me to - ::lognetworkaccess <enter>.

Nothing happened. Tried to access the mapped drive - nope.

Is that what you wanted me to do? What was supposed to show after typing ::lognetworkaccess <enter>?


Jay

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

Re: Connecting to mapped network drive after Windows has booted

Post by admin »

jayfischer wrote:After installing the latest beta (to get mixed sorting - thank you!!) - I did as you wanted me to - ::lognetworkaccess <enter>.

Nothing happened. Tried to access the mapped drive - nope.

Is that what you wanted me to do? What was supposed to show after typing ::lognetworkaccess <enter>?


Jay

Code: Select all

::lognetworkaccess
puts XYplorer is in a state where every location change pops a message box. When you say nothing happens then it's actually hard to believe. :)

Please try this

Code: Select all

::lognetworkaccess 1
and then change to a mapped drive.

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

Re: Connecting to mapped network drive after Windows has booted

Post by jayfischer »

I tried ::lognetworkacess 1 <enter> - I do not get any dialog or message of any type after trying to change to ANY folder or drive including a mapped drive.

Image

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

Re: Connecting to mapped network drive after Windows has booted

Post by admin »

Please try it with 8.70.0011.

Post Reply