Hey folks, I threw this document together for the techs in our office as a shortcut to test the print function of an mfp in the field. It is mostly meant for the techs that aren't really network savvy and have a difficulty/fear configuring a print driver. It's also a good way to bypass the print driver and confirm whether or not there is a problem with the controller.
Quick test print using telnet
Collapse
X
-
Tags: None
-
Re: Quick test print using telnet
Hey folks, I threw this document together for the techs in our office as a shortcut to test the print function of an mfp in the field. It is mostly meant for the techs that aren't really network savvy and have a difficulty/fear configuring a print driver. It's also a good way to bypass the print driver and confirm whether or not there is a problem with the controller.Mystic Crystal Revelations -
Re: Quick test print using telnet
Hey folks, I threw this document together for the techs in our office as a shortcut to test the print function of an mfp in the field. It is mostly meant for the techs that aren't really network savvy and have a difficulty/fear configuring a print driver. It's also a good way to bypass the print driver and confirm whether or not there is a problem with the controller.
Good post."You can't trust your eyes, if your mind is out of focus" --Comment
-
Comment
-
Re: Quick test print using telnet
UPDATE-
When I dragged and dropped a text file into the telnet window and close it, all it prints is the path to the document. Is there some other method to accomplish this?Last edited by teebee1234; 12-27-2013, 05:51 PM.Comment
-
Mystic Crystal RevelationsComment
-
Re: Quick test print using telnet
Excellent, I'll update that in there. Does it keep the formatting on dropped in files or just print plain text?
UPDATE-
When I dragged and dropped a text file into the telnet window and close it, all it prints is the path to the document. Is there some other method to accomplish this?
oops, sorry for that, was mistaking with FTP printing.
You can drag and drop a file in the box when printing with an FTP command.Comment
-
Re: Quick test print using telnet
I like the fact that you don't need a driver to print.
This is my preferred method:
Another way to just as quickly do a test print is using LPR Jar, and a print-to-file .PRN file.
You can download LPR Jar here: http://gccprinters.com/support/doc/lprutil.html
This can be as simple or as complex as you want to make it: Using whatever document, whatever emulation you'd like to use, print-to-file then name the document something you can remember. My most used document is a CS-8030 printer test page in PCL XL. The application can be run from a laptop or just a USB memory stick plugged into an endusers computer.
Open the app, enter the recipient printer's IP address, browse to the .PRN file, and Send.
(Naturally you'll want to select an emulation that your printer can recognize. Also Kyocera/Copystar equipment has a few coding differences in the initial lines of the print-to-file, so I've got files for Kyocera equipment and then files for all other manufacturers, monochrome images and color images, anything you want.) If you want to get really crazy, you can edit the file to include any advanced functions like booklet making, stapling, tray selection, job accounting, or any combination.
You can do the same thing from the Command Prompt screen:
C:\Documents and Settings:\blackcat4866>copy filename.prn \\fullcomputernamelessdomain\printersharename
filename.prn is your print-to-file, located in the root (C:\ drive)
fullcomputernamelessdomain is the full computer name of the server where the driver is located (you can also use the IP address of the server)
printersharename is the printer share name
Another option is the GX4PEK Printer Tester app.
It generates some interesting test images, but needs an installed print driver.
Usually I'm looking for more than a basic print test. I'd like some image quality to look at.
=^..^=Last edited by blackcat4866; 12-28-2013, 04:03 PM.If you'd like a serious answer to your request:
1) demonstrate that you've read the manual
2) demonstrate that you made some attempt to fix it.
3) if you're going to ask about jams include the jam code.
4) if you're going to ask about an error code include the error code.
5) You are the person onsite. Only you can make observations.
blackcat: Master Of The Obvious =^..^=Comment
Comment