Converter unable to connect to network share

[fraber01]

Hi! I am trying to clone a physical machine to a Vmware Server machine (running under windows) and I keep have the message cannot connect to network share even if I change the credentials (connect as...)

However I can connect from both ends, on the machine hosting vmware converter and on the 'to be virtualized' host as well.

I enter the future name of the machine in the first box, then I enter:

10.x.x.x\d$ or
10.x.x.x\ShareName

also tried

VmwareServerName\d$ or
VmWareServer\ShareName

VmwareServer being in the DNS of course

Always the same problem... unable to connect to the network share

WHAT AM I DOING WRONG??

Converter is running on XP SP2 on my laptop

Vmware Server is running on a P4 running XP SP2 as well

Simple File Sharing is disabled everywhere

The To be Virtualized host is a XP SP1 Pentium4

plz help me understand this!

[esiebert7625]

Did you try mapping a drive instead and browsing to the drive letter when it asks you for the destination. Are you entering a directory on the destination share that does not exist.

Also make sure you can connect from the source computer to the destination computer and vice versa. Just because you can connect from the computer running converter to each server individually doesn't mean they can talk to each other. The source and destination servers need to talk to each other even though you are running converter remotely.

[pjaglowski · Accepted solution]

It may not be a share issue. I had the same error reported by the converter. I had to enter the connection credentials to the linux destination as domain\username. Simply entering in username "user" and a password did not work.

Try your user's workgroup instead of domain if you're domain-less, ie. "workgroup\user".

[Illuminata]

I was getting very frustrated over the same problem. We have a workgroup configuration and nothing worked until I specified the workgroup before the system name.

Thanks for posting the suggestion it worked!

[mzigman]

This worked for me. To clarify, here is what I needed to do:

1. My systems were domainless but they shared the same user name and password.

2. I had to use the Source workgroup name, which in my case was "WORKGROUP". I then used "workgroup\username" versus traditional "server\username" syntax.

3. I was able to proceed forward.

Also, the log on the source agent was clearly showing it could not connect to the target share. However, I could connect from the machine manually so I lost about an hour messing around on it. Thank goodness for Google!

[LeSaint]

Thanks, the solution worked just fine!

Great great great great!!!!!

[mkc_tcp32]

I have read this post but it has gone bad for me i did it once the second it did not work. I also tried domain/user but still is no working!

The share folder is in the same computer, why they did not do it for local and remote directory?

Is not working, I tried it in the explorer and it work fine, not like this in the converter software, also i power off the firewall, still no working, i tried with the domain/user machine/user, workgroup/user and nothing happen.

Also i run it as administrator nothing, i activate the administrator account and nothing.

Also i have reinstall the OS and the Converter five times and the same has happened need help!

As i said before it just did it once but i need to do a second time, i can reach the share folder throught explorer, but converter says it has incorrect user credentials! What i do not understand is why if i gave all permisions and also y did 01234 password, a easy password that is not a misstyping.

Even I tried with a remote source and nothing.

[mkc_tcp32]

Solved! The server i was trying to clone was in another network, my fault i did not read well!

Thanks to fraber01

[johnsmith1]

hi all,

been fighting with that issue here, without any luck cant convert to smb share

I mounted smb share as using credentials: WORKGROUP\user ; pass ... still the same error : FAILED: Insufficient permissions to access the source.

any clue? thanks

[jimkNC]

You cannot use drive maps.  It's very clear about that.  The CONVERTER client PROGRAM is ran under the username, which may or may not have this same drive mapped.  The JOB is ran as a service, which definitely does not have this drive mapped.