Yosemite OSX Server 4, pushed printers show as 'not connected'

Question

I am using a Mac Mini on Yosemite with Server 4 primarily as a profile server.  It's pushing out two printers to clients, both Ricoh MP 3503's with the latest drivers.  Clients receiving the printers from the profile server get "Printer not connected" when printing to them.  When you add the printer locally, either by IP or as a managed printer on the server, clients can print just fine.
The printers and server are in the same subnet but clients are in another.  You can discover the printers through the Mac Mini server, or by adding them by IP and again, printing is just fine.  If the printer is added through the profile server, you get 'Printer not connected", something about adding them from the client vs. pushed through a profile is affecting whether or not the client can see the printer.
I've tried resetting the printer system locally and on the server, verifying reachability between the client and printers, adjusting the domain on the printers so they're in the same domain as the clients.

Answer 1

A lot to check for!
All my users are "Local Network Users" setup in what is now Server 4.03 (as of a few days ago), not Local Users.
Ours are Local Users - but I would argue strongly against this being a factor.
My usergroup is also a "Local Network Group", not a Local Group.
Ours are Local User Groups - but I would argue strongly against this being a factor.
I believe you can print from your server as your clients can when the server is sharing - but just to ask, can you print from the server?
You are correct.  I can print directly to the printer, or I can print through/on the server without any problems.  Yes, I can print from the server.  Both as a client that's added the server's shared printer or as a local user on the server.
Under Sharing menu in System Preferences on the Server, is Printer Sharing OFF (it is off for me).
No, it is on.  Presently, the server is sharing out the printers for discovery because clients are in a different subnet.  They cannot discover the printers on their own.  The printer has an IP in both the printer subnet and the client subnet.
We use the Mac Server for DNS and DHCP, so that printer is statically assigned on the server, just sayin'.
With all I've heard about DNS, I was thinking hard on this but I don't think it's a factor.  We use a Windows 2012 server for DHCP and DNS.
Take a look at this screenshot below - it is of my Profile Manager where that printer "Fiery" works fine passing to the clients.
Yes, what about it?
Could it be a router port problem? On our router, an Airport Extreme, we have opened up Printer Sharing ports, see screenshot below.
No, because we don't segment our network.  I can add the printer directly to my client machine and print to it without issue - I just can't discover it because I'm in a different subnet then the printer.  The server acts as an intermediary, I can discover the server's shared printers because the server is in the same subnet as me.
On my Printer Options - I will open a thread, it is just that you had some experience and I wanted to hear about it and I may not have under another thread (you would have no reason to have looked for it). Anyway, I will open a thread, thanks for letting me know your experience with "Options"!
I appreciate it!  I'm just trying to keep a convoluted problem as clear as possible.  I am nearly positive your issue has to do with the printer driver you have installed on the server.  The clients get the driver from the server, we used to have ours show up as 'generic printer', but then downloaded a different type of driver, PS is generic, PCL6 showed up as specific.