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 I can solve it? Our previous server was on CentOS 5 and worked OK.
Thanks.
-- Juan Pablo De Mola Rodríguez
On Sat, Mar 2, 2013 at 11:24 AM, Juan De Mola juan.demola@gmail.com 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 restart gives a connection error.
What will be happening here and how I can solve it? Our previous server was on CentOS 5 and worked OK.
Check CUPS logs.
If you were to locally log onto the box, down, then up the interface does it behave the same?
Thanks.
-- Juan Pablo De Mola Rodríguez _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
El 04/03/2013 09:41 p.m., SilverTip257 escribió:
On Sat, Mar 2, 2013 at 11:24 AM, Juan De Mola juan.demola@gmail.com 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 restart gives a connection error.
What will be happening here and how I can solve it? Our previous server was on CentOS 5 and worked OK.
Check CUPS logs.
If you were to locally log onto the box, down, then up the interface does it behave the same?
Thanks.
-- Juan Pablo De Mola Rodríguez _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
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 Internet goes down.
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 Internet goes down. _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
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 are resolving even when the name servers are unavailable or running a local caching nameserver.
Just a thought!
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 are resolving even when the name servers are unavailable or running a local caching nameserver.
Just a thought!
It does sound like it could be that... But I'd just like the OP to clarify his network topology... Is the ADSL connected to this server and then this being a gateway for other systems?
Also telnet? Out of sheer curiosity why the telnet server?
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 Internet.
Telne, well, the software programmer has used it for years and is very sticky to it. I am trying to force SSH on new deployments, testing the keep alive methods.
2013/3/5 James Hogarth james.hogarth@gmail.com:
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 are resolving even when the name servers are unavailable or running a local caching nameserver.
Just a thought!
It does sound like it could be that... But I'd just like the OP to clarify his network topology... Is the ADSL connected to this server and then this being a gateway for other systems?
Also telnet? Out of sheer curiosity why the telnet server? _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
-- Juan Pablo De Mola Rodríguez
-
James Hogarth -
Jay Leafey -
Juan De Mola -
SilverTip257