Guest User

Untitled

a guest
Apr 24th, 2015
1,384
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 3.18 KB | None | 0 0
  1. This Error 4 times - 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.
  2.  
  3. TCP/IP failed to establish an outgoing connection because the selected local endpoint was recently used to connect to the same remote endpoint. This error typically occurs when outgoing connections are opened and closed at a high rate, causing all available local ports to be used and forcing TCP/IP to reuse a local port for an outgoing connection. To minimize the risk of data corruption, the TCP/IP standard requires a minimum time period to elapse between successive connections from a given local endpoint to a given remote endpoint.
  4.  
  5. THis error twice The IO operation at logical block address 22f66d73 for Disk 0 was retried.
  6.  
  7. HP Ethernet 1Gb 4-port 331i Adapter #3: The network link is down. Check to make sure the network cable is properly connected.
  8.  
  9. Name resolution for the name _ldap._tcp.dc._msdcs.XXXXXXXXXXX.local. timed out after none of the configured DNS servers responded.
  10.  
  11. Microsoft Windows Server has detected that NTLM authentication is presently being used between clients and this server. This event occurs once per boot of the server on the first time a client uses NTLM with this server.
  12.  
  13. NTLM is a weaker authentication mechanism. Please check:
  14.  
  15. Which applications are using NTLM authentication?
  16. Are there configuration issues preventing the use of stronger authentication such as Kerberos authentication?
  17. If NTLM must be supported, is Extended Protection configured?
  18.  
  19. Details on how to complete these checks can be found at http://go.microsoft.com/fwlink/?LinkId=225699.
  20.  
  21. Time Provider NtpClient: This machine is configured to use the domain hierarchy to determine its time source, but it is the AD PDC emulator for the domain at the root of the forest, so there is no machine above it in the domain hierarchy to use as a time source. It is recommended that you either configure a reliable time service in the root domain, or manually configure the AD PDC to synchronize with an external time source. Otherwise, this machine will function as the authoritative time source in the domain hierarchy. If an external time source is not configured or used for this computer, you may choose to disable the NtpClient.
  22.  
  23. Faulting application name: spoolsv.exe, version: 6.2.9200.16384, time stamp: 0x501080ef
  24. Faulting module name: LMADPPLANG.DLL, version: 13.1.14.0, time stamp: 0x51f8bcb7
  25. Exception code: 0xc0000005
  26. Fault offset: 0x0000000000157330
  27. Faulting process id: 0x638
  28. Faulting application start time: 0x01d07d9a4c53bfcb
  29. Faulting application path: C:\Windows\System32\spoolsv.exe
  30. Faulting module path: C:\Windows\System32\LMADPPLANG.DLL
  31. Report Id: b7914ea0-e98d-11e4-9402-9c8e99568c63
  32. Faulting package full name:
  33. Faulting package-relative application ID:
  34.  
  35. The Print Spooler service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 5000 milliseconds: Restart the service.
  36.  
  37. THis error this morning: The IO operation at logical block address 22f66d73 for Disk 0 was retried.
Advertisement
Add Comment
Please, Sign In to add comment