Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

ESXi domain join fails when SMBv1 is disabled on the domain controller or a firewall is blocking SMB negotiate packets (67033)

Last Updated: 3/20/2024Categories: TroubleshootingTotal Views: 10260Language:
Chinese (Simplified)English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

An ESXi host may fail to join an Active Directory domain when the SMBv1 protocol is disabled on the domain controller or when a firewall is blocking SMB negotiate packets.

Cause

SMB2 is supported on ESXi 6.5 Update 1 onward but the initial SMB packet negotiation request begins over SMB1 packet. If SMB2 is enabled on both Active Directory controller and the ESXi host then the negotiation switches to SMB2 otherwise it negotiates through SMB1packets only.

If SMB1 is disabled on the domain controller then it would prevent the initial packet negotiation, thus causing packet drops and eventually failure with an error similar to ERROR_GEN_FAILURE.

A firewall that is configured to block SMB negotiate packets may also cause this issue but will send a RST packet. To confirm, perform a packet capture during join:

# tcpdump-uw -n -i vmk0 -w join.pcap

Use a wireshark filter 'tcp.port==445' to observe the SMB negotiate protocol packet and RST from the destination:

128 Negotiate Protocol Request

Requested Dialects
NT LM 0.12
SMB 2.002

60 445->22553 [RST] Seq=1 Win=1 Len=1

Note, numerous attempts to re-transmit indicates that the destination is not acknowledging or responding to the SMB negotiate protocol packet.

Resolution

This issue is resolved in ESXi 6.7 Update 2 where the initial packet negotiation will begin via SMB2 by default instead of SMB1, thus disabling SMB1 completely.

Workaround

Disable any firewall rules blocking SMB negotiate packet. Note, ensure to enable firewall rules on esxi and firewalls between esxi host and domain controllers.

For more information on ports that need to be opened, see "Errors in Active Directory operations" error adding the ESX/ESXi host to an Active Directory domain (1026538)"

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)English

Attachments

Additional Resources

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

KB
•
Download and Install VMware Fusion (2014097)

Results 1-2 of 2

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vSphere ESXi

Related Versions:

VMware vSphere ESXi 6.7

VMware vSphere ESXi 6.5

Take Our Survey

Support Assistant