O agente remoto do NMM SQL Server do NetWorker falha ao registrar - nsrnmsqlra -i
Podsumowanie: O agente remoto do NetWorker NMM SQL Server não consegue se registrar no registro do SQL Server Erro: Não é possível abrir o canal chamado canal do client para autenticação:
Ten artykuł dotyczy
Ten artykuł nie dotyczy
Ten artykuł nie jest powiązany z żadnym konkretnym produktem.
Nie wszystkie wersje produktu zostały zidentyfikowane w tym artykule.
Objawy
O agente remoto do NMM SQL Server do NetWorker não consegue se registrar. Quando o NMM é instalado em um SQL Server, ele deve registrar (automaticamente) um agente remoto com o NetWorker.
Usando esse comando
Usando esse comando
nsrnmsqlra -i
Isso não consegue se registrar com o erro: Não é possível abrir o lado do client chamado pipe para autenticação:
a causa está relacionada ao protocolo Server Message Block do Windows (SMB).
Przyczyna
O sistema operacional Microsoft Windows usa tubos nomeados para autenticação e acesso a arquivos, impressoras e compartilhamentos.
Os tubos nomeados usam Server Message Block (SMB) como o protocolo de transporte subjacente.
Quando o SMB está desabilitado, o agente remoto do NMM falha devido à autenticação que exige o uso de tubos nomeados.
Causa raiz de engenharia definida como:
NOTAS
1. Os servidores Microsoft Windows têm o recurso SMB1 instalado por padrão.
2. A partir do Windows 2019 Server, o SMB1 não é instalado por padrão.
Portanto, se o SMB também estiver desativado ao mesmo tempo em que o SMB1 não estiver instalado, o agente remoto apresentará falha.
EXEMPLO
RESULTADO-
Os tubos nomeados usam Server Message Block (SMB) como o protocolo de transporte subjacente.
Quando o SMB está desabilitado, o agente remoto do NMM falha devido à autenticação que exige o uso de tubos nomeados.
Causa raiz de engenharia definida como:
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. Os servidores Microsoft Windows têm o recurso SMB1 instalado por padrão.
2. A partir do Windows 2019 Server, o SMB1 não é instalado por padrão.
Portanto, se o SMB também estiver desativado ao mesmo tempo em que o SMB1 não estiver instalado, o agente remoto apresentará falha.
EXEMPLO
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*********
Rozwiązanie
HABILITAR POWERSHELL do protocolo
SMB2
Set-SmbServerConfiguration -EnableSMB2Protocol $true
Confirme
Tem certeza de que deseja executar essa ação?
Executando a operação "Modify" no destino "SMB Server Configuration".
[Y] Sim [A] Yes to All [N] No [L] No to All [S] Suspend [?] Ajuda (o padrão é "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;
Właściwości artykułu
Numer artykułu: 000209922
Typ artykułu: Solution
Ostatnia modyfikacja: 17 mar 2026
Wersja: 5
Znajdź odpowiedzi na swoje pytania u innych użytkowników produktów Dell
Usługi pomocy technicznej
Sprawdź, czy Twoje urządzenie jest objęte usługą pomocy technicznej.