Article ID: 6713, created on Sep 24, 2009, last review on May 11, 2014

  • Applies to:
  • Virtuozzo containers for Windows 4.5
  • Virtuozzo containers for Windows 4.0
  • Virtuozzo for Windows 3.5.1 SP1


A container is joined to the AD domain and is configured to use obtain the IP address automatically using DHCP.

The following event is logged in the System log when you start the container:

Event Type: Error
Event Source: NETLOGON
Event Category: None
Event ID: 5719
Date: Date
Time: Time
User: N/A
Computer: Server
No Domain Controller is available for domain <domain name> due to the following: There are currently no logon servers available to service the logon request. Make sure that the computer is connected to the network and try again. If the problem persists, please contact your domain administrator.


Because the Netlogon service may start before the network is ready, the container may be unable to locate the logon domain controller.


However, after the network is ready, the container will try again to locate the logon domain controller. In this situation, the operation should be successful.

In most cases, the event ID 5719 can be safely ignored. In cases when Windows services depending on Netlogon require a correct start up order, it is recommend to apply one of the following solutions:

  • Configure the given container to use static IP instead of DHCP
  • Apply the solution provided by KB938449
  • Apply the solution described below:
  1. Download the attached file.
  2. Extract the vznetlogon.exe and vznl.cmd files (corresponding to server architecture).
  3. Copy to the %System32% folder inside the given container.
  4. Run vznl.cmd.
  5. Restart the container.


1348db476c8a5844ffbef8d503db9c15 d02f9caf3e11b191a38179103495106f 965b49118115a610e93635d21c5694a8 28d0f7cc091e3b9304fa556c03f9a940 d09cb2230ee0cfa720ed0f2a3cc39452 2897d76d56d2010f4e3a28f864d69223

Email subscription for changes to this article
Save as PDF