4:13 p.m.
Hello all,
Sometime in the last couple of weeks, I lost my ability to print to the
office printer. If I check (KDE) System Settings, the printer's status
reads, "Paused - 'Unable to connect to CIFS host after (tried 3
times)'".
Everybody else can still use this printer, and there have been no major
network reconfiguration events recently. I can't figure out how to bring
this back online.
I tried to simply re-add the long-existing printer again, but the "Add a
New Printer" dialog won't let me browse the network for any printers at
all. The [Browse] button under "Windows Printer via SAMBA" is greyed out,
so I would have to type the URI by hand. But the URI is correct in the
configuration of the current, non-working, printer, as far as I know.
Is there any way to figure out why the current printer is offline, beyond
"Unable to connect"? Not being able to print is really messing with my
workflow.
-Alan
12:55 p.m.
Sorry for not getting back to this in a more timely manner. The computer in
question is my office workstation, and eventually I need to get some work
done for my boss regardless of whether I can print. But not being able to
print has been a serious headache.
Thanks to all who made suggestions here. I tried it all, and tried some
stuff that made me wonder if I was destroying my machine while doing it.
Fortunately, I didn't do permanent damage to my setup.
Anyway, it turns out that printing just started working again after the
machine was rebooted. So I think I'm good now. (In case you are wondering
why I didn't do that much earlier, my machine sometimes acts as a
light-duty server, and opportunities to reboot are often very limited.)
Thanks again to everyone who tried to help.
On Wed, Sep 11, 2013 at 5:57 AM, poma <pomidorabelisima(a)gmail.com> wrote:
On 11.09.2013 12:52, Tim Waugh wrote:
> On Mon, 2013-09-09 at 14:13 -0700, Alan Evans wrote:
>> Is there any way to figure out why the current printer is offline,
>> beyond "Unable to connect"? Not being able to print is really messing
>> with my workflow.
>
> Enable debug logging like this: su -c 'cupsctl --debug-logging' Then
> look in /var/log/cups/error_log after attempting to print.
> You can turn off debug logging with: su -c 'cupsctl --no-debug-logging'
>
> Tim.
> */
>
>
>
http://fedoraproject.org/wiki/How_to_debug_printing_problems
poma
--
users mailing list
users(a)lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org
8:56 a.m.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 09/09/2013 06:34 PM, Rick Stevens wrote:
On 09/09/2013 02:49 PM, Alan Evans issued this missive:
> On Mon, Sep 9, 2013 at 2:34 PM, Rick Stevens wrote:
>
> Well, since it seems to be a Windows printer (e.g. a print spooler
> running on a Windows box), did they change the authentication at that
> end? Did you change the firewall settings on your box so that Samba stuff
> is blocked now?
>
>
> The authentication has not changed on the Windows box. (The guy in charge
> of that would never do that, since it would force him to go around
> reconfiguring everybody's machine for the new authentication. He would
> never want to do that much work.) In any case, I asked, and there has
> been no change to the print-spooler's configuration.
Did you do an update to your machine just before this started happening?
You also didn't say if you're running F17, F18 or F19 (or something older).
If you're running F20, then this isn't the list for that as F20 isn't
released yet.
> As for the firewall, it is disabled on this machine. For fun, I just
> issued a "setenforce 0" and tried resuming the printer. No change in
> status. So it is something of a mystery to me why I can't even browse for
> network printers.
I'm just shotgunning this, so bear with me. The firewall and SELinux are
completely separate things. "setenforce 0" does NOT disable SELinux--it
just puts it in permissive mode and SELinux still gets in the way on
certain things even in permissive mode (ask me how I know). You might find
some clues in SELinux's logs and such.
There are Samba-based selinux policies and booleans. To see if this is the
problem, disable SELinux completely by editing /etc/selinux/config and
changing the line:
SELINUX=enforcing
to
SELINUX=disabled
and rebooting. See if you can browse your network printers then. If so,
then obviously SELinux is in the way. Change the config line back and
reboot to re-enable SELinux, then have a looksee at the man pages for
samba_net_selinux, samba_unconfined_net_selinux and
samba_unconfined_script_selinux and play with that stuff.
If you still can't browse with SELinux disabled, please ensure that the
firewall is disabled. As root, try "iptables -L -n" and see if anything
pops up. You must permit incoming UDP connections on ports 137 and 138 to
browse Samba/SMB/Windows stuff.
Like I said, this is shotgun stuff and it may not solve your problem, but
it's a start.
---------------------------------------------------------------------- -
Rick Stevens, Systems Engineer, AllDigital ricks(a)alldigital.com - -
AIM/Skype: therps2 ICQ: 22643734 Yahoo: origrps2 - -
- - Real Time, adj.: Here and now, as opposed to fake time, which only - -
occurs there and then -
----------------------------------------------------------------------
What things
are you seeing Blocked with SELinux is in permissive mode? Bugzillas?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.14 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iEYEARECAAYFAlIvJScACgkQrlYvE4MpobMERACfSDLwD20kogwGIDoOSiAFwriw
pRQAoLi1hvh2azMmJ9U/UBFFTO7u6Hlw
=IWPO
-----END PGP SIGNATURE-----
4:49 p.m.
On Mon, Sep 9, 2013 at 2:34 PM, Rick Stevens wrote:
Well, since it seems to be a Windows printer (e.g. a print spooler
running on a Windows box), did they change the authentication at that
end? Did you change the firewall settings on your box so that Samba
stuff is blocked now?
The authentication has not changed on the Windows box. (The guy in charge
of that would never do that, since it would force him to go around
reconfiguring everybody's machine for the new authentication. He would
never want to do that much work.) In any case, I asked, and there has been
no change to the print-spooler's configuration.
As for the firewall, it is disabled on this machine. For fun, I just issued
a "setenforce 0" and tried resuming the printer. No change in status. So it
is something of a mystery to me why I can't even browse for network
printers.
-Alan
4:34 p.m.
On 09/09/2013 02:13 PM, Alan Evans issued this missive:
Hello all,
Sometime in the last couple of weeks, I lost my ability to print to the
office printer. If I check (KDE) System Settings, the printer's status
reads, "Paused - 'Unable to connect to CIFS host after (tried 3
times)'". Everybody else can still use this printer, and there have been
no major network reconfiguration events recently. I can't figure out how
to bring this back online.
I tried to simply re-add the long-existing printer again, but the "Add a
New Printer" dialog won't let me browse the network for any printers at
all. The [Browse] button under "Windows Printer via SAMBA" is greyed
out, so I would have to type the URI by hand. But the URI is correct in
the configuration of the current, non-working, printer, as far as I know.
Is there any way to figure out why the current printer is offline,
beyond "Unable to connect"? Not being able to print is really messing
with my workflow.
Well, since it seems to be a Windows printer (e.g. a print spooler
running on a Windows box), did they change the authentication at that
end? Did you change the firewall settings on your box so that Samba
stuff is blocked now?
----------------------------------------------------------------------
- Rick Stevens, Systems Engineer, AllDigital ricks(a)alldigital.com -
- AIM/Skype: therps2 ICQ: 22643734 Yahoo: origrps2 -
- -
- Never try to outstubborn a cat. -
----------------------------------------------------------------------
7:57 a.m.
On 11.09.2013 12:52, Tim Waugh wrote:
On Mon, 2013-09-09 at 14:13 -0700, Alan Evans wrote:
> Is there any way to figure out why the current printer is offline,
> beyond "Unable to connect"? Not being able to print is really messing
> with my workflow.
Enable debug logging like this: su -c 'cupsctl --debug-logging' Then
look in /var/log/cups/error_log after attempting to print.
You can turn off debug logging with: su -c 'cupsctl --no-debug-logging'
Tim.
*/
http://fedoraproject.org/wiki/How_to_debug_printing_problems
poma
5:52 a.m.
On Mon, 2013-09-09 at 14:13 -0700, Alan Evans wrote:
Is there any way to figure out why the current printer is offline,
beyond "Unable to connect"? Not being able to print is really messing
with my workflow.
Enable debug logging like this: su -c 'cupsctl --debug-logging' Then
look in /var/log/cups/error_log after attempting to print.
You can turn off debug logging with: su -c 'cupsctl --no-debug-logging'
Tim.
*/
5:34 p.m.
On 09/09/2013 02:49 PM, Alan Evans issued this missive:
On Mon, Sep 9, 2013 at 2:34 PM, Rick Stevens wrote:
Well, since it seems to be a Windows printer (e.g. a print spooler
running on a Windows box), did they change the authentication at that
end? Did you change the firewall settings on your box so that Samba
stuff is blocked now?
The authentication has not changed on the Windows box. (The guy in
charge of that would never do that, since it would force him to go
around reconfiguring everybody's machine for the new authentication. He
would never want to do that much work.) In any case, I asked, and there
has been no change to the print-spooler's configuration.
Did you do an update to your machine just before this started happening?
You also didn't say if you're running F17, F18 or F19 (or something
older). If you're running F20, then this isn't the list for that as F20
isn't released yet.
As for the firewall, it is disabled on this machine. For fun, I just
issued a "setenforce 0" and tried resuming the printer. No change in
status. So it is something of a mystery to me why I can't even browse
for network printers.
I'm just shotgunning this, so bear with me. The firewall and SELinux
are completely separate things. "setenforce 0" does NOT disable
SELinux--it just puts it in permissive mode and SELinux still gets in
the way on certain things even in permissive mode (ask me how I know).
You might find some clues in SELinux's logs and such.
There are Samba-based selinux policies and booleans. To see if this is
the problem, disable SELinux completely by editing /etc/selinux/config
and changing the line:
SELINUX=enforcing
to
SELINUX=disabled
and rebooting. See if you can browse your network printers then. If so,
then obviously SELinux is in the way. Change the config line back and
reboot to re-enable SELinux, then have a looksee at the man pages for
samba_net_selinux, samba_unconfined_net_selinux and
samba_unconfined_script_selinux and play with that stuff.
If you still can't browse with SELinux disabled, please ensure that the
firewall is disabled. As root, try "iptables -L -n" and see if anything
pops up. You must permit incoming UDP connections on ports 137 and 138
to browse Samba/SMB/Windows stuff.
Like I said, this is shotgun stuff and it may not solve your problem,
but it's a start.
----------------------------------------------------------------------
- Rick Stevens, Systems Engineer, AllDigital ricks(a)alldigital.com -
- AIM/Skype: therps2 ICQ: 22643734 Yahoo: origrps2 -
- -
- Real Time, adj.: Here and now, as opposed to fake time, which only -
- occurs there and then -
----------------------------------------------------------------------
3848
days inactive
3879
days old
7 comments
5 participants
participants (5)
-
Alan Evans -
Daniel J Walsh -
poma -
Rick Stevens -
Tim Waugh