vSphere Client 5 U1 unable to connect to the host of U1 ESXi 4.1

Similar Questions

• "Unable to connect to the MKS: unable to connect to the host [servernamehere] failed on vSphere 4.0 and client.

  Anyone have this problem?  I loaded vSphere 4.0 host ESX 3.5 and everything seems to work very well yesterday, after sleep more testings and this error arose:

  "Unable to connect to the MKS: unable to connect to the host failed on vSphere 4.0 and client.

  After a google search, I could it is resolved by placing the DNS entries on the client machine c:\windows\system32\drivers\etc\hosts file point to my ESX host name and domain name FULL name runs and it worked fine.  I'm curious to know why this went well?

  What is MKS mean in this case?  Server key from Microsoft or the key management server?

  If you found this information useful, please consider awarding points to 'Correct' or 'useful '. Thank you!!!

  Kind regards

  Stefan Nguyen

  VMware vExpert 2009

  iGeek Systems Inc.

  VMware, Citrix, Microsoft Consultant

  When you click on the console of a virtual machine, the server that hosts the vm responds back with its host name for your client to connect to.  Thus, the MKS console could not be connected to, and you could not see the virtual machine console, until you updated name resolution.  Given that the ESX host is back with a name, the customer could not resolve the name, if your client could not connect to the virtual computer mouse, keyboard, screen.  Hope that makes more sense.

  -KjB

  VMware vExpert

• Error created another Console service, unable to connect to the host by vSphere vCenter

  After creating an another Service Console unable to connect to the host by vSphere vCenter. How can I remove the now Service Console or make the old one further work well?

  Thank you.

  George

  This KB will show you the steps to re-create the Service Console, but you'll need to console or ILO access to the ESX host.

  http://KB.VMware.com/kb/1000266

  If you have found this device or any other useful post please consider the use of buttons useful/correct to award points

  Twitter: http://twitter.com/mittim12

• Unable to connect to the host.   Error: The specified version is not found

  vmrun-t esx h https://192.168.1.123/SDK u root Pei password list

  Unable to connect to the host.

  Error: The specified version is not found

  Any ideas why it does not work?  It is run on a Windows XP workstation.  The target server is on the local network and running ESXi 4.1.  The vmRun version is 7.1.2 and is installed with Workstation 7.1.2.

  I also tried Ubuntu 10.04 with vmRun from a Workstation 7.1.2 installation.  There, he also fails with the same error.

  Note that ESXi 4.1 is used to test installation is not allowed and is running in demo mode.  Management of the vSphere client works without any problem the same Windows XP workstation.

  Any help would be appreciated.  Thank you.

  You must install the full package of VIX by http://communities.vmware.com/community/developer/downloads. It contains only components to manage the workstation. Please note that I had to install in the VIX 1.10.1 order then Workstation 7.1.2 to get both to work on my Windows 7 computer.

• vCenter Server displays the error message: unable to connect to the host

  vCenter Server displays the error message: unable to connect to the host

  Symptoms

  • vCenter Server cannot connect to a host when you perform operations such as:

  •

  o Storage vMotion

  o cold migration

  o cloning a virtual machine

  o the model deployment

  • Newspapers vpxd that contains an entry similar to:

  [2009-06-04 19:27:16.326 error "App" 4444] [VpxdInvtHost] IP address change for 10.223.122.143 to 10.223.127.197 unhandled, verification of the SSL certificate is not enabled.

  • You see errors similar to:

  Unable to connect to the host o

  o [2009-06-04 19:27:09.952 'Libs' 3902384 WARNING] [NFC ERROR] NfcNewAuthdConnectionEx: unable to connect to peer (numRetries = 2). Error: Unable to connect to the host 10.223.122.143: connection timed out

  • vCenter Server shows the VMS as being disconnected then connected.

  Hello

  Resolution

  Cause

  This problem can occur if an ESX host's IP address is changed while being managed by vCenter Server.

  Check the cause

  To check the cause of the problem:

  1. Log in as root to the ESX host using a SSH client.
  1. In the file etc/opt/vmware/vpxa/vpxa.cfg, find the IP address of the host. The entry looks like:

     
     10.21.48.121
     

     Note: for more information about editing the files, see installation in VMware ESX configuration files (1017022).

  Troubleshooting

  If the IP address is incorrect, perform the following steps in order. If the operation does not resolve the problem, continue to the next step. Don't skip a step.

  1. Disconnect and then reconnect the host:
  1. Right click on the ESX host in vCenter Server and click Disconnect.
  1. Reconnect the ESX host in vCenter Server.
  1. Restart the VirtualCenter agent on the ESX host:
  1. Stop the service of vpxa with the command:

     # service vmware-vpxa stop

  1. Open the /etc/opt/vmware/vpxa/vpxa.cfg file in a text editor and correct the IP address of the ESX host.
  1. Start the service of vpxa with the command:

     # service vmware-vpxa start

     Note: for VMware ESXi, you may have to restart all the management agents. For more information, see restart the agents on an ESX or ESXi Server (1003490) management .

  1. Rebuild the VirtualCenter agent on the ESX host configuration file:

     Attention: this step removes all the Statistics counters historical host and the virtual machine. If VMware ESX host is running in virtual machines that starts in a permitted CVS environment, you maybe won't be able to add the host without stopping the virtual machines first.

  1. Right click on the ESX host in vCenter Server and click Disconnect.
  1. Remove the ESX host disconnected from vCenter Server.
  1. Backup the file vpxa.cfg with the command:

     # mv /etc/opt/vmware/vpxa/vpxa.cfg /etc/opt/vmware/vpxa/vpxa.oldcfg

  1. Add the ESX host disconnected to the server vCenter inventory.
  1. Run the following command to view the contents of /etc/opt/vmware/vpxa/vpxa.cfg and confirm that the host IP address is correct:

     # cat /etc/opt/vmware/vpxa/vpxa.cfg

• ' Could not connect: unable to connect to the host localhost: connection refused "on variuos orders

  On ESX 4.0.0 Update 1.

  When I run a command like "vim-cmd/hostsvc/hostsummary | "grep inMaintenanceMode" or vimsh - n - e/hostsvc/maintenance_mode_enter ' / 'vimsh - n - e
  "/ hostsvc/maintenance_mode_exit" all returned the same error message ' could not connect: unable to connect to the host localhost: connection refused.

  I checked the checked the file /etc/resolv.conf Bed & Breakfast.

  I am able to ssh on the server as well as the use of WinSCP without any problem.

  I can connect with the VI Client also without problem.

  Any ideas?

  The problem has been resolved.

  The fix:

  =====

  # vimsh-e - n/hostsvc/hostsummary | grep inMaintenanceMode

  Using the libcrypto, version 90809F

  inMaintenanceMode = false,

  # vim-cmd/hostsvc/hostsummary | grep inMaintenanceMode

  inMaintenanceMode = false,

  Rationality for the problem is these commands (vim - FCM or vimsh) were unable to communicate due to lack of xinetd process.

  # ps - ef | grep-i xinet

  root 11527 25978 0 04:30 pts/0 00:00:00 grep-i xinet

  # service xinetd restart

  #

  # Service xinetd status

  #

  # service xinetd start

  # Service xinetd status

  # /etc/init.d/xinetd ls

  /etc/init.d/xinetd

  / * But NETWORK seems to be normal on the server * /.

  # cat /etc/resolv.conf

  nameserver 172.26.6.21

  nameserver 172.25.6.51

  # ifconfig

  Lo encap:Local Loopback link

  INET addr:127.0.0.1 mask: 255.0.0.0

  RACE of LOOPING 16436 Metric: 1

  Dropped packets: 6053620 RX errors: 0:0 overruns: 0 frame: 0

  Dropped packets: 6053620 TX errors: 0:0 overruns: 0 carrier: 0

  collisions: 0 txqueuelen:0

  RX bytes: 2021352939 (1.8 GiB) TX bytes: 2021352939 (1.8 GiB)

  ppp0 link encap:Point - to-Point Protocol

  INET-addr:164.152.87.72 P - t - P:164.152.87.64 mask: 255.255.255.255

  Up POINTOPOINT RUNNING NOARP MULTICAST metric MTU:1500: 1

  Fall of RX packets: 208 errors: 2:0 overruns: 0 frame: 0

  Dropped packets TX: 205 errors: 0:0 overruns: 0 carrier: 0

  collisions: 0 txqueuelen:3

  RX bytes: 18165 (17.7 KiB) TX bytes: 22314 (21.7 KiB)

  vmnic100200 Link encap HWaddr 00: 1B: 21:6 A: C9:C4

  RUNNING BROADCAST MULTICAST MTU:1500 metric: 1

  Dropped packets: 1383869 RX errors: 0:0 overruns: 0 frame: 0

  Dropped packets: 1382815 TX errors: 0:0 overruns: 0 carrier: 0

  collisions: 0 txqueuelen:1000

  RX bytes: 90351869 (86.1 MiB) TX bytes: 92106912 (87.8 MiB)

  Interruption: 97

  vmnic100201 Link encap HWaddr 00: 1B: 21:6 A: C9:C5

  RUNNING BROADCAST MULTICAST MTU:1500 metric: 1

  Dropped packets: 24239456 RX errors: 0:0 overruns: 0 frame: 0

  Dropped packets: 23905751 TX errors: 0:0 overruns: 0 carrier: 0

  collisions: 0 txqueuelen:1000

  RX bytes: 2078777971 (1.9 GiB) TX bytes: 2226266024 (2.0 GiB)

  Interruption: 113

  vmnic100600 Link encap HWaddr 00:25:5 C: 2: 75:30

  RUNNING BROADCAST MULTICAST MTU:1500 metric: 1

  Dropped packets: 13076343 RX errors: 0:0 overruns: 0 frame: 0

  Dropped packets: 5226061 TX errors: 0:0 overruns: 0 carrier: 0

  collisions: 0 txqueuelen:1000

  RX bytes: 1292112365 (1.2 GiB) TX bytes: 1224021381 (1.1 GiB)

  Interruption: 129

  vmnic100601 Link encap HWaddr 00:25:5 C: 2: 75:31

  RUNNING BROADCAST MULTICAST MTU:1500 metric: 1

  Dropped packets: 819469 RX errors: 0:0 overruns: 0 frame: 0

  Dropped packets: 770101 TX errors: 0:0 overruns: 0 carrier: 0

  collisions: 0 txqueuelen:1000

  RX bytes: 56287946 (53.6 MiB) TX bytes: 52499576 (50.0 MiB)

  Interruption: 137

  vmnic110200 Link encap HWaddr 00: 1B: 21:6 A: CA:44

  RUNNING BROADCAST MULTICAST MTU:1500 metric: 1

  Dropped packets: 1774795 RX errors: 0:0 overruns: 0 frame: 0

  Dropped packets: 1681079 TX errors: 0:0 overruns: 0 carrier: 0

  collisions: 0 txqueuelen:1000

  RX bytes: 142435399 (135.8 MiB) TX bytes: 135079293 (128.8 MiB)

  Interruption: 145

  vmnic110201 Link encap HWaddr 00: 1B: 21:6 A: CA:45

  RUNNING BROADCAST MULTICAST MTU:1500 metric: 1

  Dropped packets: 21079616 RX errors: 0:0 overruns: 0 frame: 0

  Dropped packets: 20688606 TX errors: 0:0 overruns: 0 carrier: 0

  collisions: 0 txqueuelen:1000

  RX bytes: 1859632344 (1.7 GiB) TX bytes: 1852761835 (1.7 GiB)

  Interruption: 161

  vmnic110600 Link encap HWaddr 00:25:5 C: 2: 75:32

  RUNNING BROADCAST MULTICAST MTU:1500 metric: 1

  Dropped packets: 39205375 RX errors: 0:0 overruns: 0 frame: 0

  Dropped packets: 21339531 TX errors: 0:0 overruns: 0 carrier: 0

  collisions: 0 txqueuelen:1000

  RX bytes: 32420064542 (30.1 GiB) TX bytes: 3709579479 (3.4 GiB)

  Interruption: 177

  vmnic110601 Link encap HWaddr 00:25:5 C: 2: 75:33

  RUNNING BROADCAST MULTICAST MTU:1500 metric: 1

  Dropped packets: 2922150 RX errors: 0:0 overruns: 0 frame: 0

  Dropped packets: 2110634 TX errors: 0:0 overruns: 0 carrier: 0

  collisions: 0 txqueuelen:1000

  RX bytes: 398811808 (380.3 MiB) TX bytes: 245899848 (234.5 MiB)

  Interruption: 185

  vswif0 Link encap HWaddr 00:50:56:41:76:EB

  INET addr:172.26.6.13 Bcast:172.26.6.255 mask: 255.255.255.0

  RUNNING BROADCAST MULTICAST MTU:1500 metric: 1

  Dropped packets: 109779 RX errors: 0:0 overruns: 0 frame: 0

  Dropped packets: 23715 TX errors: 0:0 overruns: 0 carrier: 0

  collisions: 0 txqueuelen:1000

  RX bytes: 10137604 (9,6 MiB) TX bytes: 21716347 (20.7 MiB)

  vswif1 Link encap HWaddr 00:50:56:40:30:F7

  INET addr:172.26.7.11 Bcast:172.26.7.255 mask: 255.255.255.0

  RUNNING BROADCAST MULTICAST MTU:1500 metric: 1

  Fall of RX packets: 36515 errors: 0:0 overruns: 0 frame: 0

  Dropped TX packets: 4 errors: 0:0 overruns: 0 carrier: 0

  collisions: 0 txqueuelen:1000

  RX bytes: 3702390 (3,5 Mio) TX bytes: 168 (168,0 b)

  vswif2 Link encap HWaddr 00:50:56:4 A: DF:1 B

  INET addr:172.26.8.11 Bcast:172.26.8.255 mask: 255.255.255.0

  RUNNING BROADCAST MULTICAST MTU:1500 metric: 1

  Fall of RX packets: 20525 errors: 0:0 overruns: 0 frame: 0

  Dropped packets TX: 6 errors: 0:0 overruns: 0 carrier: 0

  collisions: 0 txqueuelen:1000

  RX bytes: 2742990 (2.6 MiB) TX bytes: 252 (252.0 b)

  vswif3 Link encap HWaddr 00:50:56:4E:1E:24

  INET addr:172.26.9.12 Bcast:172.26.9.255 mask: 255.255.255.0

  RUNNING BROADCAST MULTICAST MTU:1500 metric: 1

  Fall of RX packets: 26408 errors: 0:0 overruns: 0 frame: 0

  Dropped TX packets: 4 errors: 0:0 overruns: 0 carrier: 0

  collisions: 0 txqueuelen:1000

  RX bytes: 3095970 (2.9 MiB) TX bytes: 168 (168,0 b)

  # / opt/ft/bin/ftsmaint lsVnd

  Virtual network device (VND) groups

  ===================================

  Status of group name

  --------------------------

  vSwitch0 ONLINE

  vSwitch1 ONLINE

  vSwitch2 ONLINE

  vSwitch3 ONLINE

  Members of the Group of VND

  =================

  Link Group Name status Interface link state speed

  --------------------------------------------------------------------------

  vmnic100200 vSwitch2 DUPLEX UP LINK 1000 Mb/s-FD

  vmnic100201 vSwitch3 DUPLEX UP LINK 1000 Mb/s-FD

  vmnic100600 vSwitch0 DUPLEX UP LINK 1000 Mb/s-FD

  vmnic100601 vSwitch1 DUPLEX UP LINK 1000 Mb/s-FD

  vmnic110200 vSwitch2 DUPLEX UP LINK 1000 Mb/s-FD

  vmnic110201 vSwitch3 DUPLEX UP LINK 1000 Mb/s-FD

  vmnic110600 vSwitch0 DUPLEX UP LINK 1000 Mb/s-FD

  vmnic110601 vSwitch1 DUPLEX UP LINK

  1000 mb/s-FD

  / * Further consideration on the problem of starting XINETD * /.

  Further examination shows that the xinetd is unable to start because he believed NETWORK unavailable.

  Starting xinetd uses the contents of the sysconfig file where there was an entry incorrect "NETWORKINcesv = yes". We have corrected this entry and restarted xinetd process.

  After this correction, xinetd is restarted, the system seems to be normal.

  # cat sysconfig

  NETWORKINcesv = yes

  HOSTNAME = Server.test .net

  GATEWAY = 172.26.6.1

  IPV6_AUTOCONF = no

  NETWORKING_IPV6 = no

  #

  # cat sysconfig

  Networking = yes

  HOSTNAME = Server.test .net

  GATEWAY = 172.26.6.1

  IPV6_AUTOCONF = no

  NETWORKING_IPV6 = no

  # ps - ef | grep-i xinet

  root 27977 25978 0 04:41 pts/0 00:00:00 grep-i xinet

  # service xinetd start

  [From xinetd: OK]

  # ps - ef | grep-i xinet

  root 28119 1 0 04:41?        00:00:00 xinetd - stayalive - pidfile /var/run/xinetd.pid

  root 28239 25978 0 04:42 pts/0 00:00:00 grep-i xinet

  #

  # service xinetd restart

  [Judgment of xinetd: OK]

  [From xinetd: OK]

  # vim-cmd/hostsvc/hostsummary | grep inMaintenanceMode

  inMaintenanceMode = false,

  # vimsh-e - n/hostsvc/hostsummary | grep inMaintenanceMode

  Using the libcrypto, version 90809F

  inMaintenanceMode = false,

  #

• Error code: 800ccc0e and the message "Unable to connect to the host server", when you set up Windows Mail to receive discussion group messages.

  I recently signed up for Windows Mail, Windows Vista Help. I have configured my Gmail OK account, but when I click TOOLS then Newsgroups I get the following error: unable to connect to the host server. When I click on show details, he said: Microsoft Community Server: msnews.microsoft.com Protocol: NNTP Port: 119 secure (SSL): 0 Code: 800ccc0e

  msnews. Microsoft.com has not existed for about three years now. MS close their news servers. You can still access newsgroups, but you will have to do with one another as eternal September or AIOE news server.
   
   

• migrate storage fails with 'unable to connect to the host.

  I'm trying to migrate storage of a virtual machine to a different data store. (on the same san)

  When I start work, I see the task:

  Moving the virtual machine / status 'in process '.

  After 10 minutes, I get 2 pop-up windows:

  -

  ---

  Error

  -

  ---

  Unable to connect to the host.

  -

  ---

  Ok

  -

  ---

  I tried to move the storage of another virtual machine, but I got the same error.

  Also tried a different vmhost (but same cluster), but also the same error.

  When you try to a host in a different cluster, it works without problem (same san/store data used in the cluster where I got the errors)

  There is no difference in the profile of security on the host computers.

  Any tips?

  Logfile attached (vpxd - 353.log) when I was running the migrate storage.

  Part of the error:

  2009-11-03 16:49:07.035 02464 info "App" (1257263347020035) VMotion began

  2009-11-03 16:58:35.903 02464 error "App" (1257263347020035) VMotion failed: vim.fault.HostConnectFault

  When it works ok:

  2009-11-03 17:29:49.470 02456 info "App" (1257265789470153) VMotion began

  Hello.

  See KB 1010837.

  Good luck!

• Unable to connect to the host server: a connection attempt failed because

  Hi all

  I install my host ESX server in vmware workstation.  It works fine except when I am creating virtual machines.

  I'm not able to install the operating system on the virtual machine and I get this error that appears inside the virtual machine.

  Unable to connect to the host server: a connection attempt failed because the connected party did not respond after a certain time, or established connection failed because connected host has no

  to answer.  Do you want to retry?

  My ESX server hosts have static IP addresses.

  I've seen a few similar posts on this issue, but their solutions have not worked for me.

  Best regards

  Nathan

  I think we confuse you.  ESX server is running like a machine virtual within the workstation, correct?  If Yes, then you must edit the vmx esx server with these entries monitor configuration file *.  They can go anywhere in the file.  Once those have been added, you should be able to run 32-bit virtual machines within the esx server.

  -KjB

  VMware vExpert

• Unable to connect to the host PuTTY using!

  Hello people.

  I try to use puTTY to connect to the host, but I can't. Message says - Network error: Connection refused. Any help.

  Thank you.

  In terms of virtualization, there is no real difference but how you interact with directly it is - the console, usually called the Service Console is part of ESX. It is essentially a virtual machine running RHEL which is used to manage and control your ESX Server.  Being based on linux is to SSH ocnnections research and this is what you connect to use a like of the PuTTY SSH client. In ESXi management and control functionality is part of the vmkernel which is the o/s of the ESXi server. It is no longer use RHEL so there is no capability of SSH connection so PuTTY will not work.  VMware has replaced the Service Console with remote CLI - which gives you the functionality of the Service Console.

  If you find this or any other answer useful please consider awarding points marking the answer correct or useful

• Unable to connect to the host to download files... help please...

  New user here, any help would be appreciated...

  I do my hosting via godaddy, just got dreamweaver and am in love, but have hit a snag.

  For a long time, I was connecting godaddy and download of updates via ftp every time.  My friend said that I could do with a simple click, but I'm having problems.  When I try to connect to the remote host I get "error FTP-only can not connect to the host.  The remote host cannot be found. »

  I have attached a pictur of my arrangement... what Miss me?

  

  Hello

  Looking at your screen you typed the wrong ftp address, you do not need the ftp: / /

  See - http://help.adobe.com/en_US/Dreamweaver/10.0_Using/WSBE25912D-A9DE-4ba1-9F85-4C692F5C14ADa .html.

  PZ

• Windows XP SP3 with view Client 5.1: unable to connect: discovers the connection connection to the server has failed

  Hi guys,.

  I need help.  I have a problem with my opinion of Client on a Windows XP SP3 computer.  When I click on connect, I get the following message immediately:

  "Failed to connect to the view connection server. Verify that the server connection mode address and network settings are correct. »

  A few details:

  My client's IP address is on the same subnet as the view connection server

  There is no firewall and DNS solves the login server see very well.  Here is the output of my customer's orders

  C:\ > nslookup X.X.X.172

  < resolves very well >

  C:\ > nslookup dd - view.viewdomain.com

  < resolves very well >

  C:\ > nslookup dd-notice

  < resolves very well >

  C:\ > tracert X.X.X.172

  < works great >

  If I open a browser on the XP workstation which is a failure, I can go to https://dd-view.viewdomain.com.  It displays the page that I need to connect with View Client. What do I think, so this should check the connectivity between the two.

  I've seen customer 5.1.0 build-704644 installed on my Windows XP SP3 client computer

  My connection to the server is running 5.1.1 build-799444 and is configured with a pool of offices 25 clone related with SSL active

  LAST IMPORTANT NOTE: I have the same version of the Client view (5.1.0 build-704644) installed on another Windows 7 workstation on the same subnet and it connects to my view connection server office pool very well.

  I tried to install the three versions of the customer view of this system of XP SP3 including the latest version, when the connection after installation, they all fail the same way. My body needs to function. The client machines can not move to something more recent to Windows XP SP3 because I am not the administrator for them.

  Any ideas?  Is this a bug or is Windows XP SP3 just not supported with view 5.1?

  VR,

  Brian Whyte

  Political of McAffee HBSS blocked 443 attempts out of the customer to view.

  The difference is that the Windows 7 machine that worked was becoming another policy HBSS applied to what was not blocking attempts.

• 5.5 'unable to connect to the host.

  Good evening

  We have installed 5.5 and re-imported our config 5.1 prior. When you try to connect to the VCO client, the message "Unable to connect to host" is returned. This occurs independently by using the IP address or the FULL domain name.

  Authentication is set to LDAP and we tested the connection using the test connection tab, the account works fine and all green elements in the configuration page. Both services are running. Don't see anything obvious in the newspapers either.

  Enjoyed any idea on what it remains to be seen. Thank you.

  I was able to get around that and connect as follows:

  -Remove the VCO 5.5 and make sure that all related files have been deleted

  -Re-install VCO 5.5

  -Change the values in the configuration by copy and paste in the new Mail LDAP server, database, another Server 5.1 using similar settings

  -Other values manually place VC, certificates

  Previously, I had done the installation and re-import the config saved version 5.1 prior. I don't know where the issue is it than that, but it does not work.

• Manager of Multi - Hypervisor, VMWare - unable to connect to the host

  
  I installed a Multi-hypervisor-VMWare in a test running vCentre 5.5 environment. However, when I try to add Microsoft Hyper-V, it says "Unable to connect to Host."

  WinRM are enabled on the Hyper-V host computer. Also, I tried to manually add its IP address on the TrustedHosts in Winrm. Still no go. Can someone please provide some guidance.

  Hello

  Hyper-V R2 2012 is not supported by the hypervisor Manager Multi, so your problem with the addition of the host.

  You can refer to the Release Notes for more information.

  HTH,

• Unable to connect to the host.

  I installed vCenter 4.1. vCO is also installed. I have configured the vCO with success but some vCO clients cannot connect to the server of vCO.

  (1) customer vCO on the vCO server can connect to the server of vCO and I can connect.

  (2) customer of vCO on the same machine on the subnet can connect to the server of vCO and I can connect.

  (3) customers of vCO on the machine of the other subnet cannot connect to the server of vCO.

  (4) customers of vCO on the remote site can not connect to the server of vCO.

  Is it possible to connect from any computer?

  The vCO is with vCenter server. I can connect to the server vCenter of all machines. Remote Desktop can connect to the server of all machines.

  The server and the clients have no firewall.

  I published telnet to the vCO ports of the server in the remote site, and all the ports of the vCO Server worked.

  Great!