Netlogon 3210 windows 7
Вопрос
В домене с двумя DC на Windows 2003 есть сервер Windows 2008 R2 64-bit, со вчерашнего дня периодически становиться недоступен. Откликатся только на ping, зайти терминальный и подключиться через mmc не удалось. Недоступны сетевые приложения с него, в частности почтовый сервер (comminigate pro)
Лечиться только перезагрузкой, хардварных ошибок нет, массив работает нормально, для сетевых интерфейсов (Intel) установлены свежие драйвера
Есть подозрения, что сервер становиться недоступен после того, как в EventLog-е появляется ошибка NETLOGON, Event 3210
Log Name: System
Source: NETLOGON
Date: 05.08.2010 18:01:50
Event ID: 3210
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: MAILSERVER
Description:
This computer could not authenticate with \\dc1.firma.lan, a Windows domain controller for domain FRSD, and therefore this computer might deny logon requests. This inability to authenticate might be caused by another computer on the same network using the same name or the password for this computer account is not recognized. If this message appears again, contact your system administrator.
Event Xml:
Как с этим боротся?
Ответы
Забекапте предварительно реестр и поставьте 0xffffffff . Попробуйте также:
1. В командной строке от администратора в Win2008R2:
netsh interface tcp set global autotuninglevel=disabled
2. Редактировать ключи
Все ответы
Еще днем была вот такая ошибка
iSCSI SAN Software QA Department StarWind Software
попробуй вывести ком из домена и заново внести
NETDOM MEMBER \\MAILSERVER /JOINDOMAIN
iSCSI SAN Software QA Department StarWind Software
при загрузки все равно появляется ошибка NETLOGON 5719
ipconfig /all покажите с проблемной машины
Windows IP Configuration
Host Name . . . . . . . . . . . . : MAILSERVER
Primary Dns Suffix . . . . . . . : firma.lan
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : firma.lan
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : TEAM : Team #0
Physical Address. . . . . . . . . : AA-AA-AA-AA-AA-AA
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : aaaa::aaaa:aaaa:aaaa:aaaa%16(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.1.116(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.254
DHCPv6 IAID . . . . . . . . . . . : 486551624
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-13-1B-1C-57-AA-AA-AA-AA-AA-AA
DNS Servers . . . . . . . . . . . : 192.168.1.10
192.168.1.11
NetBIOS over Tcpip. . . . . . . . : Enabled
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft ISATAP Adapter
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Tunnel adapter 6TO4 Adapter:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft 6to4 Adapter
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv6 Address. . . . . . . . . . . : 2002:c001:110::c001:110(Preferred)
Default Gateway . . . . . . . . . : 2002:c058:6301::c058:6301
DNS Servers . . . . . . . . . . . : 192.168.1.10
192.168.1.11
NetBIOS over Tcpip. . . . . . . . : Disabled
Tunnel adapter Teredo Tunneling Pseudo-Interface:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Enabling debug logging for the Netlogon service
This article describes the steps to enable logging of the Netlogon service in Windows to monitor or troubleshoot authentication, DC locator, account lockout, or other domain communication-related issues.
Original product version: Windows 10 — all editions, Windows Server 2016, Windows Server 2019, Windows Server 2012 R2
Original KB number: 109626
More information
This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:
322756 How to back up and restore the registry in Windows
To have us enable or disable debug logging for the Netlogon service for you, go to the Here’s an easy fix section. If you prefer to fix this problem manually, go to the Let me fix it myself section.
If you’re running Windows NT, you must use the debug version of Netlogon and the required debug DLLs.
Here’s an easy fix
To fix this problem automatically, click the Download button. In the File Download dialog box, select Run or Open, and then follow the steps in the easy fix wizard.
- The easy fix solution doesn’t work if your computer isn’t part of a domain. Netlogon logging doesn’t work if the computer is joined to a domain because the Netlogon service doesn’t start.
- This wizard may be in English only. However, the automatic fix also works for other language versions of Windows.
- If you’re not on the computer that has the problem, save the easy fix solution to a flash drive or a CD, and then run it on the computer that has the problem.
Let me fix it myself
The version of Netlogon.dll that has tracing included is installed by default on all currently supported versions of Windows. To enable debug logging, set the debug flag that you want by using Nltest.exe, the registry, or Group Policy. To do it, follow these steps:
For Windows Server 2019, Windows Server 2016, Windows Server 2012 R2, Windows Server 2012, Windows Server 2008 R2, Windows Server 2008, Windows Server 2003, and Windows 2000 Server
These steps apply to Windows 2000 Server and Windows Server 2003 only when the support tools are installed. They also apply to Windows XP (if support tools are installed), Windows Vista, Windows 7, Windows 8, Windows 8.1, and Windows 10.
To enable Netlogon logging:
Open a Command Prompt window (administrative Command Prompt window for Windows Server 2008 and later versions).
Type the following command, and then press Enter:
It’s typically not necessary to stop and restart the Netlogon service for Windows 2000 Server/Professional or later operating systems to enable Netlogon logging. Netlogon-related activity is logged to %windir%\debug\netlogon.log. Verify new writes to this log to determine whether a restart of the Netlogon service is necessary. If you have to restart the service, open a Command Prompt window (administrative Command Prompt window for Windows Server 2008/Windows Vista and later versions of the operating system), and then run the following commands:
- In some circumstances, you may have to perform an authentication against the system in order to obtain a new entry in the log to verify that logging is enabled.
- Using the computer name may cause no new test authentication entry to be logged.
To disable Netlogon logging:
Open a Command Prompt window (administrative Command Prompt window for Windows Server 2008 and higher).
Type the following command, and then press Enter:
It’s typically not necessary to stop and restart the Netlogon service for Windows 2000 Server/Professional or later versions of the operating system to disable Netlogon logging. Netlogon-related activity is logged to %windir%\debug\netlogon.log. Verify that no new information is being written to this log to determine whether a restart of the Netlogon service is necessary. If you have to restart the service, then open a Command Prompt window (administrative Command Prompt window for Windows Server 2008/Windows Vista and later versions of the operating system), and then run the following commands:
Alternative methods to enable Netlogon logging:
In all versions of Windows, you can use the registry method that’s provided in the «For Windows NT, Windows 2000 Server (without the support tools), and Windows Server 2003 (without the support tools)» section.
On computers that are running Windows Server 2003 and later versions of the operating system, you can also use the following policy setting to enable verbose Netlogon logging (value is set in bytes):
Notes
A value of decimal 545325055 is equivalent to 0x2080FFFF (which enables verbose Netlogon logging). This Group Policy setting is specified in bytes.
The Group Policy method can be used to enable Netlogon logging on a larger number of systems more efficiently. We don’t recommend that you enable Netlogon logging in policies that apply to all systems (such as the Default Domain Policy). Instead, consider narrowing the scope to systems that may be causing problems by doing either of the following:
- Create a new policy by using this Group Policy setting, and then provide the Read and Apply Group Policy rights to a group that contains only the required computer accounts.
- Move computer objects into a different OU, and then apply the policy settings at that OU level.
For Windows NT, Windows 2000 Server (without the Support tools), and Windows Server 2003 (without the support tools)
These steps also apply to Windows NT Workstation, Windows 2000 Professional (without the support tools), Windows XP (without the support tools), and all newer versions of Windows that are already covered in the preceding steps. To enable logging on Windows NT and Windows 2000 (pre-service pack), you may have to obtain a checked build of Netlogon.dll.
To enable Netlogon logging:
Start Registry Editor.
If it exists, delete the Reg_SZ value of the following registry entry, create a REG_DWORD value with the same name, and then add the 2080FFFF hexadecimal value:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Netlogon\Parameters\DBFlag
It’s typically not necessary to stop and restart the Netlogon service for Windows 2000 Server/Professional or later versions of the operating system to enable Netlogon logging. Netlogon-related activity is logged to %windir%\debug\netlogon.log. Verify the new writes to this log to determine whether a restart of the Netlogon service is necessary. If you have to restart the service, open a Command Prompt window (administrative Command Prompt window for Windows Server 2008/Windows Vista and above), and then run the following commands:
Notes
- In some circumstances, you may have to do an authentication against the system to obtain a new entry in the log to verify that logging is enabled.
- Using the computer name may cause no new test authentication entry to be logged.
To disable Netlogon logging:
In Registry Editor, change the data value to 0x0 in the following registry key:
Exit Registry Editor.
It’s typically not necessary to stop and restart the Netlogon service for Windows Server 2003, Windows XP, or later versions of the operating system to disable Netlogon logging. Netlogon-related activity is logged to %windir%\debug\netlogon.log. Verify that no new information is being written to this log to determine whether a restart of the Netlogon service is necessary. If you have to restart the service, open a Command Prompt window (administrative Command Prompt window for Windows Server 2008/Windows Vista and later versions of the operating system), and then run the following commands:
Setting the maximum log file size for Netlogon logs:
The MaximumLogFileSize registry entry can be used to specify the maximum size of the Netlogon.log file. By default, this registry entry doesn’t exist, and the default maximum size of the Netlogon.log file is 20 MB. When the file reaches 20 MB, it’s renamed to Netlogon.bak, and a new Netlogon.log file is created. This registry entry has the following parameters:
Remember that the total disk space that’s used by Netlogon logging is the size that’s specified in the maximum log file size times two (2). It’s required to accommodate space for the Netlogon.log and Netlogon.bak file. For example, a setting of 50 MB can require 100 MB of disk space. Which provides 50 MB for Netlogon.log and 50 MB for Netlogon.bak.
As mentioned earlier, on Windows Server 2003 and later versions of the operating system, you can use the following policy setting to configure the log file size (value is set in bytes):
For more information, click the following article numbers to view the articles in the Microsoft Knowledge Base:
247811 How domain controllers are located in Windows
Did this fix the problem
Check whether the problem is fixed. If the problem is fixed, you’re finished with this section. If the problem isn’t fixed, you can contact support.