One of the problems I have in the classrooms with these printers is that someone will send a print job to the printer but because the job is mis-configured, it wiill not print. Then the user logs off but does not cancel the print job. That can block the printer from printing for any following user.
When that happens, the only reliabkle way that I have found is to kill ALL the print jobs, no matter which user submitted them. Then I restart the printer and, ususlly, the computer allso. That will seem to bring the printer back to working correctly. The actual problem description may be "Printer Paused", "Communication Error" or a few other errors.
To kill ALL the print jobs, log in as admin, open Applications/Utilities/Terminal and enter the following command"
"sudo cancel -a" without the quotes.
Enter your password and let the computer completly empty the prinrter queue. Please be aware that this command will kill all the jobs for ALL printers connected to that computer and not just the 2400.
Then I restart the printer and it comes back on-line and ready. If the printer is fed from a network or is a shered printer and has multiple computers sending it print jobs, you will have to kill the print jobs on all computers that may send a job to that printer just to catch the one bad job that is plugging up the system.
If that fails, you may have to reinstall the print driver and then the printer.