Remote P2V of Windows NT Machine

[glenikins]

Hi there,

I am trying to virtualise an old Windows NT (SP6a - 4.00.1381) physical machine, using version 3.0.3 of the VMware converter package (the latest version that still supports what I am trying to do).  I am running the converter package on a Windows 7 Enterprise machine on the same network.  I run the Convert Machine wizard and get as far as the Source Logon window at which point I enter the IP address of the remote NT machine, and local administrator account (".\administrator") and the password.  On clicking Next, I get the following error message:

"Unable to connect to the remote VMware Converter Agent.  The remote host is not accessible using Microsoft Network Services.  It might be down or firewalled."

There is no firewall on the remote machine, my local machine, or on the network.

I know that the remote logon itself is working as I get a "wrong password" message if I enter the wrong password.

I have now installed the converter agent directly onto the remote machine, but on trying again I get exactly the same message.

I would be grateful for any help or advice on how to proceed from here.

[Borja_Mari]

Hello,

check this, maybe it's helpful:

Unable to connect to the remote VMWare Converter Agent error message

Best regards,

Pablo

[glenikins]

Hi Pablo,

Thanks for the info - it's similar to what I'm seeing.  The error code I get for the failure to connect to IPC$ is 53 - as per the log file excerpt below.  I've not been able to find out what 53 refers to though.

[2014-04-22 13:41:19.691 'P2V' 5848 verbose] [task,339] Transition from None to InProgress requested
[2014-04-22 13:41:19.691 'P2V' 5848 verbose] [task,388] Transition succeeded
[2014-04-22 13:41:19.691 'P2V' 5848 info] [task,274] Starting execution of a Task
[2014-04-22 13:41:19.691 'P2V' 5848 info] [clientConnection,101] Connecting to IPC$ on 158.21.227.30 as .\administrator
[2014-04-22 13:41:23.497 'P2V' 5848 info] [,0] SMB manager: Error connecting to share [\\158.21.227.30\IPC$]: 53

[2014-04-22 13:41:23.497 'P2V' 5848 warning] [clientConnection,115] Failed to connect to IPC$ on 158.21.227.30. Reason: Unspecified error in remote execution mechanism
[2014-04-22 13:41:23.497 'P2V' 5848 info] [clientConnection,119] Giving up trying to connect to IPC$ on 158.21.227.30
[2014-04-22 13:41:23.497 'P2V' 5848 error] [task,295] Task failed: P2VError REMOTE_UFA_FIREWALLED(158.21.227.30)
[2014-04-22 13:41:23.497 'P2V' 5848 verbose] [task,339] Transition from InProgress to Failure requested
[2014-04-22 13:41:23.497 'P2V' 5848 verbose] [task,388] Transition succeeded

[WoodyZ]

How much free space do you have on the Windows NT HDD, is it enough to contain a copy of itself or can you add a second HDD to it?  The reason I ask is I've imaged an NT4 system onto itself, created the VM under C:\VM and then copied the VM to another system.  I've also imaged an NT4 system onto a second drive in the system and then copied the VM to another system.  I've done this a number of different ways, booting the NT4 system after the VM was created with a Linux Live CD and copying it over the network to another system.  I've added the HDD containing the VM to an external enclosure (USB/FireWire/Thunderbolt) connecting it to the other system and copying the VM.

Yes going directly to the target from the source via Network might be nicer, depends, however if you're having connectivity issues via the Converter software then an alternate method should be considered!

[Borja_Mari]

Hello,

one option is to install locally the vmware converter in the NT, and then try to P2V it.

Check if you're be able to connect to the IPC$ of the NT from the Windows 7 machine (i would check what it's blocking the connectivity, maybe a firewall?):

IPC$ Authenication to Windows NT Servers :: Network :: Admin Tips :: Windows NT :: Windows Server 2...

The "File and Printer Sharing for Microsoft Networks" is activated in the NT network interfaces?

I would check this vmware's kb, maybe it is helpful:

VMware KB: Best practices for using and troubleshooting VMware Converter

VMware KB: Required VMware vCenter Converter 4.x/5.x ports

Best regards,

Pablo