Re: network printer is ready but error when printing
- From: "mixty" <here@xxxxxxxxx>
- Date: Mon, 15 Dec 2008 12:44:26 +0800
Thanks so much for your clear description. I will ensure we won't do any of those mistakes.
After a sleepless night of research, and thanks (really!) to everybody's help here and elsewhere, I want to post my refined questions before I go to work.
Let me state again that it is a network printer directly connected to a Windows Server (not shared to client PC yet since we're at testing stage, so I think it is not related to RPC/SMB ports)
I've found some ways to troubleshoot network printing issues. Please correct me if there's something else we should do.
1) [Firewall issue] If the driver's fine, maybe the communication between Windows and the network printer is blocked. I was looking for the listening port for TCP/IP network printers to telnet/netcat to. It should be 515 (network printer should use LPD/LPR implementation), yet I'm confused HP JetDirect and others seem to use 9100 or others as listening port (informed by a web page below).
http://members.cruzio.com/~jeffl/sco/lp/printservers.htm
PS: I wish to have a way to reproduce this problem and test it at home but could not... there's no such thing as virtual IP printer. I only found a Virtual Printer at best.
3) [Do a lowest-level test print] I'd like a method (maybe command) to print directly to the printer by IP rather than first setting it up. Something like "dir > IP_192.168.0.123" would go to printer directly at the lowest possible level to eliminate any other causes.
Then I found that it can't be done without first sharing the printer (that means passing though RPC/SMB, not lowest-level):
a) Remapping printer to LPTx by "net use LPTx \\host\share" and printing with "copy abc.ps LPTx /b".
b) print /d:IP_192.168.1.123 c:\abc.txt (no response, unless again first sharing it - print /d:\\192.168.1.133\Canon1 c:\temp.txt)
Later I found some more ways that works without sharing:
i) 'Enable printer pooling' for both LPTx and IP_192.168.1.123 ports. Then printing to LPTx by the copy command would go to the IP port.
ii) LPR command seem to do it the lowest level as the name suggests?
LPR -S 192.168.1.133 -P "Canon MP988" -o c:\abc.ps
iii) Or, simply setting up the printer by Standard TCP/IP and do a "Print Test Page" in the printer properties would be low level enough?
(by 'works' I mean it gives response, errors are still there tho)
3) [Confirm driver is working by examining the raw output] First print to file using "Keep printed documents" or "FILE:" port with the Canon driver, then use PCLReader / PostScript viewer (GSView) to view the raw printout to check if it is the driver that makes bad printouts that causes the error.
However, during the test of both programs using another working Canon printer, both PCLReader and PS viewer (GSView) can't decode the file but show weid codes. I went on and checked a .pcl file printed by a HP printer. It works tho. What could be the issue here? Isn't the Canon using either PCL or PS?
"Lanwench [MVP - Exchange]" <lanwench@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> 在郵件張貼內容主旨 uR6rqbfXJHA.6000@xxxxxxxxxxxxxxxxxxxx 中撰寫...
mixty <here@xxxxxxxxx> wrote:.Hi there.
We've set up a Canon MP988 network printer (connected to router) in
the printer server (running Windows Server) of a company。We can see
its status is ready, which I suppose should mean the driver has been
properly installed and everything is OK, even its management web page
can be accessed fine. However, it gives error when printing.
What could be the cause?
Sorry for sounding newbie-ish, but I would really like to know the
ports the network printer uses for sharing, as I want to telnet to
the port to see if there's anything (e.g. strict firewall rules) that
is blocking the communication between the network printer and the
Windows server.
If that path is not blocked, then maybe we need to send the printer to
repair; if the path is blocked, then it should be firewall, correct?
"How Network Printing Works"
http://technet.microsoft.com/en-us/library/cc783789.aspx#w2k3tr_prntt_how_fxbi
I checked this Technet article for the ports I need but I really lack
this knowledge. Is this what should be tested? Port 9100 for
"Standard TCP/IP port monitor" (RAW)"
I don't think it is about SMB / RPC ports as the network printer is a
Windows OS. Am I wrong in saying so?
Thanks and sorry for my ignorance.
mixty
I'm confused as to your mentioning "connected to router" or where your firewall would enter into this at all. What firewall are you talking about? Can you ping the prinnter's IP address?
Let me describe a typical setup of this kind:
You have A network-capable printer connected to your LAN (meaning, an Ethernet switch or hub, not a router).
The printer's network card is assigned a non-changing IP address on the LAN - either a static or a DHCP reservation.
The Windows print server is configured with a standard TCP/IP port that specifies that IP address
The printer is configured as a local printer on the print server, using the latest supported drivers.
The printer is shared from the Windows server so that workstations can print to it.
Does that sound right?
If you're having problems with printing gibberish, then it's most likely a driver problem.
- Follow-Ups:
- Re: network printer is ready but error when printing
- From: Lanwench [MVP - Exchange]
- Re: network printer is ready but error when printing
- References:
- network printer is ready but error when printing
- From: mixty
- Re: network printer is ready but error when printing
- From: Lanwench [MVP - Exchange]
- network printer is ready but error when printing
- Prev by Date: Re: Limit Network Card to Internal Only
- Next by Date: Re: Test dhcp
- Previous by thread: Re: network printer is ready but error when printing
- Next by thread: Re: network printer is ready but error when printing
- Index(es):
Relevant Pages
|
Loading
