Does anyone have any ideas? if not I will log with VMware.
Thanks
Does anyone have any ideas? if not I will log with VMware.
Thanks
I guess the reason you couldn't use your smart card to log in to dcui is because there's no middle-ware installed on ESXi for your smart card. As far as I know, it only works for DoD and Java card.
--Lance
I stopped all VMWare Services, made them all manual Start, then started VMWare. Sure enough, I couldn't get an IP Address until I started VMNAT,exe, and the service shows us as the Syswow64 version. There are 3 other VMNAT,exe files on my PC, all in directories that have the words "Duplicate Data" in the folder name somewhere. All the certificates for those application files expired in 2010, and just feature SHA1, The Syswow64 version expires in 2026, and includes SHA256. So, it seems that the Syswow64 version is the correct one - though VMWare perhaps could have cleaned up the old ones, and found a different place to put this application? (I have had VMWare Workstation for a long time, multiple upgrades.)
What it doesn't explain is the network activity. Yesterday at about 1 PM, Norton detected VMNat.exe attempting to transmit data to 104.28,1.101:80, and blocked the attempt, accusing VMNat.exe as the culprit. My firewall logs showed that a similar attempt was successful at about 11:30 that morning, for 54 seconds to the same IP Address. A lot of data can be transferred in 54 seconds. The previous time the IP Address was 166.52.27.58. Both were from my base OS Windows system, and I never use it to browse.
So, I am still worried that somehow VMNAT,EXE is corrupted somehow.
Here is what appears to be the offending record from McAfee HIPS (Host Intrusion Prevention System) logs... (obfuscated of course)
Its still not fixed as of the date below ...
Time: | 5/11/2017 7:46:36 PM |
Event: | Intrusion |
IP Address/User: | MYDOMAIN\myusername |
Description: | COM Surrogate (dllhost.exe) |
Path: | C:\WINDOWS\SYSWOW64\DLLHOST.EXE |
Message: | Attack type: VMWare Workstation Shielding - File Modification (Sig Id = 3872) |
Hi,
I have two VCenters at different locations and trying to run cross vCenters cold vMotion.
I have vSphere 6.0 U2 Enterprise Plus.
Everything works well on Default TCP/IP stack, but I would like to use Provisioning stack.
It is configured and ESXi servers on both sides can ping each other via vmkernel interfaces on Provisioning TCP stack.
However cold vMotion doesn't work. Giving me "Can not connect to host" error
I kind of found the issue: NFC service doesn't listen on port 902 on Provisioning stack vmkernel interfaces. vxpa.log confirms my guess.
However I don't know how to fix this and force NFC to work on Provisioning TCP stack.
I saw only one similar case here: Cross vCenter vMotion – Cannot connect to host – verbrough
However the recommended workaround doesn't work in my case.
Just wondering if somebody have the same issue or have any ideas/suggestions.
Thanks
Since you're using a nested ESXi host, you can add how many network adapter you want to the ESXi virtual machine, that is not limited by the number of physical adapter.
I've set up a Fujitsu DX100 S3 SAN with four iSCSI connections. As far as I know it's been correctly set up and I have tested this by connecting the SAN to a server which has correctly mounted the volumes.
My issue is trying to connect this SAN to our VMWare environment running vCentre 5.0.
The SAN appears in the Static Discovery tab in the iSCSI Storage Adaptor properties when entering the IP addresses of the iSCSI connections in the Dynamic Discovery tab (including the correct IQN names for the connections).
However, the problems start when a rescan of the storage adaptor is performed. The SAN does not show up on the devices section.
After checking the log files I noticed that in the vmkernel.log file there is an entry for when the SAN is bought ONLINE but soon after there is another entry (a warning) which reads:
"...iSCSI connection is being marked "OFFLINE" (Event: 4)"
Does anyone have any ideas as to what's going on and how I can resolve this issue and get the SAN connected to our VMWare environment?
It is not being decided which NAT to use whether SNAT or DNAT. But my design should be made such a way that it should work both with SNAT & DNAT.
Let me know if the below will work.
- Edge Gatewayh# 1 - One Uplink
- My Physical devices (R1 & R2) are running in VSS (Catalyst switches)
- Having a pair of Nexus 5K switches connecting the ESXi to the R1 & R2.
- Nexus 5K side - vPC
- R1 & R2 - Port Channel
Let me know if this will work.
I have tried reapplying the storage policy to each VM but it still shows the compliance status as out of date for each virtual object. The last checked date is over a week ago and doesn't change. Any ideas on how to fix? Previously when I reapplied the storage policy it would fix any out of date virtual objects.
I am trying just to change my VMTN Community email address ( which appears incorrect )
I read the docs on logging into myvmware.com portal to change it but my email address over there is correct...
what do i do ?
thx
Big_Daddy68
After another 4 years is there a better solution provided by vmware?
Now for several days I have had the vCenter doing failovers several times a day.
the vcenter version is vsca 6.5.0 4602587.
When I browser the datastores,it's OK at first.But I continue to browser other datastore(almost the sixth),the vcenter will become unavailable and do failover in progress.
I don't why
I am afraid it is more likely it is the VM(s) that are infected with malware rather than having a corrupted vmnat.exe.
Whatever network connections you see in the VM through command prompt netstat, will show up as connections in the Windows host with [vmnat.exe] as the binary executable involved in the connection using netstat -b in the command prompt (Admin).
The "rules of the road" for internet safety/security still apply when using VMs to browse the internet. It is not any more safe than using the host machine; in some instances it might be even less safe.
On example is using VMs via NAT to surf internet on a public WiFi. I haven't used Windows in a public WiFi for a while. But I recall that with Windows 7, you have the choice to choose "Public network" when connecting to a public WiFi such as in hotels/airports/etc. The problem with VMs through NAT is that its network profile won't change as it still see the VMNAT as the same network. So if it is set up for "Home Network" more ports are open and the VM connect through NAT on a public WiFi, the "Home Network" profile remains and in theory makes it more vulnerable.
Hi haralds,
Did you try to reset NVRAM on your Mac Pro? You can follow the instruction from Apple and see if it helps.
Regards,
-Rick
It is not being decided which NAT to use whether SNAT or DNAT. But my design should be made such a way that it should work both with SNAT & DNAT.
Let me know if the below will work.
- Edge Gatewayh# 1 - One Uplink
- My Physical devices (R1 & R2) are running in VSS (Catalyst switches)
- Having a pair of Nexus 5K switches connecting the ESXi to the R1 & R2.
- Nexus 5K side - vPC
- R1 & R2 - Port Channel
Will this work.
Inside the vCO client you need to switch to "Design" mode and then select the "resource" button. It is there that you need to upload your add or file.
to copy the file to a VM here is the first scriptable task:
var vcoPath = System.getTempDirectory() + "/" + System.nextUUID();
resourceElement.writeContentToFile(vcoPath);
var host = vm.sdkConnection;
var date = Date.now();
var dateStart = new Date(date);
var startDate = System.formatDate(dateStart, "yyyyMMdd");
var fileName = "VMPROFILE"+startDate+".csv";
//var guestFilePath = "D:\\\\temp\\"+fileName
var guestFilePath = "\\\\server\\folder\\\\"+fileName
var guestOperationsManager = host.guestOperationsManager;
var guestAuth = new VcNamePasswordAuthentication();
guestAuth.username = vmUsername;
guestAuth.password = vmPassword;
var fileManager = guestOperationsManager.fileManager;
result = false;
var attr = new VcGuestFileAttributes();
var srcFile = new File(vcoPath);
var uri = fileManager.initiateFileTransferToGuest(vm , guestAuth ,guestFilePath, attr, srcFile.length, overwrite);
result = fileManager.putFile(vcoPath, uri);
Is it port 80?
I can see "app-volume-manager-name:80"
Perfect! I'll give it a try. I would THINK it would work. I'll give it a shot. Thanks!
It is randomly happening with random users
Thanks, Ulli. I created an image and uploaded to naa.6001e6775e8220001a267f61499bf7bd.1500.bin - Google Drive . Hopefully this holds some good news. Please let me know if you need anything else to help diagnose.