[gentoo-user] New laptop won't remote print

[gentoo-user] New laptop won't remote print

[Grant]

I can't get my new laptop to print to a remote printer.  My old laptop
still does it just fine.  They both have identical
/etc/cups/client.conf:

ServerName 192.168.0.1

Each laptop is tested as 192.168.0.2.  Neither laptop has a firewall
running.  I can't think of anything else to check.  Any ideas?

- Grant

[gentoo-user] Re: New laptop won't remote print

[walt]

On 10/18/2009 10:09 AM, Grant wrote:
> I can't get my new laptop to print to a remote printer.  My old laptop
> still does it just fine.  They both have identical
> /etc/cups/client.conf:
> 
> ServerName 192.168.0.1
> 
> Each laptop is tested as 192.168.0.2.  Neither laptop has a firewall
> running.  I can't think of anything else to check.  Any ideas?

There's a lot more to cups configuration than just that one file. How
did you configure cups for that machine?  Do you know about the www
configuration interface for cups?  It's wonderful:

http://localhost:631/

But make sure cups is already running and the printer is on before
you start.

Re: [gentoo-user] Re: New laptop won't remote print

[Grant]

>> I can't get my new laptop to print to a remote printer.  My old laptop
>> still does it just fine.  They both have identical
>> /etc/cups/client.conf:
>>
>> ServerName 192.168.0.1
>>
>> Each laptop is tested as 192.168.0.2.  Neither laptop has a firewall
>> running.  I can't think of anything else to check.  Any ideas?
>
> There's a lot more to cups configuration than just that one file. How
> did you configure cups for that machine?  Do you know about the www
> configuration interface for cups?  It's wonderful:
>
> http://localhost:631/
>
> But make sure cups is already running and the printer is on before
> you start.

The printer prints from the machine it's attached to no problem.  With
remote printing, I think that one file is all that's necessary on the
client.

- Grant

Re: [gentoo-user] Re: New laptop won't remote print

[Alex Schuster]

Grant writes:

> The printer prints from the machine it's attached to no problem.  With
> remote printing, I think that one file is all that's necessary on the
> client.

And maybe not even that, I have clients running on which I did not configure 
anything at all. My client.conf's entry is "ServerName 
/var/run/cups/cups.sock" only. I used to have the CUPS server in there, but 
it seems this is no longer necessary. Changes on the sever show up on the 
clients in less than a minute I'd say.
I do not know whether the client searches the local subnet for a server, or 
whether a server broadcasts its existence along the subnet, but it just 
works here.

But why it doesn't work for you? I don't know :(

	Wonko

Re: [gentoo-user] Re: New laptop won't remote print

[Alan McKinnon]

On Sunday 18 October 2009 21:06:18 Alex Schuster wrote:
> I do not know whether the client searches the local subnet for a server,
>  or  whether a server broadcasts its existence along the subnet, but it
>  just works here.
> 

It's done by SNMP usually. Other methods exist, such as zeroconf (avahi). 
Which explains why printers "just appear"

-- 
alan dot mckinnon at gmail dot com

[gentoo-user] Re: New laptop won't remote print

[Grant Edwards]

On 2009-10-18, Grant <emailgrant@gmail.com> wrote:

> I can't get my new laptop to print to a remote printer.  My
> old laptop still does it just fine.  They both have identical
> /etc/cups/client.conf:
>
> ServerName 192.168.0.1
>
> Each laptop is tested as 192.168.0.2.  Neither laptop has a firewall
> running.  I can't think of anything else to check.  Any ideas?

Having the laptops both using the same IP address is bound to
cause odd problems.  You don't have both of them up and running
usig 192.168.0.2 do you?

-- 
Grant

Re: [gentoo-user] Re: New laptop won't remote print

[Grant]

>> I can't get my new laptop to print to a remote printer.  My
>> old laptop still does it just fine.  They both have identical
>> /etc/cups/client.conf:
>>
>> ServerName 192.168.0.1
>>
>> Each laptop is tested as 192.168.0.2.  Neither laptop has a firewall
>> running.  I can't think of anything else to check.  Any ideas?
>
> Having the laptops both using the same IP address is bound to
> cause odd problems.  You don't have both of them up and running
> usig 192.168.0.2 do you?
>
> --
> Grant

Thanks everyone.  This seems to have fixed itself.

- Grant