어느 순간 Active Directory 접속이 안되는 문제
AD 접속이 안되는 PC에서는 다음과 같은 이벤트 로그가 남고 있었고,
Log Name: System
Source: Microsoft-Windows-GroupPolicy
Date: 2011-03-29 오전 8:25:24
Event ID: 1054
Task Category: None
Level: Error
Keywords:
User: SYSTEM
Computer: Win2008R2.testpc.co.kr
Description:
The processing of Group Policy failed. Windows could not obtain the name of a domain controller. This could be caused by a name resolution failure. Verify your Domain Name System (DNS) is configured and working correctly.
Log Name: System
Source: Microsoft-Windows-GroupPolicy
Date: 2011-03-29 오후 12:13:04
Event ID: 1053
Task Category: None
Level: Error
Keywords:
User: TESTPC\SeongTae Jeong
Computer: Win2008R2.testpc.co.kr
Description:
The processing of Group Policy failed. Windows could not resolve the user name. This could be caused by one of more of the following:
a) Name Resolution failure on the current domain controller.
b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller).
Log Name: System
Source: NETLOGON
Date: 2011-03-29 오전 10:07:16
Event ID: 5719
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: Win2008R2.testpc.co.kr
Description:
This computer was not able to set up a secure session with a domain controller in domain TESTPC due to the following:
There are currently no logon servers available to service the logon request.
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.
ADDITIONAL INFO
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
반면에, AD 서버에서는 다음과 같은 로그가 남아 있었습니다.
Log Name: System
Source: NETLOGON
Date: 3/29/2011 7:32:44 AM
Event ID: 5774
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: ADServer.test.co.kr
Description:
The dynamic registration of the DNS record '_ldap._tcp.test.pe.kr. 600 IN SRV 0 100 389 ADServer.test.co.kr.' failed on the following DNS server:
DNS server IP address: ::
Returned Response Code (RCODE): 0
Returned Status Code: 0
For computers and users to locate this domain controller, this record must be registered in DNS.
USER ACTION
Determine what might have caused this failure, resolve the problem, and initiate registration of the DNS records by the domain controller. To determine what might have caused this failure, run DCDiag.exe. To learn more about DCDiag.exe, see Help and Support Center. To initiate registration of the DNS records by this domain controller, run 'nltest.exe /dsregdns' from the command prompt on the domain controller or restart Net Logon service.
Or, you can manually add this record to DNS, but it is not recommended.
ADDITIONAL DATA
Error Value: DNS name does not exist.
Log Name: System
Source: NETLOGON
Date: 3/30/2011 8:00:40 AM
Event ID: 5774
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: ADServer.test.co.kr
Description:
The dynamic registration of the DNS record '_ldap._tcp.DomainDnsZones.test.co.kr. 600 IN SRV 0 100 389 ADServer.test.co.kr.' failed on the following DNS server:
DNS server IP address: ::
Returned Response Code (RCODE): 0
Returned Status Code: 0
For computers and users to locate this domain controller, this record must be registered in DNS.
USER ACTION
Determine what might have caused this failure, resolve the problem, and initiate registration of the DNS records by the domain controller. To determine what might have caused this failure, run DCDiag.exe. To learn more about DCDiag.exe, see Help and Support Center. To initiate registration of the DNS records by this domain controller, run 'nltest.exe /dsregdns' from the command prompt on the domain controller or restart Net Logon service.
Or, you can manually add this record to DNS, but it is not recommended.
ADDITIONAL DATA
Error Value: DNS name does not exist.
Log Name: System
Source: NETLOGON
Date: 3/30/2011 7:55:38 AM
Event ID: 5782
Task Category: None
Level: Warning
Keywords: Classic
User: N/A
Computer: ADServer.test.co.kr
Description:
Dynamic registration or deregistration of one or more DNS records failed with the following error:
No DNS servers configured for local system.
위의 이벤트 로그들이 서로 밀접하게 연관되어 있는지에 대해서는 확실히 알 수 없습니다. 단지, 사건이 발생한 근처의 시간대에 기록해 둘만한 가치가 있는 것들을 위주로 추려본 것입니다.
전체적으로 보면, DNS를 찾지 못하는 것에서부터 문제가 발생한 것 같은데요. 해결 방법을 검색해 보았는데 딱히 이렇다할 답이 나오지 않았습니다.
참고로, 아래의 해법들은 전혀 도움이 되지 않았습니다.
기가비트 이더넷 장치를 사용하면 도메인 컨트롤러에 연결할 수 없고 그룹 정책을 적용할 수 없다
; http://support.microsoft.com/kb/326152
Windows에서 TCP/IP에 대한 미디어 감지 기능을 해제하는 방법
; http://support.microsoft.com/kb/239924
그럼, 어떻게 해결했느냐? ... 제 블로그 글을 종종 읽어오신 분이라면 감이 잡히실 것입니다. 바로 "IPv6를 해제하는 것!"
어느 순간 갑자기 접속이 안되는 TFS 서버
; https://www.sysnet.pe.kr/2/0/1099
Unable to connect to the Microsoft Visual Studio Remote Debugging Monitor ... Access is denied.
; https://www.sysnet.pe.kr/2/0/1093
사실, 개인적으로 최근의 IPv6 문제들을 겪으면서 제가 기본적으로 고수했던 자세는 가능한 IPv6 기능을 살려 보자는 것이었습니다. 이를 위해 해결책을 찾으려고 무던히도 노력해보았는데요. 단지 제가 그 방면의 지식이 많이 부족하기도 하고, 서버 관리에 그만큼의 시간 투자를 할 수 없다는 것 때문에 쉬운 길로 돌아가는 선택을 하게 되었습니다. 게다가 더욱 아쉬운 점은, 위의 문제들이 항상 발생하는 것은 아니라서 나중에라도 시간날 때 살펴보고 싶어도 쉽게 재현이 안된다는 것!
[이 글에 대해서 여러분들과 의견을 공유하고 싶습니다. 틀리거나 미흡한 부분 또는 의문 사항이 있으시면 언제든 댓글 남겨주십시오.]