Unable to find server ?

[ANSA]

I'm trying to do a P2V.  All is well with the SOURCE configuration.

For the DESTINATION configuration, I am able to login to the destination host, etc.  After choosing the datastore I get a error message stating 'Unable to find server'.

I tried connecting to the Virtual Center and selected the host from there, but the samething happens.  See attached.

Any suggestions appreciated.

Message was edited by: bulletprooffool - Modified Screen Capture to small png file.

[continuum]

Please post images a jpg or png - asking users to download useless 4 Mb for fun is not necessary ..

Anyway - can't you simply store the VM locally instead of using the indirect way ?

You can add it to the datastore at any time later

___________________________________

description of vmx-parameters:

VMware-liveCD:

[pizzoja]

Did you ever find the solution to this.  I know it was a long time ago,  but I am currently having hte same issue?

Thanks

[continuum]

the original post is 3 years old - very likely your problem is completely different

we need details

what Converter version do you use ?
what OS do you want to import ?
what target do you want to import to ?

[pizzoja]

Sorry about that. 

I am trying to convert a physical system running windows 2000.  I am running VMware converter 3.0.3.  The target system is a 3.0.1 (i know they are out of date,  but I am trying to avoid upgrading as the ESX host will not be around much longer. 

My esx server has 3 potential datastores to choose,  2 san attached and 1 local. 

When going through the converter wizard,  everything seems to work until i get to the point where it asked me to select a datastore for the target location I get the same error listed early thread,  I have attached a screen shot of the error.

I cant think of any additional ports that might need to be open between my VIC\Converter software, Host ESX server, and Target system.  I have opened the following in preparation for the conversion.

from target systems to ESX host TCP 443 , 902, 903 and UDP 902

From ESX host to Target TCP 443 , 902, 903 and UDP 902

From VIC (only Converter software location) to Target systems TCP 445, 139, 9089, 9090 and UDP 137, 138

Any help would be greatly appreciated.

Thanks

Joel Pizzo

[Vas_Lazutin]

So, you don't  use vCenter, correct?

I would try cold P2V. Also try using IPs instead of server names.

[ANSA]

Manually add a static route for the source server's IP adderss to be able to reach the new Service console. The VMware Converter server must also be able to see both the source server and the target (ESX) server

[pizzoja]

Yes I have Vcenter,  and I tried using IP and System Names. My converter and my Vcenter are on the same system.

[continuum]

If everything else fails install 3.0.3 on the 2k machine itself - reboot the machine
and then store the result on a Windows network-share or additional disk.

Or - in case you want to do similar tasks more then once - create a good ColdcloneCD

[pizzoja]

I tried adding static routes from the target machine to both the ESX host and the Vcenter\Converter servers.  with the same result,  I know the vcenter and the ESX host can talk to each other as i have done P2V conversions in the past with these and they are in the same VLAN.

[pizzoja]

Thanks,  I will try this in my next outage window.  I will post the results next week.  Thanks for everyones quick response.

[Vas_Lazutin]

Try using the target ESX host directly as a destination (instead of vCenter). If it doesn't work try cold P2V.

I try never to use hot/live P2V - too many dependencies and potential problems.

[continuum]

> I try never to use hot/live P2V - too many dependencies and potential problems.

yep - I agree - but not everybody wants to build a ColdcloneCd himself or has access to a ready made one

[pizzoja]

I have always used hot,  and your right,  there are a lot of little issues that seem to come up.  I will build a coldclone cd.  if that works it might save me a lot of trouble later on.

Joel

[continuum]

in case you dont know how to do that - here is the building kit I maintain
http://communities.vmware.com/docs/DOC-14671