BugZero | Citrix NetScaler BugID NSLINUX-8109 - When adding a new load balancing user monitor, Net...

Citrix NetScaler - Defect ID: NSLINUX-8109

When adding a new load balancing user monitor, NetScaler accepts a custom dispatcher IP during configuration. However, it always displays the default dispatcher IP address (192.0.0.2) in the monitor details, regardless of which IP address is actually configured.

Citrix NetScaler - Defect ID: NSLINUX-8109

When adding a new load balancing user monitor, NetScaler accepts a custom dispatcher IP during configuration. However, it always displays the default dispatcher IP address (192.0.0.2) in the monitor details, regardless of which IP address is actually configured.

Last updated on April 28th, 2026

BugZero Risk Score
0.0 Coming soon

Overall: N/A

Severity: N/A

Community: N/A

Lifecycle: N/A

What is the BugZero Risk Score?

Citrix NetScaler Integration

Learn more about where this data comes from

Citrix NetScaler Integration

Learn more

BugZero Plan

Streamline upgrades with automated vendor bug scrubs

BugZero Plan

Learn more

BugZero Prevent

Wish you caught this bug sooner? Get proactive today.

BugZero Prevent

Learn more

Bug Details

Status: Fixed
Views: 1

Description

The vendor has published 1 unique mention(s) for this bug: 1. When adding a new load balancing user monitor, NetScaler accepts a custom dispatcher IP during configuration. However, it always displays the default dispatcher IP address (192.0.0.2) in the monitor details, regardless of which IP address is actually configured. Modules: 1. Platform Latest urls for this bug: 1. https://docs.netscaler.com/en-us/updates?product=NetScaler%20ADC%20%28includes%20NetScaler%20Gateway%29&version=14.1&build=51.80

Change history

2026-04-28 Added: 14.1 Build 51.80

2026-04-28 Removed: Build 14.1-51.80

2025-10-22 Removed: Build 14.1-51.72

2025-09-29 Added: Build 14.1-51.80

2025-09-11 Added: Build 14.1-51.72

Top Citrix NetScaler Defects

Defect ID: NSHELP-42609
The NetScaler packet engine might crash due to a defect in backend TLS 1.3 connection state handling during teardown. On NetScaler SDX platforms with multiple instances, a crash in one instance can also affect other instances sharing the same crypto hardware.
Defect ID: NSHELP-41518
Client requests might fail if HTTP/2 header values contain space characters. These spaces can trigger header frame processing errors, particularly when the client sends improperly formatted header values.
Defect ID: NSBASE-19568
When the server-side TCP window reaches a 2 GB limit, the gRPC hold logic incorrectly opens the TCP window twice for held bytes, resulting in a zero window advertisement. This issue also includes incorrect accounting of chunk header and trailer bytes before they are passed to the application handler, affecting TCP window management and data transmission.
Defect ID: NSHELP-42103
Pitboss logs might sometimes flood ns.log when the SSLVPN or IC feature is enabled and cache memory is set to 492 MB, specifically when the number of NetScaler packet engines is 4 or 5.
Defect ID: NSUI-22553
Administrators cannot view or manage profile configurations in the NetScaler 14.1 GUI when accessing System > Profiles in admin partition. This action returns an "Operation not permitted" error.

Ready to prevent the next vendor outage?

Get a demo

Citrix NetScaler - Defect ID: NSLINUX-8109

When adding a new load balancing user monitor, NetScaler accepts a custom dispatcher IP during configuration. However, it always displays the default dispatcher IP address (192.0.0.2) in the monitor details, regardless of which IP address is actually configured.

Citrix NetScaler - Defect ID: NSLINUX-8109

When adding a new load balancing user monitor, NetScaler accepts a custom dispatcher IP during configuration. However, it always displays the default dispatcher IP address (192.0.0.2) in the monitor details, regardless of which IP address is actually configured.

Last updated on April 28th, 2026

BugZero Risk Score0.0 Coming soon

Bug Details

Links

Top Citrix NetScaler Defects

Ready to prevent the next vendor outage?

BugZero Risk Score
0.0 Coming soon