Error 0x000000bcb when installing a shared printer
Good morning,
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.
-
I did encounter something like this on a customer's site a little while ago but it was only on certain of the client PC, others worked correctly. We never managed to find out why.
I believe we got it to work by installing the driver on the PC first, linked to a local port (I think we used LPT1 even though that didn't physically exist), and then installed the shared driver from the network.
0 -
I managed to work around the issue by manually installing the driver using the client's Print Management console before connecting to the shared printer; this way, the client uses the pre-installed driver instead of trying to download it from the server.
0 -
Similar to the way we did it then.
0 -
Another trick you can use it's install the printer using that "The printer that I want isn't listed" option. For whatever reason, it works smoothly and no error is encountered.
0 -
Installing the printer directly ("add a printer using an IP address or hostname") works, yes, but not installing it as a shared printer. Besides, with about 300 label printers and several thousand clients in our region, installing each printer by hand is not really an option ;). That's what the directory is for.
0
Vous devez vous connecter pour laisser un commentaire.
Commentaires
5 commentaires