OPERATIONAL DEFECT DATABASE
...
...
After disabling the SMBv1 on domain controllers, ESXi Domain joining fails with an error similar to: STATUS_INVALID_NETWORK_RESPONSE In the /var/log/likewise.log, you see the entries similar to: 20170728181606:DEBUG:lwio:RdrResolveToDomain():driver.c:889: Error at ../lwio/server/rdr/driver.c:889 [status: STATUS_NOT_FOUND = 0xC0000225 (-1073741275)]20170728181606:TRACE:netlogon-ipc:lwmsg_peer_log_message():peer-task.c:212: (assoc:0xa602240 >> 75) CALL REQ LWNET_Q_RESOLVE_NAME: { pwszHostName = "ADC1.test.local" }20170728181606:TRACE:netlogon-ipc:lwmsg_peer_log_message():peer-task.c:212: (assoc:0xa602240 >> 75) CALL RES LWNET_R_RESOLVE_NAME: { pwszCanonName = "ADC1.test.local" dwAddressListLen = 1 ppAddressList = { { AddressType = LWNET_IP_ADDR_V4 Address = <arm:Ip4Addr> { 192 168 200 20 } } } }20170728181606:DEBUG:lwio:RdrSocketTaskConnect():socket.c:1019: Error at ../lwio/server/rdr/socket.c:1019 [status: STATUS_PENDING = 0x00000103 (259)]20170728181606:DEBUG:lwio:RdrSocketTask():socket.c:1246: Error at ../lwio/server/rdr/socket.c:1246 [status: STATUS_PENDING = 0x00000103 (259)]20170728181606:DEBUG:lwio:RdrSocketRead():socket.c:1773: Error at ../lwio/server/rdr/socket.c:1773 [status: STATUS_PENDING = 0x00000103 (259)]20170728181606:DEBUG:lwio:RdrSocketReceivePacket():socket.c:701: Error at ../lwio/server/rdr/socket.c:701 [status: STATUS_PENDING = 0x00000103 (259)]20170728181606:DEBUG:lwio:RdrSocketDispatchPacket2():socket.c:1423: Error at ../lwio/server/rdr/socket.c:1423 [status: STATUS_INVALID_NETWORK_RESPONSE = 0xC00000C3 (-1073741629)]20170728181606:DEBUG:lwio:RdrSocketTaskTransceive():socket.c:1134: Error at ../lwio/server/rdr/socket.c:1134 [status: STATUS_INVALID_NETWORK_RESPONSE = 0xC00000C3 (-1073741629)]20170728181606:DEBUG:lwio:RdrSocketTask():socket.c:1251: Error at ../lwio/server/rdr/socket.c:1251 [status: STATUS_INVALID_NETWORK_RESPONSE = 0xC00000C3 (-1073741629)] Note: The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment.
This issue occurs if SMBv2 is enabled on an ESXi host and SMBv1 is disabled on Active Directory.
This is a known issue affecting VMware ESXi 6.5.This issue is resolved in VMware ESXi 6.5, Patch Release ESXi650-201712001, available at VMware Patch Downloads.For more information on downloading patch, see How to download patches in Customer Connect (1021623).For more information, VMware ESXi 6.5, Patch Release ESXi650-201712401-BG: Updates esx-base, esx-tboot, vsan, and vsanhealth VIBs (2151104)
Click on a version to see all relevant bugs
VMware Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.
