• State Suggested Answer
  • +1 person also asked this people also asked this
  • Locked Locked
  • Replies 21 replies
  • Answers 1 answer
  • Subscribers 20 subscribers
  • Views 32911 views
  • Users 0 members are here
Options
Related
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Unable to connect to remote registry service. The network path was not found in RUM when trying to move computers

marisol.jackson
over 8 years ago

Hello,

I am needing some help with using the Migration Manager 8.11. I am able to discover, and run the processing command in RUM, however when trying to move the computer I am getting this error message. "Unable to connect to remote registry service. The network path was not found". I am able to ping from source to target and from target to source by netbois name. We also added the domain name to the DNS Suffix list. The interesting thing is, if we move to a server segment and assign a static ip then we can move the computer with no issue. We also tried to statically put in IP and reserve the IP in the DHCP reservation but the moved failed. Any other suggestions I can try?

 

Thanks,

Marisol

  • 0 over 8 years ago
    Marisol

    There are a few things to check.

    1. Is the remote registry service running? By default it not running.
    2. Is the firewall enabled on the workstation?

    Normally the agent will deploy and there is a warning the the remote registry service is not running. This service needs to be running.
    • 0 over 8 years ago
      Sorry forgot to mention. Yes Remote registry is running. I can get to the computer if I tried to connect to it by registry. and firewall is turned off.
      • 0 over 8 years ago
        Just to confirm, using regedit from the resource update manager server, you can open the workstation registry?
        • 0 over 8 years ago
          That is correct. My thinking is that the vlan that the workstations are on are using DHCP and the server is not using DHCP. Do we need to add anything within the DHCP settings?
          • 0 over 8 years ago
            Any other ideas before I contact support?
            • 0 over 8 years ago

              "The network path was not found" means that using the hostname provided, we can not connect to the requested resource. 

              Have you looked directly at the logs? Please post it. 

              • 0 over 8 years ago
                9/29/2017 12:56:28 PM 4004 UTC -4:00, Eastern Daylight Time
                9/29/2017 12:56:28 PM 4004 CVYHJ3X92V, Windows Server 2012 R2 Standard Edition x64
                9/29/2017 12:56:28 PM 4004 ================================================================================
                9/29/2017 12:56:28 PM 4004 Dell Migration Manager RUM Controller Service version: 8.11.3.1.
                9/29/2017 12:56:28 PM 4004 Executing move operation.
                9/29/2017 12:56:28 PM 4004 Starting to move computer: oms-martic-01.
                9/29/2017 12:56:28 PM 4004 Moving computer from source domain OLYMPUS.MX.LOCAL to target domain OAI.
                9/29/2017 12:56:28 PM 4004 Move options: restart computer: TRUE, update last domain: TRUE, save source account: TRUE.
                9/29/2017 12:56:28 PM 4004 Restart options: timeout: 60 seconds, force applications to be closed: FALSE, message: Your computer will be restarted because it has been joined to a new domain..
                9/29/2017 12:56:28 PM 4004 Move will add 3 additional accounts to local administrators group.
                9/29/2017 12:56:28 PM 4004 Additional account: OAI\OMS-ServerAdmins.
                9/29/2017 12:56:28 PM 4004 Additional account: OAI\ITS-LocalAdminWorkstations.
                9/29/2017 12:56:28 PM 4004 Additional account: OAI\Domain Admins.
                9/29/2017 12:56:28 PM 4004 Using account for access to source computer: svc_mmad@olympus.mx.local.
                9/29/2017 12:56:28 PM 4004 Resolving DC for domain: OLYMPUS.MX.LOCAL.
                9/29/2017 12:56:28 PM 4004 DC resolved to: OMSSRVDC01.olympus.mx.local.
                9/29/2017 12:56:28 PM 4004 Resolving DC for domain: OAI.
                9/29/2017 12:56:28 PM 4004 DC resolved to: CVYHJ3G92V.
                9/29/2017 12:56:28 PM 4004 Impersonating user: \svc_mmad@olympus.mx.local.
                9/29/2017 12:56:28 PM 4004 Performing move.
                9/29/2017 12:56:28 PM 4004 Connecting to remote registry.
                9/29/2017 12:57:10 PM 4004 Error 0x35. The network path was not found.
                9/29/2017 12:57:10 PM 4004 Move failed.
                • 0 over 8 years ago
                  However, I am able to ping by NetBIOS name on both sides (source and target)
                  • 0 over 8 years ago
                    Your log is telling me that "svc_mmad@olympus.mx.local. " can not connect to the remote registry.

                    There are two ways to execute a move task. The default is remotely (without the agent). Try the same task but uncheck the Remotely check box and see what the results are.

                    Additionally the %WinDir%\system32\debug\netsetup.log could shed additional light.
                    • 0 over 8 years ago
                      Here is the NetSetup log from client workstation. The last time it logged anything was on 09/25/17. Although I have been trying to move this computer every day since that day. This log same computer already exist in domain but I checked and it's not there.
                      ***************************************************
                      09/25/2017 13:33:00:960 NetpDoDomainJoin
                      09/25/2017 13:33:00:960 NetpMachineValidToJoin: 'OMS-MARTIC-01'
                      09/25/2017 13:33:00:960 OS Version: 6.1
                      09/25/2017 13:33:00:960 Build number: 7601 (7601.win7sp1_ldr.170810-1615)
                      09/25/2017 13:33:00:960 ServicePack: Service Pack 1
                      09/25/2017 13:33:00:976 SKU: Windows 7 Professional
                      09/25/2017 13:33:00:976 NetpDomainJoinLicensingCheck: ulLicenseValue=1, Status: 0x0
                      09/25/2017 13:33:00:976 NetpGetLsaPrimaryDomain: status: 0x0
                      09/25/2017 13:33:00:976 NetpMachineValidToJoin: the specified machine is already joined to 'OLYMPUS'!
                      09/25/2017 13:33:00:976 NetpMachineValidToJoin: status: 0xa83
                      09/25/2017 13:33:00:976 NetpJoinDomain
                      09/25/2017 13:33:00:976 Machine: OMS-MARTIC-01
                      09/25/2017 13:33:00:976 Domain: OAI\CVYHJ3G91V
                      09/25/2017 13:33:00:976 MachineAccountOU: OU=Windows 7,OU=OMS,OU=Workstations,DC=OAI,DC=OLYMPUSGLOBAL,DC=com
                      09/25/2017 13:33:00:976 Account: svc_mmad@oai.olympusglobal.com
                      09/25/2017 13:33:00:976 Options: 0x23
                      09/25/2017 13:33:00:976 NetpLoadParameters: loading registry parameters...
                      09/25/2017 13:33:00:976 NetpLoadParameters: DNSNameResolutionRequired not found, defaulting to '1' 0x2
                      09/25/2017 13:33:00:976 NetpLoadParameters: DomainCompatibilityMode not found, defaulting to '0' 0x2
                      09/25/2017 13:33:00:976 NetpLoadParameters: status: 0x2
                      09/25/2017 13:33:00:976 NetpValidateName: checking to see if 'OAI' is valid as type 3 name
                      09/25/2017 13:33:03:269 NetpCheckDomainNameIsValid for OAI returned 0x54b, last error is 0x3e5
                      09/25/2017 13:33:03:269 NetpCheckDomainNameIsValid [ Exists ] for 'OAI' returned 0x54b
                      09/25/2017 13:33:03:269 NetpJoinDomainOnDs: Domain name is invalid, NetpValidateName returned: 0x54b
                      09/25/2017 13:33:03:269 NetpJoinDomainOnDs: Function exits with status of: 0x54b
                      09/25/2017 13:33:03:269 NetpDoDomainJoin: status: 0x54b
                      09/25/2017 13:42:35:111 -----------------------------------------------------------------
                      09/25/2017 13:42:35:111 NetpDoDomainJoin
                      09/25/2017 13:42:35:111 NetpMachineValidToJoin: 'OMS-MARTIC-01'
                      09/25/2017 13:42:35:111 OS Version: 6.1
                      09/25/2017 13:42:35:111 Build number: 7601 (7601.win7sp1_ldr.170810-1615)
                      09/25/2017 13:42:35:111 ServicePack: Service Pack 1
                      09/25/2017 13:42:35:111 SKU: Windows 7 Professional
                      09/25/2017 13:42:35:111 NetpDomainJoinLicensingCheck: ulLicenseValue=1, Status: 0x0
                      09/25/2017 13:42:35:111 NetpGetLsaPrimaryDomain: status: 0x0
                      09/25/2017 13:42:35:111 NetpMachineValidToJoin: the specified machine is already joined to 'OLYMPUS'!
                      09/25/2017 13:42:35:111 NetpMachineValidToJoin: status: 0xa83
                      09/25/2017 13:42:35:111 NetpJoinDomain
                      09/25/2017 13:42:35:111 Machine: OMS-MARTIC-01
                      09/25/2017 13:42:35:111 Domain: OAI\CVYHJ3G91V
                      09/25/2017 13:42:35:111 MachineAccountOU: OU=Windows 7,OU=OMS,OU=Workstations,DC=OAI,DC=OLYMPUSGLOBAL,DC=com
                      09/25/2017 13:42:35:111 Account: svc_mmad@oai.olympusglobal.com
                      09/25/2017 13:42:35:111 Options: 0x23
                      09/25/2017 13:42:35:111 NetpLoadParameters: loading registry parameters...
                      09/25/2017 13:42:35:111 NetpLoadParameters: DNSNameResolutionRequired not found, defaulting to '1' 0x2
                      09/25/2017 13:42:35:111 NetpLoadParameters: DomainCompatibilityMode not found, defaulting to '0' 0x2
                      09/25/2017 13:42:35:111 NetpLoadParameters: status: 0x2
                      09/25/2017 13:42:35:111 NetpValidateName: checking to see if 'OAI' is valid as type 3 name
                      09/25/2017 13:42:37:419 NetpCheckDomainNameIsValid for OAI returned 0x54b, last error is 0x3e5
                      09/25/2017 13:42:37:419 NetpCheckDomainNameIsValid [ Exists ] for 'OAI' returned 0x54b
                      09/25/2017 13:42:37:419 NetpJoinDomainOnDs: Domain name is invalid, NetpValidateName returned: 0x54b
                      09/25/2017 13:42:37:419 NetpJoinDomainOnDs: Function exits with status of: 0x54b
                      09/25/2017 13:42:37:419 NetpDoDomainJoin: status: 0x54b