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.
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
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.
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
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).
On 2009-10-18, Grant emailgr...@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
6 matches
Mail list logo