VMware Communities
am_2009_
Contributor
Contributor
‎02-12-2021 11:52 AM

host-only adapter driver does not seem to be running

hello

I'm using VMware player for gns3 VM let me start explaining my problem from the beginning 

When I first installed the hypervisor program (as administrator) what does happen is that the installer took a long time installing the virtual network adapters, I checked with the task maneger , it seems that virtual network editor is not responding and I think that is the reason for the problem I have later on.

installationinstallation

My problem is having the Vmnet0 not working in VMware player whatsoever , and gns3 VM need to connect using host-only adapter for it to integrate with gns3 GUI .

a log massege is displayed after VM starts up saying host-only adapter driver does not seem to be running

ProblemProblem

and by the way , I couldn't fing Vmnetcfg.exe to reinstall Vmnet0 and reinstalling VMware player didn't solve the problem.

could anyone please help.

0 Kudos
4 Replies
RaSystemlord
Expert
Expert
‎02-15-2021 02:28 AM

Since no replies, I will give this a try.

Your deduction that the problem is about VMware install, is probably right. VM itself would work if Host were OK.

What makes a VMware install fail? Well, in general:

- what is your exact host version. Looks like Windows, but what is it?

- is there some history to the Windows computer ... I mean, they do get screwed up in time and correcting them isn't necessary trivial, sometimes it is next to impossible

- have you installed all Windows updates? Not all are required, but this is to say that the necessary ones needs to be there. It is next to impossible otherwise, if not all are installed, to say, what needs to be there.

- especially installer updates needs to be there. Surely, install will fail if those aren't updates ... as is relevant to the particular application (no idea, what installer VMware is dependent on)

- what happened during install of VMware? Hard to see that you didn't get any error message of a failed VMware network install

- Event Viewer is a place where to look for guidance of errors in Windows, which do not produce an error message

- the other place to check is perhaps temp-directory, both user and Windows system, if something was written there of a failed install

I hope this helps.

0 Kudos
am_2009_
Contributor
Contributor
‎02-15-2021 05:05 AM

hi there

the is my windows version, I also checked for update and my PC is up to date

mngfhnj,.jpg

0 Kudos
continuum
Immortal
Immortal
‎02-15-2021 05:21 AM

Chceck your windows registry:

do you have
HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Enum\ROOT\VMWARE\0000
HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Enum\ROOT\VMWARE\0001

If not your VMplayer installation is incomplete.

Ulli

 


________________________________________________
Do you need support with a VMFS recovery problem ? - send a message via skype "sanbarrow"
I do not support Workstation 16 at this time ...

0 Kudos
am_2009_
Contributor
Contributor
‎02-17-2021 05:02 AM

I'm sure I don't have these entries in my registry

 

today I checked the istall log in C:\Windows\Temp at file vminst

 

here it is

2021-02-17T15:16:54.870+03:00| inst-build-17198959| E1: VNLCallBridgeIoctl: ioctl call failed: 0x000005aa
2021-02-17T15:16:54.880+03:00| inst-build-17198959| I2: VNL_GetNumberOfVnets: number of vnets: 20
2021-02-17T15:16:54.884+03:00| inst-build-17198959| I2: VNL_GetNumberOfVnets: number of vnets: 20
2021-02-17T15:16:54.885+03:00| inst-build-17198959| E2: VNLStartupCOM: security specification failed since already set (ignoring)
2021-02-17T15:16:54.885+03:00| inst-build-17198959| I2: ProcessSpecificHostAdapter: finished with COM initialization (attempt)
2021-02-17T15:16:54.885+03:00| inst-build-17198959| I2: WMI_ConnectToWMI: Connecting to WMI server
2021-02-17T15:16:54.891+03:00| inst-build-17198959| I2: WMI_ConnectToWMI: Connected to WMI server
2021-02-17T15:16:54.891+03:00| inst-build-17198959| I2: AdjustSecurity: security query success
2021-02-17T15:16:54.891+03:00| inst-build-17198959| I2: AdjustSecurity: authn 0x0000000a authz 0x00000000
2021-02-17T15:16:54.891+03:00| inst-build-17198959| I2: AdjustSecurity: servername NT AUTHORITY\SYSTEM
2021-02-17T15:16:54.891+03:00| inst-build-17198959| I2: AdjustSecurity: authLev 0x00000006 imp 0x00000003
2021-02-17T15:16:54.891+03:00| inst-build-17198959| I2: AdjustSecurity: authInfo 0x00000000 capabilities 0x00000041
2021-02-17T15:16:54.957+03:00| inst-build-17198959| I2: ProcessSpecificHostAdapter: next enumerator returned: 0x00000001
2021-02-17T15:16:54.957+03:00| inst-build-17198959| I2: ProcessSpecificHostAdapter: Next() returned 14 items
2021-02-17T15:16:54.957+03:00| inst-build-17198959| E2: ProcessSpecificHostAdapter: descriptions don't match at character 0
2021-02-17T15:16:54.957+03:00| inst-build-17198959| I2: ProcessSpecificHostAdapter: at end of loop
2021-02-17T15:16:54.957+03:00| inst-build-17198959| E2: ProcessSpecificHostAdapter: descriptions don't match at character 0
2021-02-17T15:16:54.957+03:00| inst-build-17198959| I2: ProcessSpecificHostAdapter: at end of loop
2021-02-17T15:16:54.957+03:00| inst-build-17198959| E2: ProcessSpecificHostAdapter: descriptions don't match at character 0
2021-02-17T15:16:54.957+03:00| inst-build-17198959| I2: ProcessSpecificHostAdapter: at end of loop
2021-02-17T15:16:54.957+03:00| inst-build-17198959| E2: ProcessSpecificHostAdapter: descriptions don't match at character 0
2021-02-17T15:16:54.957+03:00| inst-build-17198959| I2: ProcessSpecificHostAdapter: at end of loop
2021-02-17T15:16:54.957+03:00| inst-build-17198959| E2: ProcessSpecificHostAdapter: descriptions don't match at character 0
2021-02-17T15:16:54.957+03:00| inst-build-17198959| I2: ProcessSpecificHostAdapter: at end of loop
2021-02-17T15:16:54.957+03:00| inst-build-17198959| E2: ProcessSpecificHostAdapter: descriptions don't match at character 0
2021-02-17T15:16:54.957+03:00| inst-build-17198959| I2: ProcessSpecificHostAdapter: at end of loop
2021-02-17T15:16:54.957+03:00| inst-build-17198959| E2: ProcessSpecificHostAdapter: descriptions don't match at character 0
2021-02-17T15:16:54.957+03:00| inst-build-17198959| I2: ProcessSpecificHostAdapter: at end of loop
2021-02-17T15:16:54.957+03:00| inst-build-17198959| E2: ProcessSpecificHostAdapter: descriptions don't match at character 0
2021-02-17T15:16:54.957+03:00| inst-build-17198959| I2: ProcessSpecificHostAdapter: at end of loop
2021-02-17T15:16:54.957+03:00| inst-build-17198959| E2: ProcessSpecificHostAdapter: descriptions don't match at character 0
2021-02-17T15:16:54.957+03:00| inst-build-17198959| I2: ProcessSpecificHostAdapter: at end of loop
2021-02-17T15:16:54.957+03:00| inst-build-17198959| E2: ProcessSpecificHostAdapter: descriptions don't match at character 0
2021-02-17T15:16:54.957+03:00| inst-build-17198959| I2: ProcessSpecificHostAdapter: at end of loop
2021-02-17T15:16:54.957+03:00| inst-build-17198959| E2: ProcessSpecificHostAdapter: descriptions don't match at character 0
2021-02-17T15:16:54.957+03:00| inst-build-17198959| I2: ProcessSpecificHostAdapter: at end of loop
2021-02-17T15:16:54.957+03:00| inst-build-17198959| E2: ProcessSpecificHostAdapter: descriptions don't match at character 0
2021-02-17T15:16:54.957+03:00| inst-build-17198959| I2: ProcessSpecificHostAdapter: at end of loop
2021-02-17T15:16:54.957+03:00| inst-build-17198959| E2: ProcessSpecificHostAdapter: descriptions don't match at character 0
2021-02-17T15:16:54.957+03:00| inst-build-17198959| I2: ProcessSpecificHostAdapter: at end of loop
2021-02-17T15:16:54.957+03:00| inst-build-17198959| E2: ProcessSpecificHostAdapter: descriptions don't match at character 0
2021-02-17T15:16:54.958+03:00| inst-build-17198959| I2: ProcessSpecificHostAdapter: at end of loop
2021-02-17T15:16:54.958+03:00| inst-build-17198959| I2: ProcessSpecificHostAdapter: next enumerator returned: 0x00000001
2021-02-17T15:16:54.958+03:00| inst-build-17198959| I2: ProcessSpecificHostAdapter: all network cards properly enumerated
2021-02-17T15:16:54.960+03:00| inst-build-17198959| I2: VNL_GetVnetAdapterStatus: searched for adapter 'vmnet0': installed=FALSE IP=FALSE IPX=FALSE
2021-02-17T15:16:54.960+03:00| inst-build-17198959| I2: GetVnetParameter: vmnet: 'vmnet0' 'NAT' 'UseNAT'
2021-02-17T15:16:54.960+03:00| inst-build-17198959| E2: GetVnetParameter: vmnet config not found: vmnet0\NAT
2021-02-17T15:16:54.960+03:00| inst-build-17198959| I2: VNLRegistryGetVnetUseNAT: got result 0 and value 0
2021-02-17T15:16:54.960+03:00| inst-build-17198959| I2: GetVnetParameter: vmnet: 'vmnet0' 'DHCP' 'UseDHCP'
2021-02-17T15:16:54.960+03:00| inst-build-17198959| I2: GetVnetParameter: type of 'UseDHCP': 0x00000004
2021-02-17T15:16:54.960+03:00| inst-build-17198959| I2: VNLRegistryGetVnetUseDHCP: got result 1 and value 1
2021-02-17T15:16:54.961+03:00| inst-build-17198959| I2: VNL_GetNumberOfVnets: number of vnets: 20
2021-02-17T15:16:54.961+03:00| inst-build-17198959| I2: GetVnetParameter: vmnet: 'vmnet0' 'DHCP' 'DHCPDefaultLeaseDuration'
2021-02-17T15:16:54.962+03:00| inst-build-17198959| E2: GetVnetParameter: registry value 'DHCPDefaultLeaseDuration' not found
2021-02-17T15:16:54.962+03:00| inst-build-17198959| E2: VNLGetVnetParameterAs8BitString: registry parameter not found
2021-02-17T15:16:54.962+03:00| inst-build-17198959| I2: VNLGetVnetParameterAs8BitStringWithDefault: using default value 1800 for parameter: DHCPDefaultLeaseDuration
2021-02-17T15:16:54.962+03:00| inst-build-17198959| I2: VNL_GetNumberOfVnets: number of vnets: 20
2021-02-17T15:16:54.962+03:00| inst-build-17198959| I2: GetVnetParameter: vmnet: 'vmnet0' 'DHCP' 'DHCPMaxLeaseDuration'
2021-02-17T15:16:54.962+03:00| inst-build-17198959| E2: GetVnetParameter: registry value 'DHCPMaxLeaseDuration' not found
2021-02-17T15:16:54.962+03:00| inst-build-17198959| E2: VNLGetVnetParameterAs8BitString: registry parameter not found
2021-02-17T15:16:54.962+03:00| inst-build-17198959| I2: VNLGetVnetParameterAs8BitStringWithDefault: using default value 7200 for parameter: DHCPMaxLeaseDuration
2021-02-17T15:16:54.963+03:00| inst-build-17198959| I2: VNL_GetNumberOfVnets: number of vnets: 20
2021-02-17T15:16:54.963+03:00| inst-build-17198959| I2: GetVnetParameter: vmnet: 'vmnet0' 'DHCP' 'DHCPLeaseBeginIP'
2021-02-17T15:16:54.963+03:00| inst-build-17198959| E2: GetVnetParameter: registry value 'DHCPLeaseBeginIP' not found
2021-02-17T15:16:54.963+03:00| inst-build-17198959| E2: VNLGetVnetParameterAs8BitString: registry parameter not found
2021-02-17T15:16:54.963+03:00| inst-build-17198959| I2: VNL_GetDHCPParam: computing default parameter for lease begin
2021-02-17T15:16:54.963+03:00| inst-build-17198959| I2: ComputeLeaseIP: computing subnet-derived dhcp range addr
2021-02-17T15:16:54.963+03:00| inst-build-17198959| I2: VNL_GetNumberOfVnets: number of vnets: 20
2021-02-17T15:16:54.963+03:00| inst-build-17198959| I2: ComputeLeaseIP: using vnet-specified subnet addr: 192.168.235.0
2021-02-17T15:16:54.963+03:00| inst-build-17198959| I2: VNL_GetNumberOfVnets: number of vnets: 20
2021-02-17T15:16:54.963+03:00| inst-build-17198959| I2: ComputeLeaseIP: using vnet-specified subnet mask: 255.255.255.0
2021-02-17T15:16:54.963+03:00| inst-build-17198959| I2: ComputeLeaseIP: subnet ip : 0xc0a8eb00
2021-02-17T15:16:54.963+03:00| inst-build-17198959| I2: ComputeLeaseIP: subnet mask: 0xffffff00
2021-02-17T15:16:54.963+03:00| inst-build-17198959| I2: ComputeLeaseIP: subnet result: 0xc0a8eb80
2021-02-17T15:16:54.963+03:00| inst-build-17198959| I2: ComputeLeaseIP: Computed subnet DHCP range start addr: 192.168.235.128
2021-02-17T15:16:54.963+03:00| inst-build-17198959| I2: VNL_GetNumberOfVnets: number of vnets: 20
2021-02-17T15:16:54.963+03:00| inst-build-17198959| I2: GetVnetParameter: vmnet: 'vmnet0' 'DHCP' 'DHCPLeaseEndIP'
2021-02-17T15:16:54.965+03:00| inst-build-17198959| E2: GetVnetParameter: registry value 'DHCPLeaseEndIP' not found
2021-02-17T15:16:54.965+03:00| inst-build-17198959| E2: VNLGetVnetParameterAs8BitString: registry parameter not found
2021-02-17T15:16:54.965+03:00| inst-build-17198959| I2: VNL_GetDHCPParam: computing default parameter for lease end
2021-02-17T15:16:54.965+03:00| inst-build-17198959| I2: ComputeLeaseIP: computing subnet-derived dhcp range addr
2021-02-17T15:16:54.965+03:00| inst-build-17198959| I2: VNL_GetNumberOfVnets: number of vnets: 20
2021-02-17T15:16:54.965+03:00| inst-build-17198959| I2: ComputeLeaseIP: using vnet-specified subnet addr: 192.168.235.0
2021-02-17T15:16:54.965+03:00| inst-build-17198959| I2: VNL_GetNumberOfVnets: number of vnets: 20
2021-02-17T15:16:54.965+03:00| inst-build-17198959| I2: ComputeLeaseIP: using vnet-specified subnet mask: 255.255.255.0
2021-02-17T15:16:54.965+03:00| inst-build-17198959| I2: ComputeLeaseIP: subnet ip : 0xc0a8eb00
2021-02-17T15:16:54.965+03:00| inst-build-17198959| I2: ComputeLeaseIP: subnet mask: 0xffffff00
2021-02-17T15:16:54.965+03:00| inst-build-17198959| I2: ComputeLeaseIP: subnet result: 0xc0a8ebfe
2021-02-17T15:16:54.965+03:00| inst-build-17198959| I2: ComputeLeaseIP: Computed subnet DHCP range end addr: 192.168.235.254
2021-02-17T15:16:54.965+03:00| inst-build-17198959| I2: VNL_GetNumberOfVnets: number of vnets: 20
2021-02-17T15:16:54.966+03:00| inst-build-17198959| E2: VNLStartupCOM: security specification failed since already set (ignoring)
2021-02-17T15:16:54.966+03:00| inst-build-17198959| I2: ProcessSpecificHostAdapter: finished with COM initialization (attempt)
2021-02-17T15:16:54.966+03:00| inst-build-17198959| I2: WMI_ConnectToWMI: Connecting to WMI server
2021-02-17T15:16:54.968+03:00| inst-build-17198959| I2: WMI_ConnectToWMI: Connected to WMI server
2021-02-17T15:16:54.968+03:00| inst-build-17198959| I2: AdjustSecurity: security query success
2021-02-17T15:16:54.968+03:00| inst-build-17198959| I2: AdjustSecurity: authn 0x0000000a authz 0x00000000
2021-02-17T15:16:54.968+03:00| inst-build-17198959| I2: AdjustSecurity: servername NT AUTHORITY\SYSTEM
2021-02-17T15:16:54.968+03:00| inst-build-17198959| I2: AdjustSecurity: authLev 0x00000006 imp 0x00000003
2021-02-17T15:16:54.968+03:00| inst-build-17198959| I2: AdjustSecurity: authInfo 0x00000000 capabilities 0x00000041
2021-02-17T15:16:55.018+03:00| inst-build-17198959| I2: ProcessSpecificHostAdapter: next enumerator returned: 0x00000001
2021-02-17T15:16:55.018+03:00| inst-build-17198959| I2: ProcessSpecificHostAdapter: Next() returned 14 items
2021-02-17T15:16:55.018+03:00| inst-build-17198959| E2: ProcessSpecificHostAdapter: descriptions don't match at character 0
2021-02-17T15:16:55.018+03:00| inst-build-17198959| I2: ProcessSpecificHostAdapter: at end of loop
2021-02-17T15:16:55.018+03:00| inst-build-17198959| E2: ProcessSpecificHostAdapter: descriptions don't match at character 0
2021-02-17T15:16:55.018+03:00| inst-build-17198959| I2: ProcessSpecificHostAdapter: at end of loop
2021-02-17T15:16:55.018+03:00| inst-build-17198959| E2: ProcessSpecificHostAdapter: descriptions don't match at character 0
2021-02-17T15:16:55.018+03:00| inst-build-17198959| I2: ProcessSpecificHostAdapter: at end of loop
2021-02-17T15:16:55.018+03:00| inst-build-17198959| E2: ProcessSpecificHostAdapter: descriptions don't match at character 0
2021-02-17T15:16:55.018+03:00| inst-build-17198959| I2: ProcessSpecificHostAdapter: at end of loop
2021-02-17T15:16:55.018+03:00| inst-build-17198959| E2: ProcessSpecificHostAdapter: descriptions don't match at character 0
2021-02-17T15:16:55.018+03:00| inst-build-17198959| I2: ProcessSpecificHostAdapter: at end of loop
2021-02-17T15:16:55.018+03:00| inst-build-17198959| E2: ProcessSpecificHostAdapter: descriptions don't match at character 0
2021-02-17T15:16:55.018+03:00| inst-build-17198959| I2: ProcessSpecificHostAdapter: at end of loop
2021-02-17T15:16:55.018+03:00| inst-build-17198959| E2: ProcessSpecificHostAdapter: descriptions don't match at character 0
2021-02-17T15:16:55.019+03:00| inst-build-17198959| I2: ProcessSpecificHostAdapter: at end of loop
2021-02-17T15:16:55.019+03:00| inst-build-17198959| E2: ProcessSpecificHostAdapter: descriptions don't match at character 0
2021-02-17T15:16:55.019+03:00| inst-build-17198959| I2: ProcessSpecificHostAdapter: at end of loop
2021-02-17T15:16:55.019+03:00| inst-build-17198959| E2: ProcessSpecificHostAdapter: descriptions don't match at character 0
2021-02-17T15:16:55.019+03:00| inst-build-17198959| I2: ProcessSpecificHostAdapter: at end of loop
2021-02-17T15:16:55.019+03:00| inst-build-17198959| E2: ProcessSpecificHostAdapter: descriptions don't match at character 0
2021-02-17T15:16:55.019+03:00| inst-build-17198959| I2: ProcessSpecificHostAdapter: at end of loop
2021-02-17T15:16:55.019+03:00| inst-build-17198959| E2: ProcessSpecificHostAdapter: descriptions don't match at character 0
2021-02-17T15:16:55.019+03:00| inst-build-17198959| I2: ProcessSpecificHostAdapter: at end of loop
2021-02-17T15:16:55.019+03:00| inst-build-17198959| E2: ProcessSpecificHostAdapter: descriptions don't match at character 0
2021-02-17T15:16:55.019+03:00| inst-build-17198959| I2: ProcessSpecificHostAdapter: at end of loop
2021-02-17T15:16:55.019+03:00| inst-build-17198959| E2: ProcessSpecificHostAdapter: descriptions don't match at character 0
2021-02-17T15:16:55.019+03:00| inst-build-17198959| I2: ProcessSpecificHostAdapter: at end of loop
2021-02-17T15:16:55.019+03:00| inst-build-17198959| E2: ProcessSpecificHostAdapter: descriptions don't match at character 0
2021-02-17T15:16:55.019+03:00| inst-build-17198959| I2: ProcessSpecificHostAdapter: at end of loop
2021-02-17T15:16:55.020+03:00| inst-build-17198959| I2: ProcessSpecificHostAdapter: next enumerator returned: 0x00000001
2021-02-17T15:16:55.020+03:00| inst-build-17198959| I2: ProcessSpecificHostAdapter: all network cards properly enumerated

 

can you understand this

0 Kudos