Hello, these are the march 2026 Release Notes of NDD Print, we have a lot of news, and we hope you like it.
Here you can download the latest versions.
See a summary of all updates and click on the links to navigate each one.
NDD Print MF HP - 5.31.4
IMPROVEMENTS
FIXES
NDD Print MF Brother - 5.12.1
fixes
-
Error when using special character “&” in AD password in Scan to Folder
-
Insecure release in environments without hostname resolution
-
Incorrect call to NDD Print Releaser on printers configured with authentication only
NDD Print MF HP - 5.31.4
Released on March 4, 2026
Improvements
Postgres version update
What is the objective?
To update Postgres to fix failures in previous versions.
What has been done?
Postgres has been updated to version 17.9.1.
Corrections
Loop on the authentication screen when no printer is found (PrinterNotFoundException)
How did the problem happen?
Authentication could not find the printer (PrinterNotFoundException) and the user was repeatedly redirected to the error screen.
When did the problem occur?
When the request arrived with the IP address of an internal/local adapter on the machine itself (not exactly 127.0.0.1 or : (line 1)), especially in a scenario where the host/address was different from the one configured.
Where did the problem happen?
On the authentication screen.
What was done to fix it?
Local IP detection for internal adapters has been added, and the local treatment condition now also considers these local IPs. As a result, internal addresses are now processed as local hosts in the flow, preventing printer identification failures and breaking the loop to the error screen.
NDD Print MF Brother - 5.12.1
Released on March 2, 2026
Fixes
Error when using special character “&” in AD password in Scan to Folder
How did the problem happen?
When the special character “&” was included in the Active Directory (AD) user password, specifically in the user configured in Tools > Settings > Scan Configuration > Storage Server Authentication, sending the XML generated during the process resulted in an error, preventing the operation from continuing and displaying the failure screen.
When did the problem occur?
When accessing Scan to Folder, a function active and configured in NDD Print Host.
What was done to fix it?
A fix was implemented that ensures that special characters in XML are properly escaped once at the entry point, preventing the generation of invalid XML.
Insecure release in environments without hostname resolution
How did the problem happen?
In environments without hostname resolution, when performing releases on equipment with the application installed (with the authentication URLs and NDD Print Releaser registered on the equipment/BSI) but which was not registered in the NDD Print MF Brother XML, the release was executed on the printer used by the user, but the job was printed on another printer.
When did the problem occur?
The problem occurred when the equipment was turned off or removed from the network and subsequently removed from NDD Print MF Brother. In this situation, the authentication and NDD Print Releaser URLs were not removed from the equipment. Thus, when reconnected to the network, the equipment continued to authenticate and allow secure release as normal.
However, as the equipment was no longer listed in the NDD Print MF Brother XML and there was no hostname resolution, the system directed the release to the first printer listed in the XML, resulting in printing on an incorrect device.
Where did the problem happen?
In the XML Printers of NDD Print MF Brother.
What was done to fix it?
A validation has been implemented to check whether the printer is registered in the NDD Print MF Brother database. If the equipment is not registered, the system displays a message to the user informing them that the printer is not registered in NDD Print MF Brother.
Incorrect call to NDD Print Releaser on printers configured with authentication only
How did the problem happen?
When performing authentication on the printer panel, on equipment configured with authentication only, and without the NDD Print Releaser module installed on the server, the system still made a call to NDD Print Releaser, even when the NDD Print Releaser option was disabled on the printer.
When did the problem occur?
The problem occurred during the authentication attempt on the printer panel. On equipment that only had authentication, the NDD Print Releaser address remained configured locally, and the NDD Print Releaser module was not installed on the server with NDD Print MF Brother Admin.
Where did the problem happen?
When attempting authentication on the equipment:
What was done to fix it?
The code logic has been adjusted to first check whether the NDD Print Releaser option is active on the printer (isReleaser) before making any calls to the module. This way, the call is only made when really necessary.