El agente remoto de NetWorker NMM SQL Server no se puede registrar: nsrnmsqlra -i

El agente remoto de NetWorker NMM SQL Server no se puede registrar. Cuando NMM se instala en un SQL Server, debe registrar (automáticamente) un agente remoto con NetWorker.
Uso de este comando

nsrnmsqlra -i 

 

Esto no se puede registrar con el siguiente error:  No se puede abrir el lado del cliente denominado canalización para la autenticación:

la causa está relacionada con el protocolo de bloque de mensajes del servidor de Windows (SMB).

El sistema operativo Microsoft Windows utiliza canalizaciones con nombre para la autenticación y el acceso a archivos, impresoras y recursos compartidos.

Las tuberías con nombre utilizan el bloque de mensajes del servidor (SMB) como el protocolo de transporte subyacente.   

Cuando SMB está deshabilitado, el agente remoto de NMM falla debido a la autenticación que requiere el uso de canalizaciones con nombre.

La causa raíz de ingeniería se define de la siguiente manera:

Named Pipe uses the SMB protocol. Please find reference link.

[[MS-WPO]: Named Pipes | Microsoft Learn|https://learn.microsoft.com/en-us/openspecs/windows_protocols/ms-wpo/4de75e21-36fd-440a-859b-75accc74487c]

This is windows requirement.
 
During authentication process, Server will create the named pipe file in the client and open the named pipe to get the RPCSEC_GSS 
credentials. But when SMB protocol is disabled,  server fails to get the details from the client.

NOTAS

1. Los servidores de Microsoft Windows tienen la función SMB1 instalada de manera predeterminada. 

2. A partir de Windows 2019 Server, SMB1 no está instalado de manera predeterminada.
Por lo tanto, si SMB también está deshabilitado al mismo tiempo que SMB1 no está instalado, el agente remoto fallará.

EJEMPLO  

POWERSHELL

//*  THIS  SHOWS  
//  SMB1  is disabled (not installed)  
//  SMB2  is enabled
//  RESULT ----  remote agent works 


PS  
Get-SmbServerConfiguration |select enablesm*

EnableSMB1Protocol EnableSMB2Protocol
------------------ ------------------
             False               True

//*  THIS  SHOWS  
//  SMB1  is disabled (not installed)  
//  SMB2  is disabled  (in Powershell)
//  RESULT ----  remote agent fails



PS 
Set-SmbServerConfiguration -EnableSMB2Protocol $False

Confirm
Are you sure you want to perform this action?
Performing operation 'Modify' on Target 'SMB Server Configuration'.
[Y] Yes  [A] Yes to All  [N] No  [L] No to All  [S] Suspend  [?] Help (default is "Y"):

PS
   Get-SmbServerConfiguration |select enablesm*

EnableSMB1Protocol EnableSMB2Protocol
------------------ ------------------
             False              False

RESULTADO-
 

nsrnmsqlra -D5 -i 2> deb5ra.txt
The remote agent resource with the same values already exists.

--
02/21/23 20:54:22.013511 Auth methods not set, using default
02/21/23 20:54:22.016510 RPC Authentication: Client failed to obtain RPCSEC_GSS credentials: Cannot open client side named pipe for authentication: The specified network name is no longer available. (Win32 error 0x40).

02/21/23 20:54:22.016510 Could not get a session key for GSS authentication.  Perhaps this authentication method is not allowed/supported by both the local and remote remote machines.
02/21/23 20:54:22.016510 Falling back to use the older protocol which does not support pipe impersonation. Perhaps were are talking to an older auth server.
02/21/23 20:54:22.017511 Auth methods not set, using default


02/21/23 20:54:26.575461 Auth methods not set, using default
02/21/23 20:54:26.576462 RPC Authentication: Client failed to obtain RPCSEC_GSS credentials: Cannot open client side named pipe for authentication: The specified network name is no longer available. (Win32 error 0x40).

02/21/23 20:54:26.576462 Could not get a session key for GSS authentication.  Perhaps this authentication method is not allowed/supported by both the local and remote remote machines.
02/21/23 20:54:26.576462 Falling back to use the older protocol which does not support pipe impersonation. Perhaps were are talking to an older auth server.
02/21/23 20:54:26.576462 Auth methods not set, using default
02/21/23 20:54:26.592460 lg_getnameinfo(): Found the entry in getnameinfo_cache ...
                 backup type: SQL Server;
                    features: Configuration, NMM;
                        name: SQL Server;
             product version: 19.7.0.54;
     remote agent executable: nsrnmsqlra;
remote agent protocol version: 1;
                        type: NSR remote agent;
02/21/23 20:54:26.595460 Received unkown message
02/21/23 20:54:26.595460 Failed to build reply object list for Unknown message
02/21/23 20:54:26.595460 Remote Agent Ending*********

HABILITAR EL protocolo

SMB2 POWERSHELL

 

 Set-SmbServerConfiguration -EnableSMB2Protocol $true

Confirme
¿Está seguro de que desea realizar esta acción?
Ejecución de la operación "Modify" en la "Configuración del servidor SMB" de destino.
[Y] Sí [A] Sí a todos [N] No [L] No a todos [S] Suspender [?] Ayuda (el valor predeterminado es "Y"):

 

 

 Get-SmbServerConfiguration |select enablesm*

EnableSMB1Protocol EnableSMB2Protocol
------------------ ------------------
             False               True

RESULT

nsrnmsqlra -D5 -i 2> deb5okra.txt
The remote agent resource with the same values already exists.

---------- DEB5OKRA.TXT

02/21/23 21:00:53.406661 lg_getnameinfo(): Successfully added entry into getnameinfo_cache ...
02/21/23 21:00:53.407661 lgto_auth for `nsrexec' succeeded
02/21/23 21:00:53.407661 Auth methods not set, using default
02/21/23 21:00:53.407661 Auth methods not set, using default
02/21/23 21:00:53.407661 Auth methods not set, using default
02/21/23 21:00:53.424661 lg_getnameinfo(): Found the entry in getnameinfo_cache ...
                 backup type: SQL Server;
                    features: Configuration, NMM;
                        name: SQL Server;
             product version: 19.7.0.54;
     remote agent executable: nsrnmsqlra;
remote agent protocol version: 1;
                        type: NSR remote agent;