I have read your post here and I am having some trouble determining exactly the scenario that you are using to get this error.
Below are some suggestions to aid in achieving a successful hot clone conversion of problem source machines. Please let me know if any of these help in your situation.
\- Running converter over RDP is not recommended
\- Install converter locally on the machine, using the local "Administrator" account
\- Run converter as the local "Administrator" account
\- If selecting an ESX server as the destination, use the IP address of the target
\- If available, select local storage for the destination data store. If ESX is the preferred destination VM type, try converting to a Workstation/Server format and then importing it into ESX from the command line after the conversion.
\- Temporarily disable all anti virus and firewall software
\- Only convert the OS partition ( Typically the C: drive )
\- Do not resize any of the drives
\- Install VMware tools after the conversion has completed, rather than during the conversion process.
Here are some things to look at that may cause issues under certain configurations when converting:
\- Are there dynamic disks involved?
\- What is the version and SP level of the OS on the machine being converted?
\- Did you install converter from a network share?
\- If converting over the network and experiencing issues, would it be possible to attach through a different switch, use a crossover cable, use an externally attached hard drive ( USB ) ?
I'm having the same issue. I've tested the location name by entering it into "run" and it brings up the directory whether it's an ip or hostname. I've tried entering the "connect as" using just the name/pwd as well as
host\username / pwd.... no luck.
I'm thinking there is some windows setting or service on the dest pc that is blocking the connection but I can't determine what it is... if that is really the problem.
Anyways, someone else having heartburn on this same issue so any more ideas are appreciated.
Have you checked firewalls settings?
When filling out the "Connect as" dialogue, the wizard assumes that you are in a DOMAIN environment, which implies a PDC and authenticated users. If that isn't the case (you have a workgroup setup, for instance), use either the DNS name (your DNS server is visible from both machines) or the network share IP and a username in the Administrator group. In my case it looked like "192.168.0.34\admin" with the admin password in the "password" field. Of course, the folder you are pointing at must actually be shared on the network, and you must use the "
Been a while since I tried that but I'll try again. I was pretty sure that I did use IP addresses and an account that has admin privs on both PCs.
Thanks for the advice.
And for me, it's not a fw issue. MS not turned on and no other fw installed.