Opened 14 years ago

Closed 10 years ago

#979 closed Bug report (outdated)

FileZilla Server fails to list network drives.

Reported by: twilek242 Owned by:
Priority: normal Component: FileZilla Server
Keywords: Cc: twilek242, atlantisal, davinchurch, Alexander Schuch
Component version: Operating system type:
Operating system version:

Description

It seems like FileZilla Server fails to list network
drives.

I have added some network drives to my shared folders.
I have tried to map them both to the drive letter and
to the unc-path without any luck.

If I configure it like this:
Directory: Y: (wich is a network drive)
Alias: C:\<HomeDir>\AliasForNetworkDir
then the AliasForNetworkDir-folder is shown up in my
homedir catalog, but when I enter that folder none of
it's files or subfolders are listed.

Change History (3)

comment:1 Changed 14 years ago by atlantisal

In attempting this myself, I found the problem to be two
things, rights and mappings.

Filezilla Server runs as a service, and in most instances
this defaults to Local Service. Obviously, this user
doesn't have rights to any network drive. There are three
possible ways to get rights working (see below). Also,
since it runs as a service, mappings from the logged-in user
do not apply. You need to use UNC mappings as your
directory instead.

Possible rights fixes
1) Change the service LogOn to a known network user that
has rights to the network share you are accessing. (This
obviously requires the network user to have the correct
permissions to run a service which can present security issues)
2) On the computer with the network share, add rights for
the computer with Filezilla Server. (This can be set for
only the network shares and should be more secure).
3) If you're in a business environment, set both computers
to be in the same domain. Even the Local Service account
will have rights as the "Everyone" user on other computers
in the same domain. (This also opens security by requiring
the "Everyone" user to have access to the share)

Hope this helps,
Jeremy Griffith

comment:2 Changed 13 years ago by davinchurch

When running FZ as a service, it does not have access to
network drives unless you have it log in as a specific user
(which must have access to those drives, of course).

comment:3 Changed 10 years ago by eyebex

Resolution: outdated
Status: newclosed

This sounds more like a support than a feature request. Sharing mapped network driver should work, also see #2455, and follow the above tips. For sharing UNC paths directly without them being mapped to drive letters, see e.g. #2077.

Note: See TracTickets for help on using tickets.