XYplorer Beta Club

.

.

Hard to debug for me as my network drives all show the correct label.

.

1. ExpanDrive.. which version?
2. the SFTP locations, are they on different servers?
3. what's the config for each of the mapped SFTP drives?
4. is the one that isn't showing up as named a different server software/ftp deamon?

The more info you give Don, the more likely he is to be able to find the bug

I also have this same problem.

ExpanDrive v1.8.4

Mounted drives appear named correctly in Windows Explorer, but in XY they all appear as "Network Drive".

Tthis is for two differnt servers, one on the LAN and one remote.

The config does not seem to matter -- there are not many options in ExpanDrive. just driver letter, directory to mount, server login credentials.

The same "Network Drive" labels are also shown in the drives listing (select top tree node)?

yes.

ryanagler wrote:yes.

Are these drives unconnected mapped drives?

I am not sure what you specifically mean by "unconnected"? ExpanDrive connectes to a remote filesystem via SSH and maps some part of that filesystem to a drive letter on the local computer. On my computer ExpanDrive created server1 (G:) which is to one remote computer and an server2 (H:) to another remote computer. I can actively browse those drives in both XY and Windows Explorer.

The issue is that XY is not naming the drives correctly in the tree like Explorer is.

In Explorer they show as:

server1 (G:)
server2 (H:)

And is XY as:

Network Drive (G:)
Network Drive (H:)

The word "unconnected" (or so, translated from German) is shown in the Type column in the drives listing for mapped drives that are not connected yet. But I think it is not relevant for the problem here anywhere. The term "Network Drive" is not from XY but returned by an API (at your system, not here). Looks like there is nothing I can do.

THere must be something you can do if the proper name is show in Windows Explorer?

ryanagler wrote:THere must be something you can do if the proper name is show in Windows Explorer?

Rememer that WE has some special 'privledges' that other products just don't have access to...not saying that this is one of those but it has happened before.

Actually nevermind about this -- ExpanDrive 2.0 was releasted just in the last few days and that has fixed it. Thanks!