Windows laptop, linux desktop, one printer

burkert60401 · January 29, 2009, 1:54am

I have a desktop running SUSE 11.1 that is attached to a Brother HL-5140 laser printer. It is also linked to a wireless router. My wife has a windows laptop that has built in wireless. Both communicate with the internet very well. I have been trying to get the laptop to print wirelessly. So far, I have had little success. I am looking for suggestions to help me find the best way to approach this.

user · January 29, 2009, 2:10am

On Wed January 28 2009 06:56 pm, burkert60401 wrote:

>
> I have a desktop running SUSE 11.1 that is attached to a Brother HL-5140
> laser printer. It is also linked to a wireless router. My wife has a
> windows laptop that has built in wireless. Both communicate with the
> internet very well. I have been trying to get the laptop to print
> wirelessly. So far, I have had little success. I am looking for
> suggestions to help me find the best way to approach this.
>
>
burkert;

Check the HowTo’s located here:
http://www.swerdna.net.au/linux.html
Printer sharing can be done by using either Samba or IPP.
P. V.
“We’re all in this together, I’m pulling for you.” Red Green

burkert60401 · February 5, 2009, 7:11pm

I have worked through the excellent how-to at

Linux Printer Sharing: Suse/openSUSE 10.x 11.x IPP Print Server for Linux & Windows Clients

up to the paragraph that says

“Check communications between Clients and Server: Do this the same for each Linux and Windows client. Open a terminal or DOS prompt and ping the Server with ping 192.168.2.2. A positive response there is a must before proceeding. Next enter this address in the web browser of the client and look at the installed printer on the server: http://192.168.2.2:631/printers/. Here’s a screenshot of what you should see. When you establish these adequate communications you can proceed to configure the client”

When I use the windows laptop to ping my IP address(192.168.0.100) I get a reply that shows definite contact.

However when I use the Firefox browser to look at the installed printer using

http://192.168.0.100:631/printers/

I get a message that says:

“Failed to Connect
Firefox can’t establish a connection to the server at 192.168.0.100:631.”

I’m at a bit of a loss as to how to proceed from here.

user · February 6, 2009, 5:06am

On Thu February 5 2009 12:16 pm, burkert60401 wrote:

>
> I have worked through the excellent how-to at
>
> -‘Linux Printer Sharing: Suse/openSUSE 10.x 11.x IPP Print Server for
> Linux & Windows Clients’
> (http://www.swerdna.net.au/linhowtoprintipp.html)-
>
> up to the paragraph that says
>
> “-Check communications between Clients and Server: Do this the same for
> each Linux and Windows client. Open a terminal or DOS prompt and ping
> the Server with ping 192.168.2.2. A positive response there is a must
> before proceeding. Next enter this address in the web browser of the
> client and look at the installed printer on the server:
> http://192.168.2.2:631/printers/. Here’s a screenshot of what you should
> see. When you establish these adequate communications you can proceed to
> configure the client-”
>
> When I use the windows laptop to ping my IP address(192.168.0.100) I
> get a reply that shows definite contact.
>
> However when I use the Firefox browser to look at the installed printer
> using
>
> http://192.168.0.100:631/printers/
>
> I get a message that says:
>
> “Failed to Connect
> Firefox can’t establish a connection to the server at
> 192.168.0.100:631.”
>
> I’m at a bit of a loss as to how to proceed from here.
>
>
Burkert;
Make sure the Firewall is not blocking port 631. For testing purpose only,
disable the firewall. If it works, you can open port 631 on the firewall.

P. V.
“We’re all in this together, I’m pulling for you.” Red Green

burkert60401 · February 6, 2009, 7:29pm

After turning off the firewall, I have the same result.

user · February 7, 2009, 12:46am

On Fri February 6 2009 12:36 pm, burkert60401 wrote:

>
> After turning off the firewall, I have the same result.
>
>
burkert;

From the CUPS server can you access CUPS with:
http://localhost:631/
Look at the contents of:
/etc/xinetd.d/cups-lpd

make sure you have:


disable     = no

If the above is ok or changing does not help, please post the contents of:

/etc/cups/cupsd.conf

Note: If you change /etc/xinitd.d/cups=lpd, you may need to reboot or at
least restart cups for the changes to take effect; not sure about this, but
it would do no harm.

P. V.
“We’re all in this together, I’m pulling for you.” Red Green

burkert60401 · February 9, 2009, 7:06pm

1.Using http://localhost:631/ I did access the cups server.

In
/etc/xinetd.d/cups-lpd

disabe was set to yes so I changed it to
disable = no
I then restarted

I tried the ping from the windows laptop. It was good.
I then tried
http://192.168.0.100:631/printers/

I still get a message that says:

“Failed to Connect
Firefox can’t establish a connection to the server at
192.168.0.100:631.”

"3. post the contents of:

/etc/cups/cupsd.conf"

Well, here goes:

“$Id: cupsd.conf.in 7199 2008-01-08 00:16:30Z mike $”

Sample configuration file for the Common UNIX Printing System (CUPS)

scheduler. See “man cupsd.conf” for a complete description of this

file.

Log general information in error_log - change “info” to “debug” for

troubleshooting…

LogLevel info

Administrator user group…

SystemGroup sys root

Listen to all connections for from the local machine.

#Listen localhost:631
#Listen /var/run/cups/cups.sock
#Port631

Show shared printers on the local network.

Browsing On
BrowseOrder allow,deny
BrowseAllow @LOCAL

Default authentication type, when authentication is required…

DefaultAuthType Basic

Restrict access to the server…

<Location />
Order deny, allow
Deny From All
Allow From 127.0.0.1
Allow From 127.0.0.2
Allow From 192.168.0.*
Allow From @LOCAL
</Location>

Restrict access to the admin pages…

<Location /admin>
Encryption Required
Order allow,deny
</Location>

Restrict access to configuration files…

<Location /admin/conf>
AuthType Default
Require user @SYSTEM
Order allow,deny
</Location>

Set the default printer/job policies…

Job-related operations must be done by the owner or an administrator…

<Limit Send-Document Send-URI Hold-Job Release-Job Restart-Job Purge-Jobs Set-Job-Attributes Create-Job-Subscription Renew-Subscription Cancel-Subscription Get-Notifications Reprocess-Job Cancel-Current-Job Suspend-Current-Job Resume-Job CUPS-Move-Job>
Require user @OWNER @SYSTEM
Order deny,allow
</Limit>

All administration operations require an administrator to authenticate…

<Limit CUPS-Add-Modify-Printer CUPS-Delete-Printer CUPS-Add-Modify-Class CUPS-Delete-Class CUPS-Set-Default>
AuthType Default
Require user @SYSTEM
Order deny,allow
</Limit>

All printer operations require a printer operator to authenticate…

<Limit Pause-Printer Resume-Printer Enable-Printer Disable-Printer Pause-Printer-After-Current-Job Hold-New-Jobs Release-Held-New-Jobs Deactivate-Printer Activate-Printer Restart-Printer Shutdown-Printer Startup-Printer Promote-Job Schedule-Job-After CUPS-Accept-Jobs CUPS-Reject-Jobs>
AuthType Default
Require user @SYSTEM
Order deny,allow
</Limit>

Only the owner or an administrator can cancel or authenticate a job…

<Limit Cancel-Job CUPS-Authenticate-Job>
Require user @OWNER @SYSTEM
Order deny,allow
</Limit>

<Limit All>
Order deny,allow
</Limit>
</Policy>

DefaultPolicy default

easy is a very relaxed policy

Job-related operations must be done by the owner or an administrator…

<Limit All>
Satisfy any
Order allow,deny
</Limit>
</Policy>

paranoid is a very restricted policy

Job-related operations must be done by the owner

<Limit Send-Document Send-URI Hold-Job Release-Job Restart-Job Purge-Jobs Set-Job-Attributes Create-Job-Subscription Renew-Subscription Cancel-Subscription Get-Notifications Reprocess-Job Cancel-Current-Job Suspend-Current-Job Resume-Job CUPS-Move-Job>
Require user @OWNER
Allow from 127.0.0.0/8
Order deny,allow
</Limit>

All administration operations require an administrator to authenticate…

<Limit CUPS-Add-Modify-Printer CUPS-Delete-Printer CUPS-Add-Modify-Class CUPS-Delete-Class CUPS-Set-Default>
AuthType Default
Require user @SYSTEM
Allow from 127.0.0.0/8
Order deny,allow
</Limit>

All printer operations require a printer operator to authenticate…

<Limit Pause-Printer Resume-Printer Enable-Printer Disable-Printer Pause-Printer-After-Current-Job Hold-New-Jobs Release-Held-New-Jobs Deactivate-Printer Activate-Printer Restart-Printer Shutdown-Printer Startup-Printer Promote-Job Schedule-Job-After CUPS-Accept-Jobs CUPS-Reject-Jobs>
AuthType Default
Require user @SYSTEM
Allow from 127.0.0.0/8
Order deny,allow
</Limit>

Only the owner or an administrator can cancel or authenticate a job…

<Limit Cancel-Job CUPS-Authenticate-Job>
Require user @OWNER
Allow from 127.0.0.0/8
Order deny,allow
</Limit>

<Limit All>
Require user @OWNER @SYSTEM
Allow from 127.0.0.0/8
Order deny,allow
</Limit>
</Policy>

End of “$Id: cupsd.conf.in 7199 2008-01-08 00:16:30Z mike $”.

2009-02-06,12:44:18 modify_cupsd_conf Listen localhost

Listen localhost:631

user · February 9, 2009, 7:39pm

On Mon February 9 2009 12:16 pm, burkert60401 wrote:

>
> 1.Using http://localhost:631/ I did access the cups server.
>
> 2. In
> /etc/xinetd.d/cups-lpd
>
> disabe was set to yes so I changed it to
> disable = no
> I then restarted
>
> I tried the ping from the windows laptop. It was good.
> I then tried
> http://192.168.0.100:631/printers/
>
> I still get a message that says:
>
> “Failed to Connect
> Firefox can’t establish a connection to the server at
> 192.168.0.100:631.”
>
>
<snip>
Burkert;

At first glance your cupsd.conf looks ok. I’ll look at it a bit more
carefully later. Is the firewall still disabled. If you only stopped it and
did not totally disable it via YAST->system->system services" it will start
with a reboot. Maybe you have port 631 blocked now.

–
P. V.
“We’re all in this together, I’m pulling for you.” Red Green

NigmaToolin · February 9, 2009, 8:03pm

I have

Show shared printers on the local network.

Browsing On
BrowseOrder allow,deny
BrowseAllow @LOCAL
BrowseAddress 192.168.0.0/24

Default authentication type, when authentication is required…

DefaultAuthType Basic

You may already have enough in place to use the printer but not to browse it?

user · February 9, 2009, 8:28pm

On Mon February 9 2009 12:16 pm, burkert60401 wrote:

<snip>
>
> #
> # “$Id: cupsd.conf.in 7199 2008-01-08 00:16:30Z mike $”
> #
> # Sample configuration file for the Common UNIX Printing System
> (CUPS)
> # scheduler. See “man cupsd.conf” for a complete description of
> this
> # file.
> #
>
> # Log general information in error_log - change “info” to “debug” for
> # troubleshooting…
> LogLevel info
>
> # Administrator user group…
> SystemGroup sys root
>
>
> # Listen to all connections for from the local machine.
> #Listen localhost:631
> #Listen /var/run/cups/cups.sock
> #Port631
Uncomment the last two
Listen /var/run/cups/cups.sock
Port 631
>
>
>
>
>
> # Show shared printers on the local network.
> Browsing On
> BrowseOrder allow,deny
> BrowseAllow @LOCAL
>
> # Default authentication type, when authentication is required…
> DefaultAuthType Basic
>
>
> # Restrict access to the server…
> <Location />
> Order deny, allow
Try:
Order allow,deny

No space after “,”
> Deny From All
> Allow From 127.0.0.1
> Allow From 127.0.0.2
> Allow From 192.168.0.*
> Allow From @LOCAL
> </Location>
>
> # Restrict access to the admin pages…
> <Location /admin>
> Encryption Required
> Order allow,deny
> </Location>
>
> # Restrict access to configuration files…
> <Location /admin/conf>
> AuthType Default
> Require user @SYSTEM
> Order allow,deny
> </Location>
>
> # Set the default printer/job policies…
> <Policy default>
> # Job-related operations must be done by the owner or an
> administrator…
> <Limit Send-Document Send-URI Hold-Job Release-Job Restart-Job
> Purge-Jobs Set-Job-Attributes Create-Job-Subscription Renew-Subscription
> Cancel-Subscription Get-Notifications Reprocess-Job Cancel-Current-Job
> Suspend-Current-Job Resume-Job CUPS-Move-Job>
> Require user @OWNER @SYSTEM
> Order deny,allow
> </Limit>
>
> # All administration operations require an administrator to
> authenticate…
> <Limit CUPS-Add-Modify-Printer CUPS-Delete-Printer
> CUPS-Add-Modify-Class CUPS-Delete-Class CUPS-Set-Default>
> AuthType Default
> Require user @SYSTEM
> Order deny,allow
> </Limit>
>
> # All printer operations require a printer operator to
> authenticate…
> <Limit Pause-Printer Resume-Printer Enable-Printer Disable-Printer
> Pause-Printer-After-Current-Job Hold-New-Jobs Release-Held-New-Jobs
> Deactivate-Printer Activate-Printer Restart-Printer Shutdown-Printer
> Startup-Printer Promote-Job Schedule-Job-After CUPS-Accept-Jobs
> CUPS-Reject-Jobs>
> AuthType Default
> Require user @SYSTEM
> Order deny,allow
> </Limit>
>
> # Only the owner or an administrator can cancel or authenticate a
> job…
> <Limit Cancel-Job CUPS-Authenticate-Job>
> Require user @OWNER @SYSTEM
> Order deny,allow
> </Limit>
>
> <Limit All>
> Order deny,allow
> </Limit>
> </Policy>
>
> DefaultPolicy default
>
> # easy is a very relaxed policy
> <Policy easy>
> # Job-related operations must be done by the owner or an
> administrator…
> <Limit All>
> Satisfy any
> Order allow,deny
> </Limit>
> </Policy>
>
> # paranoid is a very restricted policy
> <Policy paranoid>
> # Job-related operations must be done by the owner
> <Limit Send-Document Send-URI Hold-Job Release-Job Restart-Job
> Purge-Jobs Set-Job-Attributes Create-Job-Subscription Renew-Subscription
> Cancel-Subscription Get-Notifications Reprocess-Job Cancel-Current-Job
> Suspend-Current-Job Resume-Job CUPS-Move-Job>
> Require user @OWNER
> Allow from 127.0.0.0/8
> Order deny,allow
> </Limit>
> # All administration operations require an administrator to
> authenticate…
> <Limit CUPS-Add-Modify-Printer CUPS-Delete-Printer
> CUPS-Add-Modify-Class CUPS-Delete-Class CUPS-Set-Default>
> AuthType Default
> Require user @SYSTEM
> Allow from 127.0.0.0/8
> Order deny,allow
> </Limit>
>
> # All printer operations require a printer operator to
> authenticate…
> <Limit Pause-Printer Resume-Printer Enable-Printer Disable-Printer
> Pause-Printer-After-Current-Job Hold-New-Jobs Release-Held-New-Jobs
> Deactivate-Printer Activate-Printer Restart-Printer Shutdown-Printer
> Startup-Printer Promote-Job Schedule-Job-After CUPS-Accept-Jobs
> CUPS-Reject-Jobs>
> AuthType Default
> Require user @SYSTEM
> Allow from 127.0.0.0/8
> Order deny,allow
> </Limit>
>
> # Only the owner or an administrator can cancel or authenticate a
> job…
> <Limit Cancel-Job CUPS-Authenticate-Job>
> Require user @OWNER
> Allow from 127.0.0.0/8
> Order deny,allow
> </Limit>
>
> <Limit All>
> Require user @OWNER @SYSTEM
> Allow from 127.0.0.0/8
> Order deny,allow
> </Limit>
> </Policy>

>
> #
> # End of “$Id: cupsd.conf.in 7199 2008-01-08 00:16:30Z mike $”.
> #
> # 2009-02-06,12:44:18 modify_cupsd_conf Listen localhost
>
> Listen localhost:631
burkert;
I’ve made a few notes above on your cupsd.conf.

Since you can access CUPs on the server; go to http://localhost:631/. From the
Administration tab you can enable a few features with check marks and also
edit /etc/cups/cupsd.conf. Setting the check marks actually changes
cupsd.conf so do not do both at the same time. When you are asked to
authenticate the user is “root” and the password is your root’s password.

Be double sure your firewall is down while you test this; no sense getting two
problems at once. After you’re sure you can get remote access to CUPS, make
sure port 631 is open on your firewall and then re-enable it.

P. V.
“We’re all in this together, I’m pulling for you.” Red Green

tuxituk · February 9, 2009, 11:06pm

Hi,

can you telnet to 192.168.0.100 port 631?

i.e. from a console
telnet 192.168.0.100 631

If not then the server is either not listening on that port (daemon not running) or the firewall on the server is blocking client access to the port.

telnet localhost 631

from a console on the server will tell you if the daemon is accepting connections locally.

hth
J

Windows laptop, linux desktop, one printer

Note: If you change /etc/xinitd.d/cups=lpd, you may need to reboot or at least restart cups for the changes to take effect; not sure about this, but it would do no harm.

“$Id: cupsd.conf.in 7199 2008-01-08 00:16:30Z mike $”

Sample configuration file for the Common UNIX Printing System (CUPS)

scheduler. See “man cupsd.conf” for a complete description of this

file.

Log general information in error_log - change “info” to “debug” for

troubleshooting…

Administrator user group…

Listen to all connections for from the local machine.

Show shared printers on the local network.

Default authentication type, when authentication is required…

Restrict access to the server…

Restrict access to the admin pages…

Restrict access to configuration files…

Set the default printer/job policies…

Job-related operations must be done by the owner or an administrator…

All administration operations require an administrator to authenticate…

All printer operations require a printer operator to authenticate…

Only the owner or an administrator can cancel or authenticate a job…

easy is a very relaxed policy

Job-related operations must be done by the owner or an administrator…

paranoid is a very restricted policy

Job-related operations must be done by the owner

All administration operations require an administrator to authenticate…

All printer operations require a printer operator to authenticate…

Only the owner or an administrator can cancel or authenticate a job…

End of “$Id: cupsd.conf.in 7199 2008-01-08 00:16:30Z mike $”.

2009-02-06,12:44:18 modify_cupsd_conf Listen localhost

Show shared printers on the local network.

Default authentication type, when authentication is required…

Be double sure your firewall is down while you test this; no sense getting two problems at once. After you’re sure you can get remote access to CUPS, make sure port 631 is open on your firewall and then re-enable it.

Note: If you change /etc/xinitd.d/cups=lpd, you may need to reboot or at
least restart cups for the changes to take effect; not sure about this, but
it would do no harm.

Be double sure your firewall is down while you test this; no sense getting two
problems at once. After you’re sure you can get remote access to CUPS, make
sure port 631 is open on your firewall and then re-enable it.