Answered Event 7003 and Event 5719

  • Friday, May 28, 2010 11:19 AM
     
     

    I have 2x Server 2008 R2 both acting as AD DC and DNS (AD integrated) servers; one of them is also a DHCP server. Both have static ip addresses and reference themselves and each other as DNS servers.

    Whenever I boot these 2 servers I get Event 7003:

    "The SBSD Security Center Service service depends the following service: wscsvc. This service might not be installed"

    once on each sever at each boot.

    I am getting various DNS errors on my single domain including Event 5719 when my Win7 client logs on:

    "This computer was not able to set up a secure session with a domain controller in domain <my domain> 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."

    On both servers I uninstalled the DNS service, deleted these files:

    System32\dns\cache.dns
    System32\config\Netlogon.dns
    System32\config\Netlogon.dnb

    and then reinstalled DNS and ran

    ipconfig /flushdns
    ipconfig /registerdns

    on both of them. The domain is <my domain>.local

    Please can you let me know if the event 7003 is important and relevant to the event 5719 and if so how to resolve it.

    I also have a newly-installed Server 2008 R2 VM hosted in Hyper-V on a Server 2008 R2 box. This takes several minutes to start up and sits at 'Applying Computer Settings' and then after entering login details it sits at 'Applying User Settings' for several minutes more. The Event Log contains Event 1006:

    The processing of Group Policy failed. Windows could not authenticate to the Active Directory service on a domain controller. (LDAP Bind function failed). Look in the details tab for error code and description.

    "+ System
    - Event Data
      SupportInfo1 1
      SupportInfo2 5012
      Processing Mode 1
      ProcessingTimeInMilliseconds 136531
      ErrorCode 82
      ErrorDescription Local Error
      DC Name"

    I intially logged this under

    http://social.technet.microsoft.com/Forums/en-US/windowsserver2008r2virtualization/thread/89d9393a-6700-4738-8f3b-e0573c394019

     

All Replies

  • Monday, May 31, 2010 3:35 AM
    Moderator
     
     

    Hi Troy88,

     

    The SBSD Security Center Service requires the "wscsvc" service which is not included in Windows 2008 R2.

     

    Please perform a clean boot of Windows 2008 R2 DC to see if the Event 7003 continues.

    Windows Vista or Windows Server 2008

    To manually perform a clean boot of the computer in Windows Vista or Windows Server 2008, follow these steps:

    1. Click StaCollapse this imageExpand this image, type msconfig in the Start Search box, and then press ENTER.

    Collapse this imageExpand this imageIf you are prompted for an administrator password or for a confirmation, type the password or click Continue.

    1. On the General tab, click Selective startup.
    2. Under Selective Startup, click to clear the Load startup items check box.
    3. Click the Services tab, click to select the Hide All Microsoft services check box, and then click Disable all.
    4. Click OK, and then click Restart.

     

    Sincerely,

    Wilson Jia


    This posting is provided "AS IS" with no warranties, and confers no rights. Please click "Mark as Answer" when you get the correct reply to your question.
  • Wednesday, June 02, 2010 9:42 AM
    Moderator
     
     

    Dear Customer,

     

    I just wanted to say hi, and to see how things are going. I haven't heard back from you yet and I was wondering if there are any updates on the service request.

     

    Thanks.

     

    Sincerely

     

    Wilson Jia


    This posting is provided "AS IS" with no warranties, and confers no rights. Please click "Mark as Answer" when you get the correct reply to your question.
  • Wednesday, June 02, 2010 6:22 PM
     
     
    Hi Wilson Thanks for your reply. The previous one didn't generate an alert; I have had this happen before. I am on holiday this week and will be covering for others when I M back on Monday. I will try your suggestion as soon as I can and post the results here.
  • Tuesday, June 08, 2010 1:12 PM
     
     

    I have unmarked the answer as I haven't had time to check anything yet. My previous post says that I was on holiday and I am covering for other people now.

    I will investigate as soon as I can, probably in a few days' time.

  • Wednesday, June 09, 2010 3:01 PM
     
     

    Hi Wilson,

    I followed your instructions above. For the 7003 error that stopped it ocurring, which also means that it is not important. Out of interest I will investigate which of the items is responsible, but it is not the cause of my main problem.

    I followed each instruction for the 5719 in turn and rebooted after each one. Nothing made any difference and the error is still happening every time I reboot.

    These errors of themselves do not appear to be very important, but I found them when trying to get to the root of the cause of the 1006 mentioned in my original post. That is the main problem and I had thought that the 7003 or 5719 might help in finding the solution.

    Please can you suggest what I can try next to resolve the 1006 error above.

  • Friday, June 11, 2010 11:22 AM
     
     
    Any chance of a reply please?
  • Friday, June 11, 2010 11:36 AM
     
     

    Hello,

    for the DNS/reboot errors please post an unedited ipconfig /all from both DC/DNS servers and the Windows 7 machine so we can verify all settings.


    Best regards Meinolf Weber Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.
  • Friday, June 11, 2010 12:55 PM
     
     

    Hi Meinolf,

    Win7 client:


    Windows IP Configuration

       Host Name . . . . . . . . . . . . : GORDON-LAPTOP
       Primary Dns Suffix  . . . . . . . : XXXX.LOCAL
       Node Type . . . . . . . . . . . . : Mixed
       IP Routing Enabled. . . . . . . . : No
       WINS Proxy Enabled. . . . . . . . : No
       DNS Suffix Search List. . . . . . : XXXX.LOCAL

    Ethernet adapter Local Area Connection:

       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Intel(R) PRO/1000 PL Network Connection
       Physical Address. . . . . . . . . : 00-15-B7-B1-9B-50
       DHCP Enabled. . . . . . . . . . . : Yes
       Autoconfiguration Enabled . . . . : Yes

    Wireless LAN adapter Wireless Network Connection:

       Connection-specific DNS Suffix  . : XXXX.LOCAL
       Description . . . . . . . . . . . : Intel(R) PRO/Wireless 3945ABG Network Connection
       Physical Address. . . . . . . . . : 00-19-D2-53-65-A0
       DHCP Enabled. . . . . . . . . . . : Yes
       Autoconfiguration Enabled . . . . : Yes
       IPv4 Address. . . . . . . . . . . : 10.73.0.20(Preferred)
       Subnet Mask . . . . . . . . . . . : 255.0.0.0
       Lease Obtained. . . . . . . . . . : 11 June 2010 13:42:40
       Lease Expires . . . . . . . . . . : 11 June 2010 21:42:40
       Default Gateway . . . . . . . . . : 10.73.0.9
       DHCP Server . . . . . . . . . . . : 10.73.0.1
       DNS Servers . . . . . . . . . . . : 10.73.0.1
                                           10.73.0.8
       NetBIOS over Tcpip. . . . . . . . : Enabled

    Tunnel adapter isatap.XXXX.LOCAL:

       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . : XXXX.LOCAL
       Description . . . . . . . . . . . : Microsoft ISATAP Adapter
       Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes

    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

    DC1:


    Windows IP Configuration

       Host Name . . . . . . . . . . . . : XXXXpdc2
       Primary Dns Suffix  . . . . . . . : XXXX.LOCAL
       Node Type . . . . . . . . . . . . : Hybrid
       IP Routing Enabled. . . . . . . . : No
       WINS Proxy Enabled. . . . . . . . : No
       DNS Suffix Search List. . . . . . : XXXX.LOCAL

    Ethernet adapter Local Area Connection 2:

       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Intel(R) PRO/1000 GT Desktop Adapter
       Physical Address. . . . . . . . . : 00-1B-21-4C-69-81
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes
       IPv4 Address. . . . . . . . . . . : 10.73.0.1(Preferred)
       Subnet Mask . . . . . . . . . . . : 255.255.255.0
       Default Gateway . . . . . . . . . : 10.73.0.9
       DNS Servers . . . . . . . . . . . : 10.73.0.1
                                           10.73.0.8
       NetBIOS over Tcpip. . . . . . . . : Enabled

    Tunnel adapter isatap.{8733CC16-2093-4D00-923E-07791BB10DF4}:

       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 Local Area Connection* 11:

       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

    DC2:


    Windows IP Configuration

       Host Name . . . . . . . . . . . . : Test-Server2
       Primary Dns Suffix  . . . . . . . : XXXX.LOCAL
       Node Type . . . . . . . . . . . . : Hybrid
       IP Routing Enabled. . . . . . . . : No
       WINS Proxy Enabled. . . . . . . . : No
       DNS Suffix Search List. . . . . . : XXXX.LOCAL

    Ethernet adapter Local Area Connection:

       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : NVIDIA nForce Networking Controller
       Physical Address. . . . . . . . . : 00-01-6C-AD-08-5B
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes
       IPv4 Address. . . . . . . . . . . : 10.73.0.8(Preferred)
       Subnet Mask . . . . . . . . . . . : 255.255.255.0
       Default Gateway . . . . . . . . . : 10.73.0.9
       DNS Servers . . . . . . . . . . . : 10.73.0.1
                                           10.73.0.8
       NetBIOS over Tcpip. . . . . . . . : Enabled

    Tunnel adapter isatap.{8A4017F1-3D80-4FC7-997E-0D390807C9A4}:

       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 Local Area Connection* 11:

       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

    DC1 and DC2 are both Server 2008 R2 fully patched.

    • Edited by troy99 Monday, August 02, 2010 10:33 AM Remove company info
    •  
  • Saturday, June 12, 2010 11:49 PM
     
     

    Hello,

    the Windows 7 machine use a different subnet mask then the DCs, please change it to 255.255.255.0, run ipconfig /flushdns and ipconfig /registerdns , reboot and check again.


    Best regards Meinolf Weber Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.
  • Monday, June 14, 2010 1:00 PM
     
     

    Hi Meinolf,

    I did all of this and I still get the 5719 error. Any other suggestions please?

    Cheers, Gordon

  • Friday, June 25, 2010 3:10 PM
     
     
    Anybody?
  • Saturday, June 26, 2010 12:10 PM
     
     

    Hello,

    did you try with a cable connected to the switch instead of using the wireless connection to see if this helps?


    Best regards Meinolf Weber Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.
  • Monday, June 28, 2010 9:46 AM
     
     

    Hi Meinolf,

    I have just done that and there are no 5719 errors when it is wired. When I go back to wireless the 5719 comes back. It is a simple Linksys wireless switch (model WAP54G) and the wired switch (which is also the one I plugged my laptop directly into) it connects into is also unmanaged, so I doubt if there is anything in the networking equipment that can be changed.

    Cheers, Gordon

  • Tuesday, June 29, 2010 12:30 PM
     
     
    I have just opened an incident. I will post here how I get on................
  • Wednesday, June 30, 2010 10:36 AM
     
     

    Progress on the initial problem with the VM!

    The MS engineer created a second virtual network switch on the VM host and used that for the server VM. As yet I don't have an explanation of why this works, but it seems to have solved the problem. The DNS and Group Policy errors were just by-products of the fundamental network issue.

  • Friday, July 09, 2010 3:08 PM
     
     Answered

    Resolved at last!

    The host PC has a Marvell Yukon PCI Ethernet controller and a PCI-E Ethernet controller both on the motherboard. It turns out that Server 2008 R2 VMs did not like being connected to the PCI-E controller until I disabled BOTH TCP Checksum Offload AND Large Send Offload.

    The PCI controller never had a problem, even though it uses exactly the same driver. Win 7 VMs were also never affected.

    • Marked As Answer by troy99 Friday, July 09, 2010 3:08 PM
    •