ERR2:7711 Unable to retrieve the DNS hostname for the migrated com

Discussion in 'Server Migration' started by Ully, Apr 9, 2010.

  1. Ully

    Ully Guest

    ADMT v3.1
    Full Message:
    Unable to retrieve the DNS hostname for the migrated computer
    '<hostname>.<sourcedomain>.local'. The ADSI property cannot be found in the
    property cache. (hr=0x8000500d)

    This is the error I'm getting when testing a migration of computers. All
    machines are running XP SP3. I had to disable the anti-virus to install the
    agent. The message is a bit vague about whether the name resolution problem
    is in the source or target domain.

    I had managed to work out most of the snags we've come across, as this is
    the first time I've used ADMT, but there is almost no information about this
    error by google or bing and nothing on the Microsoft Help and Support Site.
    Any clues? And thinks in advance.
     
    Ully, Apr 9, 2010
    #1
    1. Advertisements

  2. Ully

    Ully Guest

    Update:
    Just found these two on the computer to be migrated:

    Event Type: Warning
    Event Source: LSASRV
    Event Category: SPNEGO (Negotiator)
    Event ID: 40960
    Date: 09/04/2010
    Time: 11:24:33
    User: N/A
    Computer: T03-03
    Description:
    The Security System detected an attempted downgrade attack for server
    cifs/<targetdc>.<targetdomain>.local. The failure code from authentication
    protocol Kerberos was "There are currently no logon servers available to
    service the logon request.
    (0xc000005e)".

    For more information, see Help and Support Center at
    http://go.microsoft.com/fwlink/events.asp.

    Event Type: Warning
    Event Source: LSASRV
    Event Category: SPNEGO (Negotiator)
    Event ID: 40961
    Date: 09/04/2010
    Time: 11:24:33
    User: N/A
    Computer: T03-03
    Description:
    The Security System could not establish a secured connection with the server
    cifs/<targetdc>.<targetdomain>.local. No authentication protocol was
    available.

    For more information, see Help and Support Center at
    http://go.microsoft.com/fwlink/events.asp.

    The account running the migration has full administrative access on both
    domains.
     
    Ully, Apr 9, 2010
    #2
    1. Advertisements

  3. The 40961 errors are not the errors related to your DNS hostname query errors.

    DNS is specific to each forest. Part of migrating from one domain to another domain in a different forest, is you must setup DNS resolution capabilities between both entities. The easiest is to setup a Conditional Forwarder from domainA.local to domainB.local's DNS server, and vice versa. This way anything in domainA.local can resolve domainB.local's records.

    Also, do not use the ISP's DNS server in any machines IP properties. If so, thatwill surely give you errors. Also make sure you do not use the router as a DNS address. Same thing. The router or the ISP have no information about the internal domain names. Setup a Forwarder to the ISP.

    I hope that helps.


    --
    Ace

    This posting is provided "AS-IS" with no warranties or guarantees and confers no rights.

    Please reply back to the newsgroup or forum for collaboration benefit among responding engineers, and to help others benefit from your resolution.

    Ace Fekay, MVP, MCT, MCITP EA, MCTS Windows 2008 & Exchange 2007, MCSE & MCSA 2003/2000, MCSA Messaging 2003
    Microsoft Certified Trainer
    Microsoft MVP - Directory Services

    If you feel this is an urgent issue and require immediate assistance, please contact Microsoft PSS directly. Please check http://support.microsoft.com for regional support phone numbers.
     
    Ace Fekay [MVP-DS, MCT], Apr 16, 2010
    #3
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.