XP SP2: cannot access Disk Manager (LDM) on remote Win 2000 systems>>>

From: Dragan Misina (Dragan_Misina_at_SPECTRUMSIGNAL.COM)
Date: 08/24/04

  • Next message: Russ: "Re: XP SP2: cannot access Disk Manager (LDM) on remote Win 2000 systems>>>" 
    Date:         Tue, 24 Aug 2004 13:00:05 -0700
To: NTBUGTRAQ@LISTSERV.NTBUGTRAQ.COM

    After installing XP SP2 I cannot use the Computer Management from my
    system to access the Disk Manager (LDM) on remote Win 2000 systems. This
    worked fine while I had XP SP1 and it still works from other XP SP1 and
    W2K systems. When I try to access, I get different errors:
     
    1. If I first try to access, it says I don't have rights to access it
    (I'm a member of the domain admins) and it shows DCOM error in System
    log on the destination system:
     
    Event Type: Error
    Event Source: DCOM
    Event Category: None
    Event ID: 10005
    Date: 8/24/2004
    Time: 11:21:13 AM
    Description:
    DCOM got error "The service cannot be started, either because it is
    disabled or because it has no enabled devices associated with it. "
    attempting to start the service NtmsSvc with arguments "-Service" in
    order to run the server:
    {D61A27C6-8F53-11D0-BFA0-00A024151983}
     
    For more information, see Help and Support Center at
    http://go.microsoft.com/fwlink/events.asp.

     
    2. If I now try to access the local system and than again to the remote
    one, I got the following error:
    "The Disk Manager console failed to connect to the remote computer
    because the Disk Manager remote service is not in the Windows Firewall
    exception list. Add the Disk Management service (dmremote.exe) to the
    Windows Firewall list and try again"
    All this while the Windows Firewall is turned off. In the System log on
    the remote system there is the entry:
     
    Event Type: Error
    Event Source: LDM
    Event Category: None
    Event ID: 2
    Date: 8/24/2004
    Time: 11:39:33 AM
    User: N/A
    Description:
    Access is denied. (80070005).

    3. After adding dmremote.exe to the Windows Firewall exception list, I
    get the following error:
    " The Disk Management console failed to connect to the remote computer
    because the RPC port is not opened in the Windows Firewall. Open the
    port by adding the RPC port (TCP port 135) to the Windows Firewall
    exception list and try again."
     
    4. After adding this port to the exception list and try to access the
    remote LDM, I get the error:
    "An unexpected error has occurred. Check the System Event Log for more
    information on the error. Close the Disk Management console, then
    restart Disk Management or restart the computer".
     
    In the System log on the remote system there is the same LDM error:
    Access is denied. (80070005).

    If I keep Computer Management open, some time the nmc will crash with
    the following error in the local Application log:
    Event Type: Error
    Event Source: Application Error
    Event Category: None
    Event ID: 1000
    Date: 8/24/2004
    Time: 12:08:27 PM
    User: N/A
    Description:
    Faulting application mmc.exe, version 5.1.2600.2180, faulting module
    unknown, version 0.0.0.0, fault address 0x0003019a.
     
    For more information, see Help and Support Center at
    http://go.microsoft.com/fwlink/events.asp.
    Data:
    0000: 41 70 70 6c 69 63 61 74 Applicat
    0008: 69 6f 6e 20 46 61 69 6c ion Fail
    0010: 75 72 65 20 20 6d 6d 63 ure mmc
    0018: 2e 65 78 65 20 35 2e 31 .exe 5.1
    0020: 2e 32 36 30 30 2e 32 31 .2600.21
    0028: 38 30 20 69 6e 20 75 6e 80 in un
    0030: 6b 6e 6f 77 6e 20 30 2e known 0.
    0038: 30 2e 30 2e 30 20 61 74 0.0.0 at
    0040: 20 6f 66 66 73 65 74 20 offset
    0048: 30 30 30 33 30 31 39 61 0003019a
    0050: 0d 0a ..

    Any idea how to fix this?
     
    Thanks,
    Dragan Misina [ Senior Network Systems Analyst, IT ]
    Spectrum Signal Processing Inc.
     

    -----
    NTBugtraq Editor's Note:

    Want to reply to the person who sent this message? This list is configured such that just hitting reply is going to result in the message coming to the list, not to the individual who sent the message. This was done to help reduce the number of Out of Office messages posters received. So if you want to send a reply just to the poster, you'll have to copy their email address out of the message and place it in your TO: field.
    -----

  • Next message: Russ: "Re: XP SP2: cannot access Disk Manager (LDM) on remote Win 2000 systems>>>"