Hi Folks
I am running a DELL laptop with CentOS 6.2 64-bit. At home, I set a network with another Windows WS and a Color Laser Printer Brother HL-3040CN. Printing from the Windows machine is fine.
I used the instructions from Brother Support Site:
http://welcome.solutions.brother.com/bsc/public_s/id/linux/en/instruction_prn1a.html
The only difference is that I didn't use the option --nodeps on rpm command.
By default, the printer is connected by dnssd protocol. The manual says to change it to lpd. I tried both protocol unsuccessfully.
Here the facts:
1 - Driver Installation successful
2 - Using CUPS Web Interface I successfully modified connection protocol to lpd
3 - Print a test page - it says "Processing since " in CUPS. Also, at the printer Data Indicator turns on. But the status keeps "Ready" and no printing is executed. The strange thing is the Data Indicator keeps on. Normally it receives the data, blinks a couple of times and turn off while it is printing.
Many thanks in advance.
Network Brother Printer HL-3040CN Installed but no printing
-
- Posts: 9
- Joined: 2012/02/19 14:55:48
- Location: Sao Mateus, ES - Brazil
- Contact:
-
- Posts: 9
- Joined: 2012/02/19 14:55:48
- Location: Sao Mateus, ES - Brazil
- Contact:
Re: Network Brother Printer HL-3040CN Installed but no printing
It seems nobody uses (or at least has no problem with) this printer.
Just to add some information, I realized that the data is sent to printer but some information that printer sends back to computer is no received which generates the following message at CUPS interface:
"remote host did not respond with command status byte after 300 seconds"
Could this be related to SElinux configuration? I think it is activated in my OS by default but I never change its configurations. Is there something specific for network printers?
Thanks in advance
Just to add some information, I realized that the data is sent to printer but some information that printer sends back to computer is no received which generates the following message at CUPS interface:
"remote host did not respond with command status byte after 300 seconds"
Could this be related to SElinux configuration? I think it is activated in my OS by default but I never change its configurations. Is there something specific for network printers?
Thanks in advance
-
- Retired Moderator
- Posts: 18276
- Joined: 2006/12/13 20:15:34
- Location: Tidewater, Virginia, North America
- Contact:
Network Brother Printer HL-3040CN Installed but no printing
I don't know of any SELinux or firewall settings required for network printers. My Brother MFC-7820N Laser [i]just works[/i] with the supplied driver. You could try
[code]setenforce 0
service iptables stop[/code]
to temporarily disable one or both for testing.
[code]setenforce 0
service iptables stop[/code]
to temporarily disable one or both for testing.
-
- Posts: 9
- Joined: 2012/02/19 14:55:48
- Location: Sao Mateus, ES - Brazil
- Contact:
Re: Network Brother Printer HL-3040CN Installed but no printing
Hello pschaff
I have been busy and didn't try your suggestions right way. I did that today and it works. I just disable SELinux with
setenforce 0
And the printing went on.
for the record, I reported this issue to Brother Helpline. They found this bug only in this Model (HL-3040CN).
Well, I'm not sure this is a bug...
Anyway, let's put this thread in posterity
Cheers
I have been busy and didn't try your suggestions right way. I did that today and it works. I just disable SELinux with
setenforce 0
And the printing went on.
for the record, I reported this issue to Brother Helpline. They found this bug only in this Model (HL-3040CN).
Well, I'm not sure this is a bug...
Anyway, let's put this thread in posterity
Cheers
-
- Retired Moderator
- Posts: 18276
- Joined: 2006/12/13 20:15:34
- Location: Tidewater, Virginia, North America
- Contact:
Re: Network Brother Printer HL-3040CN Installed but no printing
That's not a permanent or recommended solution. For one thing, it will not survive a reboot, and for another, disabling SELinux security features is undesirable. Even if there is a bug that is bothering SELinux is should be possible to create a policy rule to handle it. See the Wiki [url=http://wiki.centos.org/?action=fullsearch&context=180&value=SELinux&titlesearch=Titles]SELinux articles[/url] for some guidance, and provide details if you run into problems.