We are seeing horrendous driver install and printer use when trying to use 2023.4 drivers via our printer server. I'm unsure exactly how we got to this point.

Earlier this month we were "working fine" with 2023.2 version. We were running all Datamax Mark III printers at this point. At some point I attempted to add a new brand of printer (Zebra) and downloaded 2023.4.  I thought I had it working after a couple of girations and eventually installing 2023.2 Datamax drivers again and removing the Zebra printers. After a period of a few days of 'stability'. I retried the DriverWizard to update the 2023.2 Datamax drivers to 2023.4 and then used the Zebra DriverWizard to install the 2023.4 Zebra drivers.

We are using these printers with Bartender but also have end users directly connected to the printers to support ad-hoc highly "formatted" labels.  
Almost consistently attempting to add a printer using that utilizes the Seagull drivers from the print server (using "Printers & Scanners") returns an error message. Restarting the computer and then re-trying the addition completes successfully.  I might be able to avoid restarting the computer by restarting the print spooler service on the client computer. 
Once the printer is added trying to print to this successfully added printer results in a significant delay on selecting the printer and it's questionable if the print job will ever actually goes through. 

I have bi-directional support turned off on the Zebra's but it's enabled on the Datamaxes (as it was already enabled when working previously). I've not "made" any changes to the Datamax printers.

As best I can tell BarTender itself has no issues, it is installed on the PrintServer itself.

When I tried calling support when this originally began the agent's stated position was that they don't support print servers. 

I feel like this is something stupid that I'm missing because this is not the world I live in all the time, but I'm at a loss for what it is.

The print server is 2019 (v1809) and is mostly up-to date. Maybe a month behind on Windows updates.

On my client I'm getting this warning about ever 20 seconds:

The description for Event ID 512 from source Seagull TCP Library V3 cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event: 

splwow64.exe: TCPSocketWithReUse::Connect: SocketException occurred. ID: 0x0000000007322150, Host:<printServer>.local, Port: 5130 Error: 0x0000274C A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
 Retries: 0

The message resource is present but the message was not found in the message table