I have four Windows print servers using Seagull drivers for Intermec, Zebra and Citizen label printers in my region; two using old 7.3.x drivers and two servers using the current 2022 one.
When I try to install a shared printer on a client, I get a notification "looking for driver" and a prompt to enter an admin authorization (which is the intended behavior). From the two servers using old drivers, the installation of both driver and printer then proceeds normally. From the "up to date" servers, however, I receive the aforementioned error "0x000000bcb Windows cannot connect to the printer".
With drivers from other manufacturers (Kyocera, Lexmark, Zebra), there aren't any issues. Only Seagull driver >= 7.4.x are affected.
I already tried to manually install the root and Seagull certificate on a test workstation as per this article (Installing Authenticode signature prior to Seagull Driver installation – BarTender Support Portal (seagullscientific.com) without success.
The server settings\GPOs\network rules etc. are identical for all four machines (VMs deployed from a default template), the only difference is the driver version. All relevant MS patches, especially those related to the Print Nightmare exploit, are installed, of course.
Downgrading the driver from 2022 to 7.3 works, but I'm not exactly happy using an outdated driver (the entire issue came up when I updated the drivers on two servers and users started complaining that they can't install their printers anymore)
I'm out of idea here.
Please sign in to leave a comment.