Windows Domain User get "Access Denied"

[GustuvWynd]

I have a U4-423 I am testing out in a Windows Domain environment and I have upgraded it to TOS 6.0.555. I have successfully joined the domain and I get the domain users and groups options in the permissions settings on a shared folder. I have selected read or read/write access for all users and for the Domain User and Domain Admin groups. I have verified that SMB is activated on the NAS.

Yet when I try to access the shared folder via the path TOS is suggesting, I get an access denied.

Is there some other setup I am missing? All client computers can access an SMB share that is hosted on a server so I know SMB is working on my network though I have verified that the SMB1.0/CIFS Client and SMB Direct Windows features are enabled on client systems. I can ping the IP of the NAS. So this is looking like a permissions issue yet, but I don't see any other places that I could set a permission for file access on the NAS.

[GustuvWynd]

Oh...I think I have it resolved.

I cannot access it via the "\\192.168.xx.xx\FileShare" IP address path, but I can access it if I put the device's host name in the path "\\tnas\FileShare".

Typically I experience the opposite and IPs work better since there is no risk of a DNS not resolving a host name and such...so it was a ways down my list of things to try. I still find this odd that the host name resolves and not the IP, though. I have verified that my IP did not change or get blocked by a firewall. Like I said...odd.

Is this expected in TOS?

[mrslother]

Oh...I think I have it resolved.

I cannot access it via the "\\192.168.xx.xx\FileShare" IP address path, but I can access it if I put the device's host name in the path "\\tnas\FileShare".

Typically I experience the opposite and IPs work better since there is no risk of a DNS not resolving a host name and such...so it was a ways down my list of things to try. I still find this odd that the host name resolves and not the IP, though. I have verified that my IP did not change or get blocked by a firewall. Like I said...odd.

Is this expected in TOS?

This is literally the problem I am seeing with my U4-423!
I have been asking how to fix here: viewtopic.php?p=40865#p40865
but no joy yet.

From Windows any access made using a DNS host works fine (host or fqdn):

Code: Select all

\\nas\myshare

or

Code: Select all

\\nas.mydomain.com\myshare

But any access mdns or IP will be denied access:

Code: Select all

\\192.168.x.y\myshare

and

Code: Select all

\\nas.local\myshare

This happens with net use, net view and accessing UNC's directly like

Code: Select all

dir \\nas\myshare

Likewise I am having trouble logging in from linux systems regardless of UNC host:

Code: Select all

    smbclient -N //nas/myshare  <----- this works (as guest)
    smbclient -U mydomain/myuser //nas/myshare  <----- this fails with "session setup failed: NT_STATUS_ACCESS_DENIED"

The smbclient test even fails on the NAS itself (after SSH'ing in).

[RyanYang]

We recently fixed a bug related to \\nas.local\myshare, so we can try it again in the next release.
What version is your domain server, and what specific error message does your computer display when access fails?
You can try the following methods to resolve the issue:
1. Clear DNS cache: Enter `ipconfig /flushdns` in the command prompt to clear your computer's DNS cache. This can help resolve issues where domain names fail to resolve due to DNS cache problems.
2. Check Windows hosts file: Edit the hosts file on your computer (located at `C:\Windows\System32\drivers\etc\hosts`) to add domain names and their corresponding IP addresses. This ensures that the domain names resolve to the correct IP addresses.
3. Modify TOS hosts file: Edit the hosts file in TOS (located at `/etc/hosts`) to ensure domain name mappings are correct.

[GustuvWynd]

We recently fixed a bug related to \\nas.local\myshare, so we can try it again in the next release.
What version is your domain server, and what specific error message does your computer display when access fails?
You can try the following methods to resolve the issue:
1. Clear DNS cache: Enter `ipconfig /flushdns` in the command prompt to clear your computer's DNS cache. This can help resolve issues where domain names fail to resolve due to DNS cache problems.
2. Check Windows hosts file: Edit the hosts file on your computer (located at `C:\Windows\System32\drivers\etc\hosts`) to add domain names and their corresponding IP addresses. This ensures that the domain names resolve to the correct IP addresses.
3. Modify TOS hosts file: Edit the hosts file in TOS (located at `/etc/hosts`) to ensure domain name mappings are correct.

My issue was the opposite. It would not work with the IP address (\\192.168.xx.xx\myshare). It does work when I use the host name...in my case \\tnas\myshare.

Domain server is Windows Server 2019 version 1809. Clients are a mix of Win10 and Win11.
The error message was only "Access Denied". No different than if I put in the wrong user ID. It was able to reach it, but not authenticate.

[GustuvWynd]

Oops, I missed your thread. Yeah...looks like the same issue. Though it does seem to work fine with using the hostname in the path. I just prefer IPs incase the DNS decides to be stupid. Doesn't happen often, but why risk it.

[RyanYang]

Is it convenient to use the online support of our official website to make an appointment for technical engineers to solve your problems remotely?

[GustuvWynd]

That would be great, but I don't see anything on the web page for scheduling such. How do I set up an appointment? Just launch a chat?

[RyanYang]

Yes, you can schedule a suitable time after initiating the chat.

[mrslother]

Oops, I missed your thread. Yeah...looks like the same issue. Though it does seem to work fine with using the hostname in the path. I just prefer IPs incase the DNS decides to be stupid. Doesn't happen often, but why risk it.

I think we are experiencing the same issue. Mine works fine with host name or FQDN is used in the UNC. IP or mDNS names (eg. mydns.local) will fail.

TMRyan,

My system:
Windows Server 2022 domain

• Mix of different server versions (2016, 2019, 2022)
  Various desktop clients versions (10, 11)

Most of my testing is from Windows 11

I noted that various linux devices using smbclient fail when using IP address in the UNC:

Code: Select all

smbclient -U mydomain/myuser //192.168.1.98/myshare

Error is: session setup failed: NT_STATUS_ACCESS_DENIED
This particular test was actually run on the NAS device itself (via SSH).