ReadyNAS 314 refuses all incoming SMB connections with "Access Denied"

[jhu23]

I've got a ReadyNAS set up as a backup storage location for our server 2008R2 servers. I am looking to move from Rsync to Veeam, which means switching the way I connect to the NAS. I have set up a new folder and a new user account on the NAS (we do not have AD).

I have granted the account "veeam" read/write access to the folder "Veeam_Fileserver". I have also added veeam in to the file access tab. I have made sure SMB is enabled on the folder as well. I have the workgroup name set.

When I go to \\nas\veeamfolder I get prompted for credentials. Entering the user account I set up for this purpose gets rejected with access denied. I have tried using the workgroup I set (i.e. workgroup\veeam) but same result - access denied.

Any idea what I've missed?

[jhu23 · Accepted solution]

Looking at the logs you just provided I noticed the server was connecting with IPV6. I disabled IPV6 on the server's NIC and the server can now connect with no issues. Thanks for your help!

[mdgm-ntgr]

Is the NAS in the same workgroup as your PC?

Have you checked to make sure that there are no other connections to the NAS from this PC (you can do this using the "net use" command from the command prompt)?

[StephenB]

---

@mdgm-ntgr wrote:

Have you checked to make sure that there are no other connections to the NAS from this PC (you can do this using the "net use" command from the command prompt)?

---

There is a workaround here - if you need to use two credentials with the NAS for SMB sessions, then you can use one with the NAS hostname and the other with the NAS IP address.

[jhu23]

Thanks for the reply - no the server has 0 mapped network drives. It does connect to the NAS via a program called Acrosync which uses rsync. Could that be the issue?

Edited to add that yes they are both on the same workgroup

[StephenB]

---

@jhu23 wrote:

It does connect to the NAS via a program called Acrosync which uses rsync. Could that be the issue?

---

No, rsync doesn't use SMB sessions.

Assuming that your RN314 uses the default data name for it's volume, and you aren't using the default admin password...

Can you try mapping the NAS data volume to a drive letter with net use?  For instance

net use * /delete

net use t: \\nas-ip-address\data /user:admin nas-admin-password

If you aren't familiar with these commands - be careful with the typing.  The spaces and the slash directions matter.

[jhu23]

Yep, I had tried that already unfortunately. Same result - Access Denied. Tried using my Veeam user as well as Admin. (Admin's password is not default)

[mdgm-ntgr]

Please send in your logs (see the Sending Logs link in my sig).

[jhu23]

No worries, I've sent an email to the mod address with my zip file attached.

[mdgm-ntgr]

You can see the failed login attempts in smbd.log.

You are running old firmware (6.7.5). You may wish to update the firmware and see if that helps. We are using a newer version of the samba package (used for the SMB server/client) in the current firmware so it would be good to rule out the issue being something addressed by a firmware update.

[jhu23]

I see I can move to update 6.9.3, will it cause any config changes / downtime? I do not have physical access to the NAS, will it come back on its own?

[mdgm-ntgr]

It should preserve the config (except for adding anything needed for new firmware) and come back on its own but it's always best to be prepared just in case it doesn't come back up.

[jhu23]

I am now on 6.9.3 but issue still exists - access denied when attempting to access my SMB share with windows GUI or command prompt net use.

[mdgm-ntgr]

Can you provide fresh logs?

Does the user you're trying to use have the same name as the user on your PC or your computer name?

[jhu23]

I have sent another email with a new zip file. I did try creating a local account called veeam on my 2008R2 server with the same password as is on the NAS but no dice.

[mdgm-ntgr]

I wonder if there could be a firewall issue perhaps?

The authentication succeeds and milliseconds later the connection is denied.

[2018/08/23 12:20:10.841951,  2] ../source3/auth/auth.c:314(auth_check_ntlm_password)
  check_ntlm_password:  authentication for user [veeam] -> [veeam] -> [veeam] succeeded
[2018/08/23 12:20:10.904174,  0] ../lib/util/access.c:361(allow_access)
  Denied connection from IPv6 address

[jhu23 · Accepted solution]

Looking at the logs you just provided I noticed the server was connecting with IPV6. I disabled IPV6 on the server's NIC and the server can now connect with no issues. Thanks for your help!

[mdgm-ntgr]

Great! Glad that it's now solved.