The ADSL is connected toa switch and from that switch all the other
clients and the server itself. All clients, LPD hosts and servers use
IPs, I think no name resolution must be present for it to work.
Yesterday I switched servers to a backup CentOS 5 install that works
excelent with or without In
>>
>
> Hmmm... this sounds like common issues that crop up when you are having
DNS resolution issues. Are the name servers for your network on the "other
end" of the ADSL connection? If so, you might be able to resolve some of
the issues by editing the hosts file to make sure the local systems ar
On 03/04/2013 07:52 PM, Juan De Mola wrote:
The logs only show LPD backend failed.
I have tested restarting networking, re enabling printers, restartig the
service. The only way to print is sending release commands from the CUPS
web interface.
The telnet login screen also become slow when the I
El 04/03/2013 09:41 p.m., SilverTip257 escribió:
> On Sat, Mar 2, 2013 at 11:24 AM, Juan De Mola wrote:
>
>> Hi.
>>
>> I have CentOS 6 on a HP ProLiant ML110 G7. We have a cobol invoicing
>> system that prints to LPD printers on Windows hosts via CUPS.
>>
>> All works great until the ADSL service
On Sat, Mar 2, 2013 at 11:24 AM, Juan De Mola wrote:
> Hi.
>
> I have CentOS 6 on a HP ProLiant ML110 G7. We have a cobol invoicing
> system that prints to LPD printers on Windows hosts via CUPS.
>
> All works great until the ADSL service goes down. The printers stop
> working and the service res
Hi.
I have CentOS 6 on a HP ProLiant ML110 G7. We have a cobol invoicing
system that prints to LPD printers on Windows hosts via CUPS.
All works great until the ADSL service goes down. The printers stop
working and the service restart gives a connection error.
What will be happening here and how
6 matches
Mail list logo
