Call now to talk to an automation expert — (512) 345-2211

Knowledge Base

Enter search queries below or use the tag links to the right to browse the knowledge base by category (Show All Tags).

Robo-FTP Server fails to show directory listing when home directory is a network share

The symptoms for this issue are that if you set up a network share as a home directory, an FTP client connecting to Robo-FTP Server will not be able to see a directory listing for that home directory.

If you are running Robo-FTP Server as NETWORK SERVICE and you want to use a network share as a virtual folder or home directory for a user you must give the computer account for the machine running Robo-FTP Server read access to the folder. Computer accounts are not by default returned by the search when adding security principals. You must click the object type dialog and check the computers box to get it to return them. This is because NETWORK SERVICE is not a user account. It is actually the computer account for the computer upon which that service is running.

NOTE: A simpler and more secure option is to simply run Robo-FTP Server as a domain user account and make sure that user has access to the share in question.

Article last updated: 2017-07-11

Tags: Robo-FTP Server, permissions

Need help figuring out where to start?

Our sales staff is available to answer product questions and help you determine if Robo-FTP is a good match for your project.

Call Now: (512) 345-2211