A couple of months back, I added to a C”losed” thread, This sounds like my problem as well.”
It is now trime to tell my own story from the beginning.
During the COVID lockdown, there was only one printer model available, an Epson ECO-Tank MFC. In a Windows-only setting, it would probably have been quite adequate, but officially, it had never heard of Linux. There was a Linux driver available, in either RPM or .deb format, but it had other limitations. When it started sounding like a concrete mixer and the Readcy light wouldn’t light, I bought a Brother MFC-4440DW multifunction inkjet. Om its own network, it is an MFC-J4440DW_BR3603. The MFC-J series do not exist on my CUPS database.
It wouldn’t print. A troubleshooter said that the server could not broadcast to the printer. That was easily fixed, but it didn’t help. I downloaded the Mopria app on my phone. It said that the network was unreachable, but a JetDirect connection, a completely different animal would work. Naturally, it didn’t.
I found a very useful thread on Server_Fault, a board of Stack Exchange. It was 11 years old, from the days of Windows XP, but it was basic. Both were sysadmins. The inquirer had an in-house network driven by CentOS7. It had an assortment of printers throughout the building, swome specialized. He asked whether he needed a dedicated print server. The other party said “NO” and told him how to set up everything on the CentOS machine. Flor my purposes, he gave 2 sample configurations, one for an XP printer using Samba, and one for a Linux printer on the CUPS network. The Linux example should work for me, but I probably have a syntax error.