topic Re: 8.2 C-Mode cifs create error message - MS_LSA in Network and Storage Protocols

8.2 C-Mode cifs create error message - MS_LSA

ARTHUR_STUDY — Mon, 13 Jan 2014 03:42:01 GMT

Hi All, Thanks a lot first!

Does anyone know how to fix this issue which I meet when I try to create a cifs server in my 8.2 C-Mode.

NetApp: 8.2 C-Mode

AD: Windows 2003 Enterprise Server , 192.168.1.150 (In fact, I used this AD to create cifs server in my 8.1.1 C-Mode successfully, but don't know why it doesn't work for 8.2 )

DNS: 192.168.1.150

Vserver: security style : cifs ( I got the same error message below when I chose unix here on another test )

Data Lif: 192.168.1.188 (AD server can ping to this Lif, meanwhile 8.2 C-Mode can also ping AD server)

C-M82::vserver cifs> create -vserver vs_nas2 -cifs-server cifs_20 -domain sun.com

In order to create an Active Directory machine account for the CIFS server, you must

supply the name and password of a Windows account with sufficient privileges to add

computers to the "CN=Computers" container within the "sun.com" domain.

Enter the user name: ADMINISTRATOR

Enter the password:

Error: CIFS server creation procedure failed

[ 103] Loaded the preliminary configuration.

[ 167] Created a machine account for the Cifs server in the

domain

[ 168] Connecting to LSA server abcserver.sun.com (192.168.1.150)

**[ 174] FAILURE: 'CifsServer' configuration not available

[ 176] Unable to connect to abcserver.sun.com through the192.168.1.188 interface

[ 177] No servers available for MS_LSA, vserver: 3, domain: sun.com.

[ 177] Could not find Windows SID

'S-1-5-21-751731-2604463755-2935551411-512'

[ 189] Deleted existing account

'CN=CIFS_20,CN=Computers,DC=sun,DC=com'

Error: command failed: Failed to create CIFS server CIFS_20. Reason: SecD Error: no

server available.

-----------------------------DNS information is shown below-------------------------------------

C-M82::vserver services dns hosts> show

Vserver Address Hostname Aliases

---------- -------------- --------------- ----------------------

vs_nas 192.168.1.150 abcserver.sun.com

C-M82::vserver services dns> show

Name

Vserver State Domains Servers

--------------- --------- ----------------------------------- ----------------

vs_nas enabled sun.com 192.168.1.150

vs_nas2 enabled sun.com 192.168.1.150

2 entries were displayed.

Best Regards

Re: 8.2 C-Mode cifs create error message - MS_LSA

dchilton — Mon, 13 Jan 2014 19:38:11 GMT

Hi David,

Which cluster lif are you logging in through? Which node is it on?

Can you provide a network interface show output?

There is a condition where the DNS connection to the DC breaks if the interface you log in for management does not have a network interface that connect to the DC.

This situation might occur if the vserver you are using vs_nas2 is located on a different node than the management interface you are logging into (cluster management or node management).

Thanks,

Dan Chilton

Re: 8.2 C-Mode cifs create error message - MS_LSA

ARTHUR_STUDY — Tue, 14 Jan 2014 02:11:53 GMT

Hi Dan,

Thanks a lot for your reply.

I changed the DNS setting in 8.2 by modifying the entry in DNS, adding DNS host. and I also modify the timezone. After I reboot the AD server, I can create the CIFS server now.

I am really not very sure which step correct this issue. But your input definitely helped me a lot! Thanks a lot!

Best Regards

Re: 8.2 C-Mode cifs create error message - MS_LSA

dchilton — Tue, 14 Jan 2014 11:59:16 GMT

Hi David,

I am so glad it is working now. All of the steps you took were good troubleshooting steps for when CIFS set-up is failing.

Best Regards,

Dan Chilton

Re: 8.2 C-Mode cifs create error message - MS_LSA

kodavali — Thu, 06 Feb 2014 06:30:58 GMT

Hi David,

most common cause of these errors during the CIFS server creation are :

1. time skew difference between the DC and the controllers : max accepted time skew difference is 5 min. if the difference is higher than that then we get no logon servers available error.

2. DNS configuration - either it is DNS server is taking longer time to respond to the queries or there is DNS name space disjoin issue.

Regards,

Chowdary

Re: 8.2 C-Mode cifs create error message - MS_LSA

jha71 — Thu, 27 Oct 2016 12:32:22 GMT

what was the solution?

Currently I habe a similiar Issue:

Error: Machine account creation procedure failed
[    82] Loaded the preliminary configuration.
[   111] Created a machine account in the domain
[   112] Successfully connected to ip 10.30.253.1, port 445 using
           TCP
[   113] Unable to connect to LSA service on dc01.gym-hksb.local
           (Error: RESULT_ERROR_SPINCLIENT_SOCKET_RECEIVE_ERROR)
[   114] Successfully connected to ip 10.30.253.3, port 445 using
           TCP
[   114] Unable to connect to LSA service on dc02.gym-hksb.local
           (Error: RESULT_ERROR_SPINCLIENT_SOCKET_RECEIVE_ERROR)
[   115] No servers available for MS_LSA, vserver: 4, domain:
           gym-hksb.local.
**[   115] FAILURE: Unable to make a connection
**         (LSA:GYM-HKSB.LOCAL), result: 6940
[   115] Could not find Windows SID
           'S-1-5-21-1131981276-2882716370-3949356162-512'
[   119] Deleted existing account
           'CN=FILE02,CN=Computers,DC=gym-hksb,DC=local'

Re: 8.2 C-Mode cifs create error message - MS_LSA

Gast — Tue, 10 Jan 2017 07:44:06 GMT

Uns hat diese Lösung geholfen.

http://www.g-offline.com/index.php/arec-datenbank/windows-server/item/domain-beitreten-der-angegebene-netzwerkname-ist-nicht-mehr-verfuegbar-windows-server-2012-r2

Lösung 3

Ein neues "Feature" der R2 Version von Windows Server 2012.

Navigiere auf dem Server mit dem Registry-Editor nach:

HKEY_LOCAL_MACHINE > SYSTEM > CurrentControlSet > Services > LanmanServer > DependOnService

und ändere den Wert von "SamSS Srv2" auf "SamSS Srv"

Re: 8.2 C-Mode cifs create error message - MS_LSA

J_Banas — Wed, 28 Jun 2017 22:24:17 GMT

I had this issue today. The cause was SMBv1 had been disabled on domain controllers to mitigate recent global ransomware outbreaks (WannaCry and Petya). Reenabling SMBv1 on one of the domain controllers fixed the issue and allowed the cifs server to be created successfully.