Oh by the way - that persistent 'There is a job printing now (35)' message yesterday.
I finally figured out why that was. It was because the printer was attempting to send a printing request (the test print) to the Printer Spooler Queue, but during the installation, we had not assigned a port or told Windows how the printer was connected, and thus it was stuck in a loop of not being able to complete the printing.
Now that your Windows OS can see the printer, that error ought not reappear unless some random connection issue with printer pops up, in which case you can simply go to Control Panel | select Printers & Devices | click the Ricoh printer icon, and delete pending printing from the queue.