I search this morning, but I didn't found any app that where using 443 port (netstat -a tells nothing).. I'm not an expert in network, so what can I check to be sure that's not a 443 port problem ?

thx

here're the vmware logs:

Section for VMware vCenter Converter Standalone, pid=3116, version=4.0.1, build=build-161434, option=Release
--2009-11-09 11:17:36.183 03120 info 'App'-- Current working directory: C:\Program Files\VMware\VMware vCenter Converter Standalone
--2009-11-09 11:17:36.183 03120 info 'Libs'-- HOSTINFO: Seeing Intel CPU, numCoresPerCPU 1 numThreadsPerCore 2.
--2009-11-09 11:17:36.183 03120 info 'Libs'-- HOSTINFO: numPhysCPUs is 0, bumping to 1.
--2009-11-09 11:17:36.183 03120 info 'Libs'-- HOSTINFO: numCores is 0, bumping to 1.
--2009-11-09 11:17:36.183 03120 info 'Libs'-- HOSTINFO: This machine has 1 physical CPUS, 1 total cores, and 1 logical CPUs.
--2009-11-09 11:17:36.183 03120 verbose 'ThreadPool'-- TaskMax=10, IoMin=1, IoMax=21
--2009-11-09 11:17:36.183 03120 info 'Libs'-- Using system libcrypto, version 9070AF
--2009-11-09 11:17:41.964 03120 info 'App'-- Vmacore::InitSSL: doVersionCheck = true, handshakeTimeoutUs = 120000000
--2009-11-09 11:18:06.630 03120 error 'App'-- LoginWin32: StartServiceWithProgress() returned 1067

---

and the netstat -an:

Proto Adresse locale Adresse distante État
TCP 0.0.0.0:135 0.0.0.0:0 LISTENING
TCP 0.0.0.0:445 0.0.0.0:0 LISTENING
TCP 0.0.0.0:1947 0.0.0.0:0 LISTENING
TCP 0.0.0.0:3389 0.0.0.0:0 LISTENING
TCP 0.0.0.0:5357 0.0.0.0:0 LISTENING
TCP 0.0.0.0:9089 0.0.0.0:0 LISTENING
TCP 0.0.0.0:49152 0.0.0.0:0 LISTENING
TCP 0.0.0.0:49153 0.0.0.0:0 LISTENING
TCP 0.0.0.0:49154 0.0.0.0:0 LISTENING
TCP 0.0.0.0:49155 0.0.0.0:0 LISTENING
TCP 0.0.0.0:49163 0.0.0.0:0 LISTENING
TCP 172.30.8.184:139 0.0.0.0:0 LISTENING
TCP 172.30.8.184:49181 195.167.195.51:80 ESTABLISHED
TCP 172.30.8.184:49183 172.30.1.209:135 TIME_WAIT
TCP 172.30.8.184:49184 172.30.1.209:1026 TIME_WAIT
TCP :::135 :: LISTENING
TCP :::445 :: LISTENING
TCP :::1947 :: LISTENING
TCP :::3389 :: LISTENING
TCP :::5357 :: LISTENING
TCP :::9089 :: LISTENING
TCP :::49152 :: LISTENING
TCP :::49153 :: LISTENING
TCP :::49154 :: LISTENING
TCP :::49155 :: LISTENING
TCP :::49163 :: LISTENING
TCP fe80::7c99:d04b:7c5d:873f%11:3389 fe80::ac7a:ec79:4873:c230%11:55199 ESTABLISHED
TCP fe80::7c99:d04b:7c5d:873f%11:49182 fe80::ac7a:ec79:4873:c230%11:445 ESTABLISHED
UDP 0.0.0.0:123 :
UDP 0.0.0.0:500 :
UDP 0.0.0.0:1947 :
UDP 0.0.0.0:3702 :
UDP 0.0.0.0:3702 :
UDP 0.0.0.0:4500 :
UDP 0.0.0.0:5355 :
UDP 0.0.0.0:56011 :
UDP 0.0.0.0:65376 :
UDP 127.0.0.1:51875 :
UDP 127.0.0.1:58212 :
UDP 127.0.0.1:62958 :
UDP 172.30.8.184:137 :
UDP 172.30.8.184:138 :
UDP :::123 :
UDP :::500 :
UDP :::1947 :
UDP :::3702 :
UDP :::3702 :
UDP :::4500 :
UDP :::5355 :
UDP :::65377 :

sorry for the formatting, I didn't found the "text mode" in the forum, and thanks for your help

you're right, I've alredy done that after my battle against the server under seven : I installed the converter server in a VM, and I use it with the converter client on my seven x64, and it's works fine. But if the server is not working on seven, isn't it a bug, and musn't I report it to vmware developpers ?

Maybe here isn't the right place, duno ??

No new no, I've asked vmware support for that problem during another incident on the converter, but they didn't answer me, I think we must wait the next version, now seven is out, so they must add official support of it in theirs softwares.

The correct answer for now is the one of continuum, put the converter server in a VM, it's working great.

I thought some developpers or support team of vmware would have a look sometimes in the communities, but apparently not..