Mapping Network Drive

[danhall76]

Hi All,

I have searched around and come across similar issues but so far have not been able to solve this.

Have been using Truenas core for about a year now to store work files for myself and my boss.

My boss bought a new PC and gave me the one he was using. I reset to factory settings and set it all up again but now I'm having this error message when I try to map the network drive:

This is a different login box than previously (including on this machine before it was reset) and offers the below response when I click 'use different account' and enter my credentials:

It should also be noted that the new PC my boss bought works fine as does my previous machine.

To be clear, the settings on freenas have not changed, my credentials work on other machines and I am running the same OS on this PC as before the reset when it worked without issue.

Any assistance would be greatly appreciated as neither of us are clever enough to solve ourselves.


Cheers

 

[jgreco]

If you've signed into some Microsoft cloud services, AD, or other fu, you might need to use the workgroup name of the NAS, the name of the NAS, or some other sort of Microsoft-stupidity thing as the domain and include that in the username field. Try

NASNAME\yourlogin

or

NASWORKGROUP\yourlogin

for the login names. Note that this implies you may need to go to "More Choices" and "Use a different account"

 

[anodos]

You can view a log of authentication failures over SMB by running the following command:
midclt call smb.status AUTH_LOG '[["Authentication.status", "!=", "NT_STATUS_OK"]]' | jq

Piping through `jq` pretty-prints the JSON list.

 

[anodos]

Here's sample output:

Code:

  {
    "timestamp": "2022-02-17T06:23:54.645386-0800",
    "type": "Authentication",
    "Authentication": {
      "version": {
        "major": 1,
        "minor": 2
      },
      "eventId": 4625,
      "logonId": "0",
      "logonType": 3,
      "status": "NT_STATUS_NO_SUCH_USER",
      "localAddress": "ipv4:192.168.0.200:445",
      "remoteAddress": "ipv4:192.168.0.94:50628",
      "serviceDescription": "SMB2",
      "authDescription": null,
      "clientDomain": "HOMENAS",
      "clientAccount": "awalker",
      "workstation": "MACMINI-52E715",
      "becameAccount": null,
      "becameDomain": null,
      "becameSid": null,
      "mappedAccount": "awalker",
      "mappedDomain": "HOMENAS",
      "netlogonComputer": null,
      "netlogonTrustAccount": null,
      "netlogonNegotiateFlags": "0x00000000",
      "netlogonSecureChannelType": 0,
      "netlogonTrustAccountSid": null,
      "passwordType": "NTLMv2",
      "duration": 5567
    }
  }

In this case the particular mac mini in question failed to authentication with error NT_STATUS_NO_SUCH_USER.

If I query for that user on my NAS:

Code:

root@homenas[~]# midclt call user.query '[["username", "=", "awalker"]]'       
[]

It does not exist.

 

[winnielinnie]

You can try clearing the credentials cache and rebooting the computer.

From the CMD prompt:
net use * /d /y

You'll either have to reboot the computer or restart explorer.exe for it to take effect. (Rebooting the computer after clearing the credentials cache is a more sure-fire way to test this out.)

First try @jgreco's suggestion of More Choices > Use a Different Account > manually enter workgroup\loginname

 

[jgreco]

[mod note: moved to Offtopic as this isn't a Networking issue, or even really a FreeNAS/TrueNAS issue]