Tools

Error: Permission denied by Serv-U access rule on the home directory

Permission denied by Serv-U access rule is caused by permission. To fix it, you need to use a domain service account that has permission to the shared folder.

First published date

4/23/2019 8:24 PM

Last published date

3/14/2025 10:15 PM

Overview

The error “Permission denied by Serv-U access rule on the home directory ex. \\servername\sharedfolder” normally occurs when the user logs in to Serv-U. Usually, this happens if the home directory is on a network shared path or UNC path. It indicates that Serv-U service account has no permission to the share path especially if it’s running as a local system account.

When Serv-U access the home directory on a shared path, it impersonates the local system account, and you will get rejected if the system account has no permission. It can also happen if the user or group properties does not have permission configured. 

When a user authenticates via Window Authentication, this error may also show if the proper permission is not configured correctly. The user may also get the issue if the home directory is configured at the Windows AD profile. In this case, the NTFS permission will apply to the user home directory.

Product section

Serv-U Managed File Transfer & Serv-U FTP Server

Cause

  • Serv-U service account has no permission to the shared directory.
  • AD user account does not have read permission to the root home directory

Resolution

Check the Serv-U logon service account if it is under the Network Service or a domain admin account.

1. If it is on Network Service, make sure that the home directory also has Network Service permission. Refer to: Running Serv-U under NETWORK SERVICE

2. Use a domain service account that has permission to the shared directory.

  • Open Window Services.
  • Select the Serv-U File Server.
  • Go to Log on tab.
  • Select this account and specify the domain account.
  • Click OK and restart Serv-U service.


Note: Always double check if the user or a group has permission configured in the directory access tab.

3. If the user is via Windows authentication.

  •  Make sure that the AD user account is added to the NTFS permission of the home directory.
  • If NTFS permission is already added but still getting permission issue, make sure that the Serv-U service account or the AD user account has permission to the root home directory at least read.


Example: 
The user home directory is \\sharedfolder\usershome\userfolder, and NTFS permission was already added to the “userfolder”
The root home directory is \\sharedfolder\usershome and make sure either service account or AD user has at least read permission

For instances where the home directory being used is the Home Folder specified in the Active Directory user profile (for Windows Authentication or LDAP Authentication), this is most likely a network path.

  • Set a service account to be used by the Serv-U service to have permissions to the network path. OR
  • Configure Serv-U to use a local folder by enabling the 'Use Windows User group home directory instead of account home directory' option by going to Domains > Users > Windows Authentication or LDAP Authentication > check the Enable the 'Use Windows User group home directory instead of account home directory' box and save the changes.