Hello Everyone,

I was wondering if someone might have run into an issue with Mozilla Firefox on AppStack not working. What is happening is that after I created an appstack with Firefox on it everything seem to work great for a day or two  however then all of the sudden it won't launch at all. It happens to multiple users including myself. I'm using UEM to capture user information using the UEM template available here on VMware site. Besides that there are no other alterations to the program. If I install Firefox on master image it works flawlessly but I don't really want that on my image. The Firefox versions I tried is regular Firefox 62 and Firefox 60.2 ESR. The OS I'm on is Windows 10 1607 LTSB . THere not a single Event in the event viewer that could point to what is happening here.

Any help would be much appreciated

Hi everyone,

Ok, i have this new installed ESXi 6.7.0 Update 1 on a Dell Server with 16GB of RAM, 2 physical processors and 1T of physical storage capacity. I have licensed with a free key and i know i cant use vCenter with it, also i dont want to. I just connect directly and use the default embedded HTML5 client, ok? The problem is that at first when installed i could (playing with the system) create and delete datastorages normally but the next day it just throw this error and wont let me delete datastores anymore. I notice also that when creating a 500GB VMFS6 datastore, it wont let me create a second one. The datastore creation wizard just tell me i dont have free space when i have 1T available. Why is that happening to me? Please see attached pic to see deletion error. Thanks guys!

Hello All

I'm moving from vCenter 6.5 Update 1g with external PSC  >>  6.7 Update 1 and converging the PSC into vCenter.

Steps I've followed:

1.  Upgrade PSC 6.5u1g  >>  PSC 6.7u1   [success]

2.  Upgrade vCenter (Appliance) 6.5u1g  >>  vCenter (Appliance) 6.7u1   [success]

3.  Converge PSC to vCenter: vcsa-util.exe converge --log-dir d:\logs --verbose --no-ssl-certificate-verification --backup-taken converge.json   [success]

4.  Decommission External PSC:  vcsa-util.exe decommission --log-dir d:\logs --verbose --no-ssl-certificate-verification decommission_psc.json   [FAIL]

I've tested both converge.json and decommission_psc.json in our DEV environment and the decom went through with no errors.  The pre-prod decommission got a long way through the process including shutting down the PSC.  If you log into the vCenter Administration / System Configuration, you can see only the vCenter with embedded PSC.

As this is fairly new, I can't find much PSC decom failures on Google / VM community.

IS THIS ANYTHING TO WORRY ABOUT - DO I NEED TO RE-RUN  THE DECOM???

This is the output from the logs showing the failure:

2019-01-10 14:14:53,021 - vCSACliConvergeLogger - DEBUG - Powering off PSC machine...

2019-01-10 14:14:55,038 - vCSACliConvergeLogger - INFO - PSC machine powered off successfully.

2019-01-10 14:14:55,039 - vCSACliConvergeLogger - DEBUG - Proceed with certificate thumbprint check...

2019-01-10 14:14:55,937 - vCSACliConvergeLogger - INFO - Decommissioning PSC node. This may take some time. Please wait..

2019-01-10 14:14:55,938 - vCSACliConvergeLogger - DEBUG - Running command on vm vcenter: /bin/bash --login -c '/usr/bin/cmsso-util unregister --node-pnid psc.domain --username administrator@vsphere.local --passwd *** --debug'

2019-01-10 14:22:47,614 - vCSACliConvergeLogger - ERROR - DecommissionTask: Caught exception Traceback (most recent call last):

  File "d:\build\ob\bora-9914372\bora\install\vcsa-installer\vcsaConvergeCli\cli_tasks\decommission\decommission_task.py", line 123, in execute

  File "d:\build\ob\bora-9914372\bora\install\vcsa-installer\vcsaConvergeCli\utils\esxvim.py", line 407, in run_command_wait

  File "d:\build\ob\bora-9914372\bora\install\vcsa-installer\vcsaConvergeCli\utils\esxvim.py", line 432, in CheckProcesses

  File "d:\build\ob\bora-9914372\bora\install\vcsa-installer\vcsaConvergeCli\deps\pyVmomi\pyVmomi\VmomiSupport.py", line 557, in <lambda>

  File "d:\build\ob\bora-9914372\bora\install\vcsa-installer\vcsaConvergeCli\deps\pyVmomi\pyVmomi\VmomiSupport.py", line 363, in _InvokeMethod

  File "d:\build\ob\bora-9914372\bora\install\vcsa-installer\vcsaConvergeCli\deps\pyVmomi\pyVmomi\SoapAdapter.py", line 1346, in InvokeMethod

pyVmomi.VmomiSupport.vmodl.fault.SystemError: (vmodl.fault.SystemError) {

   dynamicType = <unset>,

   dynamicProperty = (vmodl.DynamicProperty) [],

   msg = 'A general system error occurred: vix error codes = (3016, 0).\n',

   faultCause = <unset>,

   faultMessage = (vmodl.LocalizableMessage) [],

   reason = 'vix error codes = (3016, 0).\n'

}

2019-01-10 14:22:47,622 - vCSACliConvergeLogger - INFO - ================ [FAILED] Task: DecommissionTask: Running DecommissionTask execution failed at 14:22:47 ================

2019-01-10 14:22:47,623 - vCSACliConvergeLogger - DEBUG - Task 'DecommissionTask: Running DecommissionTask' execution failed because [(vmodl.fault.SystemError) {

   dynamicType = <unset>,

   dynamicProperty = (vmodl.DynamicProperty) [],

   msg = 'A general system error occurred: vix error codes = (3016, 0).\n',

   faultCause = <unset>,

   faultMessage = (vmodl.LocalizableMessage) [],

   reason = 'vix error codes = (3016, 0).\n'

}], possible resolution is []

2019-01-10 14:22:47,626 - vCSACliConvergeLogger - INFO - ================================================================================

2019-01-10 14:22:57,006 - vCSACliConvergeLogger - ERROR - Error occurred. See logs for details.

2019-01-10 14:22:57,007 - vCSACliConvergeLogger - DEBUG - Exception message: com.vmware.vcsa.installer.decommission.task: (vmodl.fault.SystemError) {

   dynamicType = <unset>,

   dynamicProperty = (vmodl.DynamicProperty) [],

   msg = 'A general system error occurred: vix error codes = (3016, 0).\n',

   faultCause = <unset>,

   faultMessage = (vmodl.LocalizableMessage) [],

   reason = 'vix error codes = (3016, 0).\n'

}

Trace:   File "d:\build\ob\bora-9914372\bora\install\vcsa-installer\vcsaConvergeCli\cli_tasks\decommission\decommission_task.py", line 123, in execute

  File "d:\build\ob\bora-9914372\bora\install\vcsa-installer\vcsaConvergeCli\utils\esxvim.py", line 407, in run_command_wait

  File "d:\build\ob\bora-9914372\bora\install\vcsa-installer\vcsaConvergeCli\utils\esxvim.py", line 432, in CheckProcesses

  File "d:\build\ob\bora-9914372\bora\install\vcsa-installer\vcsaConvergeCli\deps\pyVmomi\pyVmomi\VmomiSupport.py", line 557, in <lambda>

  File "d:\build\ob\bora-9914372\bora\install\vcsa-installer\vcsaConvergeCli\deps\pyVmomi\pyVmomi\VmomiSupport.py", line 363, in _InvokeMethod

  File "d:\build\ob\bora-9914372\bora\install\vcsa-installer\vcsaConvergeCli\deps\pyVmomi\pyVmomi\SoapAdapter.py", line 1346, in InvokeMethod

2019-01-10 14:22:57,015 - vCSACliConvergeLogger - INFO - =================================== 14:22:57 ===================================

2019-01-10 14:22:57,016 - vCSACliConvergeLogger - INFO - Result and log file information...

2019-01-10 14:22:57,017 - vCSACliConvergeLogger - INFO - WorkFlow log directory: d:\logs\workflow_1547129680951

Hello

I have 3 hosts Vsphere 6.7 and a Vcenter in 6.7 after the update from 6.5 to 6.7.

I can no longer start a Vm without the following message appears  "Le nombre total de CPU virtuelles présentes ou demandées dans la configuration des machines virtuelles a dépassé la limite de l'hôte : 21. "

I can start the machine directly when I'm on the A machine or is stored the VM but not from the Vcenter, would you have a lead?

best regards.

Excuses if there is already thread about this.

I have request to change the memory and CPU of all VDI desktop.

It is floating pool and desktops are refresh every time user logoffs.

Would you advise best way to approach this?

e.g. Would below be the right approach?

1. I have to shutdown the master image. Change CPU and Memory. power it on.

2. Take snapshot

Any changes are required in the pool settings ? I guess I have to ask user to logoff?

Is there a KB on it ?

Hello,

currently I have a problem, which involves vSphere/VCenter. I have a VCenter with many USB devices connected to different ESXi and I have to connect an USB device to a specific VM on demand. Now I need to know the USB path to these devices. The one that looks like this

deviceName = "path:1/0/3/3/2/5/1 version:2"

I can connect to the ESXi and get this path for device that are already connected to VMs with this command. The second command gives me the ID of the VM, which replaces XXXX in the first command

vim-cmd vmsvc/device.getdevices XXXX | grep path

vim-cmd vmsvc/getallvms

Now the problem is that I do not get the paths for USB devices, that are not connected to a VM. I know that I can connect a device with the device ID, that i get with lsusb, but the problem here is that all my device have the same VendorID and ProductID, because there are the same product and from the same vendor. So the vSphere Client can differentiate between all USB devices and knows which are connected to which ESXi etc. But I did not find any way to get this information via vSphere Web API or some ESXi vim-cmd.

Are there any ways to get this information?

I am using vSphere 5.5

Kind regards

Is it possible to have the "Time Settings" tab for a view take user input?

Or do I have to edit my view each time I want to run a report for a different date range?

Thanks!

Server 2016, latest OS updates

ESXi 6.7.0 Update 1 (Build 10764712)

VMWare Tools 10.3.2 build 9925305

when i run a snapshot with the "Quiesce guest file system" option, the snapshot results in "Failed - An error occurred while quiescing the virtual machine. See the virtual machine's event log for details." (unless i reboot the server first, see below).

in the application log of the server i see nothing helpful. shadow copy is duplicating discs, the lsass service announcing that it's database moved to a new location and is recovering.

DFSRs (2180) \\.\C:\System Volume Information\DFSR\database_E0D0_742D_D074_BD2\dfsr.db: The database engine stopped the instance (0).

lsass (580) Shadow copy instance 7 freeze started.

svchost (2156) Shadow copy instance 7 freeze started.

DFSRs (2180) \\.\C:\System Volume Information\DFSR\database_E0D0_742D_D074_BD2\dfsr.db: The database engine (10.00.14393.0000) is starting a new instance (0).

lsass (580) The database engine is initiating recovery steps.

lsass (580) A database location change was detected from 'C:\Windows\NTDS\ntds.dit' to '\\?\Volume{0943f5ad-14de-11e9-8b96-000c2998569c}\Windows\NTDS\ntds.dit'.

system log shows nothing helpful either. volumes are mounted, and are healthy. what is strange is that one volume gets mounted 12 times (in this case, volume 40)

Volume \\?\Volume{0943f5aa-14de-11e9-8b96-000c2998569c} (\Device\HarddiskVolume36) is healthy.  No action is needed.

Volume \\?\Volume{0943f5ad-14de-11e9-8b96-000c2998569c} (\Device\HarddiskVolume40) is healthy.  No action is needed.

Volume \\?\Volume{0943f5ad-14de-11e9-8b96-000c2998569c} (\Device\HarddiskVolume40) is healthy.  No action is needed.

.... 12 times in total...

Volume \\?\Volume{0943f5ad-14de-11e9-8b96-000c2998569c} (\Device\HarddiskVolume40) is healthy.  No action is needed.

then the message "disk 1 has been surprise removed" but according to a google search this is nothing to worry about. message appears on other vms too, where q-snapshots work fine, so i guess it can be ignored.

the dfsr service gets stuck and doesn't recover, meaning no more sysvol replication between this DC and it's peer. i can create files in sysvol on the partner DC and these files get synced to me, but creating files in sysvol on the affected DC don't get synced back. only a DFSR service restart fixes this.

when i restart the DC, i can do one snapshot with Quiesce option and it works fine, but trying a second time it results in failure again.

apart from searching the net for the entire day, i have tried restarting several services, like the vmware tools service, the VSS service, the DFSR service, but i can not reliably make it work/fail afterwards, and i have so far not the slightest clue why this happens. only a full server reboot can reliably make it work again once.

the only "solution" i found so far was to uninstall the vmware vss helper

this "solved" the problem for good but i am not confident i should leave it like this?

the server is quite a fresh install (5 month), with a fresh domain on it, there is no other software installed on it and it has not been "played with" configuration wise, so this is the most basic OS+AD+Vmwaretools install you can get.

any ideas, anyone?

We have added a puppet node as a vRO configuration endpoint and it was working. Now blueprints fail with timeouts and I can't find where the detailed logs for the puppet calls from the blueprints are being logged.

Have looked in CAFE Catalina.out and IAAS server logs but can't see the info being passed to the puppet server or an explicit error.

Has anyone troubleshooted puppet calls from blueprint provisions?

Thanks Chris

Hey Folks,

I'm having an issue with app Vols and hope someone else has seen something similar and can help out.

Environment

• ESXi 6.5
• App Volumes 2.14
• VMware Horizon 7.5 (Instant Clones)
• VMware UEM 9.4
• Windows 10 Enterprise Build 1709

When we have writable volumes enabled, we're seeing excessive login times upwards of 2 minutes, and get worse with subsequent logins.

First issue is that reviewing the svservices.log, it appears the enabling of the Windows Firewall by the App Vol agent takes an excessive amount of time. If I run the command from an elevated CMD prompt  (within the VM after it has loaded), it takes close to 50 seconds to run, but runs successfully.

This is an example of the firewall launch and completion times

[2018-09-21 22:09:27.158 UTC] [svservice:P1600:T1328] Successfully launched: C:\WINDOWS\system32\cmd.exe /c del /q /f "C:\Program Files (x86)\CloudVolumes\Agent\Logs\cvfirewall.cfg" 2>NUL && netsh advfirewall export "C:\Program Files (x86)\CloudVolumes\Agent\Logs\cvfirewall.cfg" && netsh advfirewall import "C:\Program Files (x86)\CloudVolumes\Agent\Logs\cvfirewall.cfg" (wait -1 ms)

[2018-09-21 22:10:54.641 UTC] [svservice:P1600:T1328] ExitCode 0. Finished waiting for "C:\WINDOWS\system32\cmd.exe /c del /q /f "C:\Program Files (x86)\CloudVolumes\Agent\Logs\cvfirewall.cfg" 2>NUL && netsh advfirewall export "C:\Program Files (x86)\CloudVolumes\Agent\Logs\cvfirewall.cfg" && netsh advfirewall import "C:\Program Files (x86)\CloudVolumes\Agent\Logs\cvfirewall.cfg"" (WaitStatus 0)

The second issue  I have found that if I delete the writable, and recreate it, the login time  decreases dramatically. Subsequent logins after the creation are better, but then they get increasingly worse. It's only until I delete the writable again that things get better.

Has anyone seen anything like this? I had opened a call with VMware support, but they havent been able to solve the problem. Any help you can provide would be much appreciated!

After upgrading to 4.10 I've had audio dropout issues with Skype.

The audio for the whole VDI drops out, meaning I can't listen to a youtube video even until I've reconnected the desktop. It'll work fine for a few minutes and then it's just silence again. Windows audio doesn't show muted or anything.

This seems to only happen during Skype calls/meetings.

Not sure whats going on, but its really frustrating.

I'm going to try and go back to 4.9. Just wondered if anyone else was seeing the same problem.

Thanks.

We had an image accidentally upgrade to 1803. We were unaware when the image was handed to us and attempted to build a new linked clone pool with a persistent disk and it failed to provision. The VMs comes up with the date/time set without the timezone (UTC 0) and eventually fail to provision with error "View Composer agent initialization state error (22): Failed to mount persistent disk. Please check the parent VM if an existing disk is using the same drive letter. (waited 0 seconds)". We recreated the pool without a persistent disk and the linked clones provisioned successfully.

I understand that 1803 is currently listed as a supported for 7.5 and not supported for 7.4 (Supported versions of Windows 10 on Horizon Agent Including All VDI Clones (Full Clones, Instant Clones, and Linked Clones on Horizon 7) (2149393).

Hello everyone,

I'm trying to install the vRealize Operations for horizon desktop agent.do i need to install on every virtual machine or RDS server/Terminal server ?

Can you help me please and how to install the desktop agent on RDS server or Any of the machine can you help me please.

Ravi

  I have been having issues trying to pull the provisioned space per connected datastore of each VM.  I can get the total provisioned space of the VM via 'ProvisionedGB' but this total is across all of the VM's connected datastores.  What I need is a .CSV that contains a breakdown of all datastores connected to each VM and the provisioned space that VM is using on each connected datastore.  I have modified several scripts but I am uncertain on how to get this information.  Most scripts I have worked with look something like the line below where it only pulls one of the connected datastores.

"where {$_.ID -match (($vmview.Datastore | Select -First 1) | Select Value).Value}"

Currently, I am pulling the below details and I realize there will be redundant info this way if we add additional rows for each disk and/or datastore.  I am open to other suggestions you may have. 

(Current Column Layout)

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

| VMName | Powerstate | OS | IPAddress | ToolsStatus | NumCPU | MemGB | Datastore | DiskType | DiskGb | DiskFree | DiskUsed | ProvisionedSpace |

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

Perhaps adding each datastore name to the columns would help prevent redundant data and simply add the VM's provisioned space of that specific datastore to these columns? 

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

Example:  | VMName | etc. | Datastore_1 | Datastore_2 | Datastore_3 |

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

.

..

...

  Anyway, below is the current script I have been modifying.  As you can see it will only pull one connected datastore per VM although the VM's have multiple datastores attached.  The "Guest.Disks" and "ProvisionedSpaceGB" properties will measure all VM guest disks and provisioned space regardless of what datastore.  I need to figure out how to break these fields down to a per datastore equation for each VM guest. 

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

START SCRIPT:

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

filter Get-FolderPath {

    $_ | Get-View | % {

        $row = "" | select Name, Path

        $row.Name = $_.Name

        $current = Get-View $_.Parent

        $path = ""

        do {

            $parent = $current

            if($parent.Name -ne "vm"){$path = $parent.Name + "\" + $path}

            $current = Get-View $current.Parent

        } while ($current.Parent -ne $null)

        $row.Path = $path

        $row

    }

}

$VCServerName = "vsphere.com"

$VC = Connect-VIServer $VCServerName

$ExportFilePath = "C:\TEST.csv"

$Report = @()

$VMs = Get-VM | Where-Object { $_.Name -like 'Client*' }

$Datastores = Get-Datastore | select Name, Id

$VMHosts = Get-VMHost | select Name, Parent

ForEach ($VM in $VMs) {

      $VMView = $VM | Get-View

      $VMInfo = {} | Select VMName, Powerstate, OS, IPAddress, ToolsStatus, NumCPU, MemGB, Datastore, DiskType, DiskGb, DiskFree, DiskUsed, ProvisionedSpace

      $VMInfo.VMName = $vm.name

      $VMInfo.Powerstate = $vm.Powerstate

      $VMInfo.OS = $vm.Guest.OSFullName

      $VMInfo.IPAddress = $vm.Guest.IPAddress[0]

      $VMInfo.ToolsStatus = $VMView.Guest.ToolsStatus

      $VMInfo.NumCPU = $vm.NumCPU

      $VMInfo.MemGB = [Math]::Round(($vm.MemoryGB),2)

      $VMInfo.Datastore = ($Datastores | where {$_.ID -match (($vmview.Datastore | Select -First 1) | Select Value).Value} | Select Name).Name

      $VMInfo.DiskType = $DiskTypes[$VMInfo.Datastore]

      $VMInfo.DiskGb = [Math]::Round((($vm.Guest.Disks | Measure-Object -Property CapacityGB -Sum).Sum),2)

      $VMInfo.DiskFree = [Math]::Round((($vm.Guest.Disks | Measure-Object -Property FreeSpaceGB -Sum).Sum),2)

      $VMInfo.DiskUsed = $VMInfo.DiskGb - $VMInfo.DiskFree

      $VMInfo.ProvisionedSpace = [math]::round(($vm.ProvisionedSpaceGB), 2)

      $Report += $VMInfo

}

$Report = $Report | Sort-Object VMName

IF ($Report -ne "") {

    $report | Export-Csv $ExportFilePath -NoTypeInformation

}

$VC = Disconnect-VIServer -Confirm:$False

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

END SCRIPT:

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

Hello,

I'm using PowerCli on a CentOS 7 VM, and I can't connect to some ESXi. There is actually only one that I can connect to, it's a sandbox, its version is 6.7.0.

The others are on version 6.5.0, and are prod ones. I can ping every ESXiand they are accessible on port 443.

PowerShell version:

PS /root> $PSVersionTable

Name                           Value

----                           -----

PSVersion                      6.1.1

PSEdition                      Core

GitCommitId                    6.1.1

OS                             Linux 3.10.0-957.el7.x86_64 #1 SMP Thu Nov 8 23:39:32 UTC 2018

Platform                       Unix

PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}

PSRemotingProtocolVersion      2.3

SerializationVersion           1.1.0.1

WSManStackVersion              3.0

PowerCli version:

PS /root> Get-Module VMWare.PowerCLI -ListAvailable

    Directory: /usr/local/share/powershell/Modules

ModuleType Version    Name                                PSEdition ExportedCommands

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

Manifest   11.1.0.... VMware.PowerCLI                     Desk

This is what I get when I connect to the sandbox:

PS /root> Connect-VIServer sandbox

Specify Credential

Please specify server credential

User: userName

Password for user userName: ***********

Name                           Port  User

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

sandbox                        443   userName

And this what I get with production ones:

PS /root> Connect-VIServer -Server productionServer [-Protocol https] [-Port 443]

Specify Credential

Please specify server credential

User: userName

Password for user userName: **********

Connect-VIServer : An error occurred while sending the request.

At line:1 char:1

+ Connect-VIServer -Server productionServer -Protocol https - ...

+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

+ CategoryInfo          : NotSpecified: (:) [Connect-VIServer], CommunicationException

+ FullyQualifiedErrorId : System.ServiceModel.CommunicationException,VMware.VimAutomation.ViCore.Cmdlets.Commands.ConnectVIServer

I tried with different kind of options without success...

On the other hand I can access those ESXi from my computer but not all, because of an intern policy that came up to avoid 443 port openning for no reason (web client use another port), this why I need to access ESXi with this VM.

I can't do anything I want on those ESXi, I may not be able to access configuration or logs.

Regards

Is there a cost associate with Skyline?

Does anyone know how to determine the reason(s) why a host is not compatible instead of just that it isn't? The published script is saying not compatible. I have 4 hosts of the same Dell Server but one of them is saying it's not compatible. I see this article but it's just a plain english list not a way to determine which is the reason and more specifics. Doesn't make sense to me why one is and the others aren't. https://kb.vmware.com/s/article/52477 :

You may see this issue if:

• Host platform is not supported.
• Host is configured to use a TPM.
• passthru devices configured for VMs on your host.
• vmklinux drivers loaded on your host.
• Other non-certified drivers loaded on your host
• Quick Boot is disabled in the Update Manager UI.

We are not using TPM chips, it's enabled in the UI, We use baselines for all hosts so can't imagine a non-certified driver being installed, but even if there were no idea how to tell which one. I'm not aware of any VMs using passthru, but then again no easy way that I know of to determine if any VM were using that (There are tons on this one host). It's a Dell PowerEdge R740x like the others and according to Dell it's supported: https://www.dell.com/support/article/us/en/04/sln314672/quick-boot-of-vmware-esxi-on-dellemc-power-edge-servers?lang=en

Resuming a CentOS 7 guest went up from seconds to minutes. I have an APFS SSD. Is there a known issue?

I'm running a VM on vSphere 6.5 ..Windows 10 brand new install, not on any domain .. firewall free .. nothing but the vmware tools installed

On only one particular website (banking services) , i'm getting this message err_connection_timed_out but not always .. it could run ok for a few session (with restart) . Then after 10 restart, it starts failing (err_connection_timed_out) ... after while few more restart it starts working again without changing anything ... it looks like the website doesnt want to answer the request sometimes when it comes from vSphere environment. We were not able to make it work if it was not working without rebooting the VM until I noticed that if i switch the Network Card to Vmxnet3 instead of E1000 or E1003 during a session .. magically it seems to fix the problem .... but if i keep the VMXNET3 and start rebooting .. it will fail eventually!

we've tried different Service Providers, with and without Firewall always the same thing happening .... it's only happening on vm running on vSphere .. no problem what's so ever with any other device

As a test, i've tried the same thing with Windows 7 ... same thing is happening ... and only for that website ...

We've been trying to figure out what was happening with the bank but  ... we haven't had no cooperation so far!

Maybe someone have seen this before .. ?

I'm trying to connect to vSphere to remote control a machine but I'm being unable to because the application hangs.

I tried to check for logs in /var/log/vmware but there are only USB arbitrator errors. Including:

usbArb| I125: [msg.dictionary.load.openFailed] Cannot open file "/usr/lib/vmware/config": No such file or directory.

How can I diagnose and solve such issue?