DeathAndPain2 10 Geschrieben 16. September 2008 Melden Geschrieben 16. September 2008 Unser Windows Server 2008 loggt für die Domänencontroller in den anderen Sites Meldungen der folgenden Art: Event ID 5810 von Source NETLOGON: During the past 4.13 hours, this domain controller has received 34 connections from dual-stack IPv4/IPv6 clients with partial subnet-site mappings. A client has a partial subnet-site mapping if its IPv4 address is mapped to a site but its global IPv6 address is not mapped to a site, or vice versa. To ensure correct behavior for applications running on member computers and servers that rely on subnet-site mappings, dual-stack IPv4/IPv6 clients must have both IPv4 and global IPv6 addresses mapped to the same site. If a partially mapped client attempts to connect to this domain controller using its unmapped IP address, its mapped address is used for the client's site mapping. The log files %SystemRoot%\debug\netlogon.log or %SystemRoot%\debug\netlogon.bak contain the name, unmapped IP address and mapped IP address for each partially mapped client. The log files may also contain unrelated debugging information. To locate the information pertaining to partial-subnet mappings, search for lines that contain the text 'PARTIAL_CLIENT_SITE_MAPPING:'. The first word after this text is the client name. Following the client name is the client's unmapped IP address (the IP address that does not have a subnet-site mapping) and the client's mapped IP address, which was used to return site information. USER ACTION Use the Active Directory Sites and Services management console (MMC) snap-in to add the subnet mapping for the unmapped IP addresses to the same site being used by the mapped IP addresses. When adding site mappings for IPv6 addresses, you should use global IPv6 addresses and not for instance temporary, link-local or site-local IPv6 addresses. The default maximum size of the log files is 20000000 bytes. The current maximum size is 20000000 bytes. To set a different maximum size, create the following registry DWORD value to specify the maximum size in bytes: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Netlogon\Parameters\LogFileMaxSize Eine schöne ausführliche Fehlermeldung, aber: In den Eigenschaften dieser Netzwerkverbindung ist der Haken bei dem Protokoll IPv6 gar nicht gesetzt. Wir arbeiten nämlich gar nicht damit. Damit sollte IPv6 doch deaktiviert sein? Wieso versucht er also was zu mappen? In der netlogon.log, von der in obiger Fehlermeldung die Rede ist, kann man erkennen, daß es um die Domänencontroller in den anderen Sites geht. Es finden sich reichlich Einträge der Form 06/25 14:52:25 UNSEREDOM: PARTIAL_CLIENT_SITE_MAPPING: NP 2002:817a:dc04::817a:dc04: Mapped address 129.122.220.4 Die "mapped address" ist die richtige lokale IPv4-Adresse des betroffenen DCs. Aber wie gesagt, der Haken beim Protokoll IPv6 ist bei allen Servern raus. Deshalb verstehe ich nicht, weshalb ich überhaupt IPv6-bezogene Fehlermeldungen bekomme. Zitieren
DeathAndPain2 10 Geschrieben 17. September 2008 Autor Melden Geschrieben 17. September 2008 bump. Zitieren
Empfohlene Beiträge
Schreibe einen Kommentar
Du kannst jetzt antworten und Dich später registrieren. Falls Du bereits ein Mitglied bist, logge Dich jetzt ein.