Ich versuche (erfolglos) die Remote-Authentifizierung bei einem Linux-basierten Netzwerk-Switch bei Windows Server 2012 R2 RADIUS mithilfe von PAP. Die folgenden Ereignisprotokolle werden angezeigt:
Veranstaltung 1
The audit log was cleared. Subject: Security ID: <account domain>\<account name> Account Name: <account name> Domain Name: <account domain> Logon ID: 0x67364F48
Ereignis 2
The computer attempted to validate the credentials for an account. Authentication Package: MICROSOFT_AUTHENTICATION_PACKAGE_V1_0 Logon Account: <account name> Source Workstation: Error Code: 0x0
Ereignis 3
A logon was attempted using explicit credentials. Subject: Security ID: SYSTEM Account Name: AuthenticationServer$ Account Domain: <account domain> Logon ID: 0x3E7 Logon GUID: Account Whose Credentials Were Used: Account Name: <account name> Account Domain: <account domain> Logon GUID: Target Server: Target Server Name: localhost Additional Information: localhost Process Information: Process ID: 0x3e4 Process Name: C:\Windows\System32\svchost.exe Network Information: Network Address: - Port: - This event is generated when a process attempts to log on an account by explicitly specifying that account’s credentials. This most commonly occurs in batch-type configurations such as scheduled tasks, or when using the RUNAS command.
Ereignis 4
An account was successfully logged on. Subject: Security ID: SYSTEM Account Name: AuthenticationServer$ Account Domain: <account domain> Logon ID: 0x3E7 Logon Type: 3 Impersonation Level: Impersonation New Logon: Security ID: <account domain>\<account name> Account Name: <account name> Account Domain: <account domain> Logon ID: 0x675FF2EE Logon GUID: Process Information: Process ID: 0x3e4 Process Name: C:\Windows\System32\svchost.exe Network Information: Workstation Name: Source Network Address: - Source Port: - Detailed Authentication Information: Logon Process: IAS Authentication Package: MICROSOFT_AUTHENTICATION_PACKAGE_V1_0 Transited Services: - Package Name (NTLM only): - Key Length: 0 This event is generated when a logon session is created. It is generated on the computer that was accessed. The subject fields indicate the account on the local system which requested the logon. This is most commonly a service such as the Server service, or a local process such as Winlogon.exe or Services.exe. The logon type field indicates the kind of logon that occurred. The most common types are 2 (interactive) and 3 (network). The New Logon fields indicate the account for whom the new logon was created, i.e. the account that was logged on. The network fields indicate where a remote logon request originated. Workstation name is not always available and may be left blank in some cases. The impersonation level field indicates the extent to which a process in the logon session can impersonate. The authentication information fields provide detailed information about this specific logon request. - Logon GUID is a unique identifier that can be used to correlate this event with a KDC event. - Transited services indicate which intermediate services have participated in this logon request. - Package name indicates which sub-protocol was used among the NTLM protocols. - Key length indicates the length of the generated session key. This will be 0 if no session key was requested.
Ereignis 5
Special privileges assigned to new logon. Subject: Security ID: <account domain>\<account name> Account Name: <account name> Account Domain: <account domain> Logon ID: 0x675FF2EE Privileges: SeSecurityPrivilege SeTakeOwnershipPrivilege SeLoadDriverPrivilege SeBackupPrivilege SeRestorePrivilege SeDebugPrivilege SeSystemEnvironmentPrivilege SeEnableDelegationPrivilege SeImpersonatePrivilege
Ereignis 6
An account was logged off. Subject: Security ID: <account domain>\<account name> Account Name: <account name> Account Domain: <account domain> Logon ID: 0x675FF2EE Logon Type: 3 This event is generated when a logon session is destroyed. It may be positively correlated with a logon event using the Logon ID value. Logon IDs are only unique between reboots on the same computer.
Diese Protokolleinträge scheinen darauf hinzuweisen, dass die Authentifizierungsanforderung erfolgreich war. Ein Wireshark-Capture weist jedoch auf das Gegenteil hin:
Hier sind die Access-Request (Code 1) -Attribut-Wertepaare, bei denen einige tatsächliche Werte durch Platzhalter ersetzt wurden:
t=User-Name(1): <user name> t=User-Password(2): Decrypted: <password> t=NAS-IP-Address(4): 192.168.1.1 t=NAS-Identifier(32): <hostname> t=Calling-Station-Id(31): 192.168.1.2 t=NAS-Port(5): 5451 t=NAS-Port-Type(61): virtual(5)
Als Antwort bekomme ich eine Zugangsverweigerung (Code 3).
Nur diese beiden RADIUS-Pakete werden ausgetauscht. Ich würde erwarten, dass ein Access-Accept angezeigt wird, das die von mir konfigurierten herstellerspezifischen Attribute enthält.
In "Active Directory-Benutzer und -Computer" habe ich eine Rolle des Gruppenbereichs "Global" und des Gruppentyps "Sicherheit" erstellt. Diese Rolle hat ein Mitglied des entsprechenden Typs.
In "Network Policy Server" habe ich einen RADIUS-Client erstellt und aktiviert, der keine Shared Secret-Vorlage verwendet, und ich habe das Shared Secret manuell konfiguriert. Der Lieferantenname hat den Typ "RADIUS-Standard".
In "Network Policy Server" habe ich eine aktivierte Netzwerkrichtlinie mit diesen Attributen erstellt:
- Grant access - Type of network access server: Unspecified - A condition specifying the connecting user is a member of a Windows Group (which it is) - Authentication Methods: PAP - Standard RADIUS attribute FramedProtocol=PPP - Vendor-Specific RADIUS attributes: As appropriate for the device - NAP Enforcement: Allow full network access - Multilink and Bandwidth Allocation Protocol: Server settings determine Multilink usage - Encryption (all choices selected): "Basic encryption (MPPE 40-bit)", "Strong encryption (MPPE 56-bit)", "Strongest encryption (MPPE 128-bit)", "No encryption" - IP Settings: Server settings determine IP address assignment
Hat jemand Vorschläge, wie ich das Problem isolieren kann?
Danke im Voraus!