How can I troubleshoot a failed PC-to-Mac connection when trying to migrate the PC?

[rsaltus]

I followed the detailed instructions "Migrate an Existing Physical PC to a Virtual Machine," using an ethernet connection from PC lap to MacBook Pro.  Everything was fine until I tried so start migration: the Mac tells me it's connected to the PC.  I put in the 4-digit code and tried to start the migration; put in the user name and password, but the connection keeps failing.  I get a general system error - connection failed.  I've checked everything and retried several times, but no go.  Any idea what the problem is?

thanks a lot

Richard

[ColoradoMarmot]

If the windows OS came with the machine, you'll need to buy a windows license in order to legally virtualize it.  If that's the case, you'll always be better off building a VM from scratch from the original install disks - converting machines always results in buggy/bloated VM's.

If you really do need to/want to convert a machine and there aren't any license issues, try using the standalone VMWare Converter (free download) instead of the in-place migration tool.

[rsaltus]

Thanks. I can't tell if this connection problem is a license issue, though - how would I know?

I previously tried the standalone converter but I got messages saying there wasn't room on the Mac to transfer it. So someone in the Community suggested I try this migration method instead.

[Coach300]

I previously did such a thing and had no success with network connections when I created a VM out of a working Vista PC. My solution was to create a new VM with a fresh install of that OS (for which I did have an unused license). I populated the VM with only those applications actually needed and ported all of the doucments, photos, e-mails, etc. into the VM from the PC and that connected fine.

I found I couldn't network in either a PC (Win 8.1 running VMWare Player) nor a Mac (Fusion 6. on Mavericks) with the directly created VM, but the one I created from scratch worked just fine. I think that it was a better install, at that, as there was no bloatware on that VM, either.

I was never prompted to activate Windows on that VM...perhaps because it was Vista as old as it is. I cannot say if that would be encountered using Windows 7.

[ColoradoMarmot]

The connection problem is separate from the license.  Use the standalone vmware converter to solve it.

[rsaltus]

Thanks for that...gives me some ideas to try. So it appears that the instructions from the VMware document center rarely if ever actually work in practice. You have to find workarounds, which may be OS-dependent. That doesn't seem right. Also, on the VMware site I have been unable to find a way to contact someone in support this -none of the categories listed fit this problem. Can anyone suggest how I can talk to a support person there?

thanks

[rsaltus]

I will try standalone again, but when I tried it previously I got a message saying there wasn't enough room on the Mac.  Is there a way to select what Windows programs to transfer and ignore the rest, to make the trnsferred file smaller/?

[WoodyZ]

Do not try to save to the Mac via the Network!  Save the VM to an external HD and when finished connect the external HD to the Mac then copy it to the Mac!

[rsaltus]

sounds like a plan - will give it a try. thanks.

[rsaltus]

Is there any way to contact VMware support about this?  I can't find any info on their site.

[WoodyZ]

VMware Fusion (menu) > Help > Get Support