No announcement yet.

DC Active Directoty issues

  • Filter
  • Time
  • Show
Clear All
new posts

  • DC Active Directoty issues

    I have a DC in a branch office that seems to have some AD issue. I can open the AD Users and Computers to modify users/groups/ and computers on that DC. I use AD to push install applications. I have all the installs local on that server and have created groups under that OU in AD.
    On that specific DC, I open AD Users/Computers and right click the OU and select properties. I select the Group Policy and select NEW. I rename the policy and then select EDIT. Under computer configuration I select Software Settings and then Software Installation. When I add the NEW PACKAGE, I point to the UNC path and the MSI file. When I select APPLY, it sits there for about 1 minute (all other DCs are faster- changes are real fast) and a message window pops up saying that the action had failed and to see the event viewer for information. When I open the event viewer under Systems it shows the following four times in a row everytime I try to create the application installation:

    This is the first one...

    Event Type: Error
    Event Source: TermServDevices
    Event Category: None
    Event ID: 1106
    Date: 5/23/2005
    Time: 12:23:29 PM
    User: N/A
    Computer: KASFP01
    The printer could not be installed.
    0000: 05 07 00 00 32 04 00 00 ....2...

    The next three are this 1 second apart.

    Event Type: Warning
    Event Source: MRxSmb
    Event Category: None
    Event ID: 3019
    Date: 5/23/2005
    Time: 1:14:59 PM
    User: N/A
    Computer: KASFP01
    The redirector failed to determine the connection type.
    0000: 00 00 00 00 04 00 4e 00 ......N.
    0008: 00 00 00 00 cb 0b 00 80 ....Ë..€
    0010: 00 00 00 00 84 01 00 c0 ....„..À
    0018: 00 00 00 00 00 00 00 00 ........
    0020: 00 00 00 00 00 00 00 00 ........

    Thanks for any help.


  • #2

    Please do the following tests:

    1. Connect the DC to other port in the switch.
    2. Check timezone/time settings on all the DCS.
    3. Check ports lbocking issues - like local FW.
    4. Upgrade to latest hotfix/service pack level.
    Best Regards,

    Yuval Sinay

    LinkedIn:, Blog:


    • #3
      So the UNC points to the server itself? Might be innocent then, if the UNC resolves to the loopback address. If so, it will go away if you use the FQDN in the UNC, like this: \\\share\software.msi

      (using the FQDN is the best way anyway, IMHO)


      • #4
        Hi wtdrisco,

        Did you remote desktop to the DC or you were on the console while performing that action?

        And if you did use remote desktop the next question should be

        Do you have a very new or "non" brand printer connected to your machine?

        If it's a yes then you you just need to run "mstsc /edit Default.rdp", uncheck connect printer.

        Please let me know how it works for you.