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

Horizon Blast Extreme Adaptive Transport and S4B uses same ports (52558)

Last Updated: 10/2/2023Categories: TroubleshootingTotal Views: 7579Language:
English

2 like this article

Subscribe to get an email
newsletter with new updates

2 people found this helpful Please provide article feedback:

Symptoms

When using Skype for Business, the video or screen sharing may not be displayed if Skype for Business and Horizon BEAT blast protocol are trying to use the same video ports.

Cause

By default, Horizon BEAT reserves some ports starting from ephemeral port range 49152-65535.
If Skype for Business servers are configured to use these same ports, the ports will not be available to the SFB Client on the Remote Desktop.

Resolution

If any third party application uses the same port as Horizon BEAT then see the workaround section.

Workaround

When installing, configure View Agent to use ports that are different than the Skype for Business client media port range. The media (audio, video and presentation) port range is configured on the Skype for Business server and is used by the SfB Client. Use the View Agent command line installer and pass the flags of BLAST_UDP_STARTING_PORT and BLAST_UDP_PORT_RANGE to select an alternate port range.

If you would like to confirm which ports are reserved by Horizon BEAT on the Remote Desktop, refer to the values in
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\vmwvudpd registry.

For example:

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\vmwvudpd]

UdpBeatSideChannelNumPorts 16
UdpBeatSideChannelStartPorts 49168 49184 49200
UdpNumPorts 16
UdpPortStart 49152

In the above case, Horizon BEAT reserves totally 64 ports between 49152 and 49215.

Related Information

VMware Horizon TCP and UDP Ports

Page last reviewed: June 2023
Next review due: September 2023

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
vSAN 6.5 以降のカスタム証明書の問題 (52567)

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

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 Horizon

Related Versions:

VMware Horizon 8

VMware Horizon 7 version 7.3.x

VMware Horizon 7

Take Our Survey

Support Assistant