"Location currently not available" on mapped network drive

[lian00]

1)
text get("network", 0); still works?

\\RaiDrive-Seven
\\FREEBOX
\\SEVEN-PC

2)
And difference to text get("network", 1);?

\\FREEBOX
\\SEVEN-PC

3) "It seems broken again" ... what is broken again?

Sorry, my mistake.

[admin]

So these two give the same results. Let me know if you ever happen to find that they give different results:

Code: Select all

text get("network", 1);
text get("network", 3);

[lian00]

So these two give the same results. Let me know if you ever happen to find that they give different results:

Code: Select all

text get("network", 1);
text get("network", 3);

OK.

[mitocas]

Hi everyone,
I'm not english native speaking/writing person so I'm sory about possible mistakes I write.
I have a similar problem to the one discribed in this post, and used the solution posted here but it doesent work on my situation. The problem is that i have a My cloud Home cloud and the WD Discovery aplicattion is installed that maps a network location on My cloud as Drive X:\ but XYeplorer can't find it, it doesen't show on My PC inside XYexplorer but it does show in Windows Explorer.
I could see the X:\ drive a few versions ago (can't remember wish one now) but in the last 2 or 3 versions of XYexplorer doesen't show, so I can't work with it what is very very annoying . Can anyone help me with it? thank you in advance.

[admin]

Try these 3 scripts in the XYplorer address bar. Does one of it show the UNC target of your mapped drive?

Code: Select all

text get("network", 0);
text get("network", 1);
text get("network", 3);

Does this script show the drive letter of your mapped drive?

Code: Select all

text get("drives");

[mitocas]

Hi Mr Admin,
I runed all scripts true the Aplication and I think that running the "text get("network", 1);" command i saw the UNC of the drive but the other script "text get("drives");" doesen't show the X:\ drive (mapped drive).
Anyway analysing better at the Network information in File Explorer I saw that I have two withy the same name and it's my computer name. as I opened one, it showed my computer shares, and the other has the shared folder of my cloud, and there is also another name that there is the UNC of my cloud. So basically I have three names: two BNQ and one MYCLOUD.
Hope it helped.
Thank you

[admin]

Untick both, this should help:

Configuration | General | Safety Belts, Network | Network | Fast network enumeration
Configuration | General | Safety Belts, Network | Network | Pre-check availability of servers

[mitocas]

Hi Mr Admin,

Unfortunatly that doesen't help because they were already unchecked before I wrote here my problem, I saw those "solutions" here before.
I must say that XYexplorer it's instaled on a MS Server 2016 version 1607. I don't know if this helps or not.
Thank you for the help.

[admin]

Sorry, I'm out of ideas. If text get("drives"); doesen't show the X:\ drive that's tough. That usually means the drive is not there.

You might try to tick this: Configuration | General | Tree and List | Items in Tree and List | Show hidden drives

[mitocas]

Hi Mr Admin,

In that group of items, all were checked, except "Show floppy drives" and "Hide protected operative system files".
No worries, but it's a peaty

[Borut]

I thought that the following already worked. Now it seems not to work. Maybe settings, maybe something else.

Suppose you have a server in another subnet. That means that it will not be shown in the network (tree, list), not even in MS file explorer. That is ok.

However, if you explicitly type something like this into the address bar:
\\MYTESTSERVER\c$
then you land there in MS file explorer, but not in XY (""Location currently not available"").

Can a user change this behaviour (=have I forgot something again)?

Here is what XY detects:

Code: Select all

Exist
\\MYTESTSERVER

XYplorer 20.50.0315  -  Windows 7 Professional (Service Pack 1), 32-bit, Build 7601  -  xxxxx

Path: \\MYTESTSERVER
Real Path: \\MYTESTSERVER
ExistFile: False
ExistPath: False
ExistFolder: False
ExistItemFF: False
ExistPathFF: False
ExistPathOrFile: False
ExistPathOrFileShell: True
ExistIcon: True
IsNetworkLocation: True
GetDriveType: 0 (DRIVE_UNKNOWN)
GetItemType: 4
GetFileAttributes: 0xFFFFFFFF (-1)
Owner: 
This path available in Tree: False
Current node available in Tree: True
Watchable: False
FilenamesCaseSensitive: False

AssumeServersExist: 0
PrecheckServers: 0
CacheServers: 0

  CheckServerMethod: 0
  CheckServer3: 0
  NetworkNetServerEnum: 0
  ShowAllServers: 1

MiniTreeVerifyOnSelect: 0
TreeSkipVerifyOnSelect: 0

ExistItemUNC: False
ExistPathUNC: False
ExistPathUNCQuick: False

ExistServer: True -  AccessDenied: False - AccessErrorCode: 0
IsShareAccessDenied: False - AccessErrorCode: 0
IsServerConnected: True - Return/BufferType: 0/3

[admin]

No chance. Every method known to XY says this location does not exist. :\

[dharya]

Thanks for the information.

[Borut]

No chance. Every method known to XY says this location does not exist. :\

Ok, Don, thanks. Then:

A workaround for the user is of course to define a logical drive, if free drive letters are still available. That works.

Now, from your side: I do not have any clue and am making a wild guess here... The fact is that a ping to such a drive apparently works (at least in my case). Couldn't you, after all other methods say "server not visible", try to ping it and, if you get a ping then try to proceed? Just a wild idea, as I said.

But yes, M$ sometimes uses black undocumented magic for its own purposes...

[mitocas]

if I put in the bar the full location of my shared folder... it works.