Network PC World

So the issue is, I can ping the gateway IP address and access the internet from inside Virtual Machine running under VMware Workstation 16.x. But I am unable to access the same VM from my laptop or any machine on the local subnet address of that Bridge Adapter.  I followed all the troubleshooting steps at VMware KB  Troubleshooting network connectivity issues for Windows virtual machines in VMware Workstation (2019836)  and also followed a long list of suggested fixes at the vmware community discussion  Network Bridge Mode Not Working Windows 10 Host , but nothing worked for me.  My VM and workstations was running for months without any issue and suddently this isssue has happed, so I started thinking of installing recent programs in my laptop that might cause the issue. And I found that one of the recent program installed in my PC is Citrix Gateway app, I could also see a virtual network adapter create by this app in the Network and Sharing Center .  Upon ...

While converting physical Windows 7 machine to Virtual machine of infrastructure type, I got this error. The error seems it is unable to read/write source or destination datastore. I have installed VMware-converter-en-6.2.0-8466193 on Windows 7 physical machine with option locally selected. (not at server/client option) All of my ESXi servers are connected to the vCenter Server, so I had to use vCenter Server's IP address to send this physical machine to the virtual world. The issue i found was with the dns resolution to the vCenter Server's hostname. Since I am not using the same dns server on the Windows 7 client machine. So I updated the host entries manually for the vCenter Server's hosname to it IP address. After adding dns eteries to the hostfile of windows 7, I am not getting this "a file I/O error has occurred while accessing vmware converter" and the migration has started. 

I got this issue with my iSCSI disk provided by Microsoft Windows Server. I am able to access the iSCSI datastore, all of my Virtual Machines are operational with any issue, my iSCSI datastore is showing as inactive but its status is showing normal. It happend after I had removed iSCSI targets from Windows but and added new target after some time. What I did; Rescanned all datastore multiple times --- no luck restarted management services from SSH of all ESXi hosts with command  $ services.sh restart --- no luck Removed and re-added targets from iSCSI (Windows) Side --- no luck Removed few VMs which were in inaccessible state and then rescanned datastore --- no luck Finally restarted each ESXi host at a time, it solved the problem.

I was getting this error while removing Operating System ISO image mounted on the Virtual Machine. What worked for me, is 1. Uncheck the "Connected and Connect at power on" from Device Status. 2. Then Change the Device type from " Datastore ISO File to Client Device " Radio Button 3. and press OK to save the changes. Note:- I was able to remove the mounted ISO only by directly logging to the ESXi at https://esxi-ip-address/ui where it asks "The guest operating system has locked the CD-ROM door and is probably using the CD-ROM, which can prevent the guest from recognizing media changes. If possible, eject the CD-ROM from inside the guest before disconnecting. Disconnect anyway and override the lock?" You need to select yes to eject the CD-ROM and then remove the ISO file successfully.

This error occurs repeatedly while adding ESXi host to the Nexus 1000v. The problem seems with the VMWare Update Manager (VUM) that it doesn't initiate the required VEM module for the installation on the ESXi host we are adding to the Nexus 1000v. I solved my problem by manually installing the .vib file on the ESXi host. And here are the steps to follow. Go to the Nexus 1000v through web browser You get list of links to download files, download your required .vib file from there. for me it was Cisco_bootbank_cisco-vem-v340-esx_5.2.1.3.2.8.0-6.0.1.vib Upload that vib file to the ESXi host with WinSCP, say in the /tmp folder Run following command to install the .vib file .i.e. the vem module. esxcli software vib install -v /tmp/Cisco_bootbank_cisco-vem-v340-esx_5.2.1.3.2.8.0-6.0.1.vib After the .vib file has been installed successfully, add the ESXi host to the Nexus 1000v.

After the VMWare upgrade from 5.x to 6.x and Nexus 1000v upgrade from 4.2 to 5.2 you are unable to add new hosts into the Nexus 1000v distributed switch, although the older hosts are seed added to the N1Kv distributed switch and running fine without any issues. This happens because Nexus 1000v has no knowledge of new versions of vCenter Server in its postgress database. You have to manually add the new version in the vCenter database to support the new Version. First you need to log in the the VCDB on command line, and for that you need to find the userID and password. To get the userID and password, open C:\ProgramData\VMware\vCenterServer\cfg\vmware-vpx\vcdb.properties vcdb.properties file contents should look like this driver = org.postgresql.Driverdbtype = PostgreSQLurl = jdbc:postgresql://localhost:5432/VCDB username = vc password = {FNr2Aad>ws8Xo<Q password.encrypted = false Grab the username and password (default userID happend to be "vc" and th...

I have installed Ubuntu Desktop 16.04.4 on ESXi 6.0. Tried to increase the pixel density so that i can view the big Screen on my other 27 inch screen through VMWare client. I tried installing open-vmtools but remained unsuccessful. Then installed VMWare tools by mounting through VMWare client (tools that come with ESXi 6.0 but again remained unsuccessfull. The third try was to download latest VMtools from VMWare website, uploaded to uploaded to the /tmp folder of ubuntu through WinSCP server and then installed as per given procedure on VMWare website. I shut down the Ubuntu VM Increase the Video Card Memory from Default to 16 MB. Restarted Virtual Machine, this time I was getting bunch of options for increasing screen size of the Ubuntu Display and successfully running my VM at  resolution of 1440x900 (16:10).

Before installing an VMWare ESXi server i was little curious that what VMTools version will come after the ESXi have been installed and any VM has been created. Looking around found a link on VMWare worth to share and keep handy while working on the deployment of VMWare especially before upgrading and existing VMWare infrastructure to newer one you would like to know the VMTools version, its support with your Operating Systems in Guest OS and/or read upon open or resolved caveats by identifying the VMTools version prior the installation and choosing the right version for your environment. Below information has been collected from the link  here # The ESXi server mapping is only to show that the particular version of # Tools ships with that particular ESXi server build number, but the Tools # can work with a greater range of ESXi versions. # # Column 1: Tools version on NGC/VI Client # Column 2: ESXi server version.'esx/0.0' indicates that the tools version # is not yet bu...