We've recently moved our Millennium system to a III hosted server. Network system printing (where the server prints directly to an HP printer via Jetdirect on port 9100) will not work with a hosted system. We can select a local (or attached) printer in any Millennium client, but not when using a character based SSH connection such as PuTTy or BitVise.
Is there a way for us to print from character based in this new environment?
When we migrated to a hosted system, I edited the SSH logins to limit the available printers to "Attached Laser Printer", "File Save", and "Email Printer." I advised staff that their printer of choice going forward would need to be the same as the default printer on their PC. Millennium users were virtually unaffected by the change. We had about 30 SSH users, but only three or four had printing needs (chiefly billing staff).
If I remember correctly, the SSH users were unable to print after the migration. I added printer choices back to their SSH logins and all was well.
In other words, we are still able to use the network printers for some applications, while in other cases, network printing would absolutely not work (Millennium notices, I think). I had been very concerned about the "no more network printing" warning, but it turned out to mostly be a non-issue.
In short, we are hosted and can still print from the character-based system. I had not asked for any firewall changes (but we were a iii customer pre-Millennium, so maybe that change had been done in the past?). It could be I am just ignorant of the finer points regarding network printers...
You would have to convince III to allow traffic on port 9100 through the hosted server's firewall, and you have to convince your campus IT department to let traffic on port 9100 through to the designated printer from your hosted server's IP address.
If our campus is any indication, that latter part is the hardest bit.
