greetings after reading 'cups printing setup mini-howto', 2005, by till kamppeter, i am still having problems getting cups to work. [system info, test, errors] uname -r = 2.6.18-128.7.1.el5 last updated; yum.log:Jun 04 04:06:08 Updated: cups-libs - 1:1.3.7-8.el5_3.6.i386 yum.log:Jun 04 04:06:39 Updated: cups - 1:1.3.7-8.el5_3.6.i386 yum.log:Jun 04 04:06:40 Updated: cups-lpd - 1:1.3.7-8.el5_3.6.i386 yum.log:Jun 04 04:06:41 Updated: cups-devel - 1:1.3.7-8.el5_3.6.i386 services - cupsd is running --- from firefox; host://localhost:631 times out from konqueror; host://localhost:631 times out --- from v-term, print fails with; A print error occurred. Error message receiver from system: /usr/bin/lpr -P 'ml4500''-#1''/tmp/kde-geo/kdeprint_oNsom8bE': execution failed with message: /usr/bin/lpr: Connection refused --- from kwrite, print fails with; A print error occurred. Error message receiver from system: /usr/bin/lpr -P 'ml4500''-#1''/tmp/kde-geo/kdeprint_3KAMxRfY': execution failed with message: /usr/bin/lpr: Connection refused --- /etc/cups/cupsd.conf; LogLevel debug --- from /var/log/cups/error, errors are; E [17/Sep/2009:12:42:43 +0000] Unable to bind socket for address \ 127.0.0.1:631 - Cannot assign requested address. X [17/Sep/2009:12:42:43 +0000] No Listen or Port lines were found to \ allow access via localhost! E [17/Sep/2009:13:08:04 +0000] File or directory for "ServerCertificate \ /etc/cups/ssl/server.crt" on line 145 does not exist! E [17/Sep/2009:13:08:04 +0000] File or directory for "ServerKey \ /etc/cups/ssl/server.key" on line 156 does not exist! --- running: $ lpinfo -v locks system, have to reset system to get back $ cat /proc/sys/dev/parport/parport*/autoprobe* CLASS:PRINTER; MODEL:ML-4500; MANUFACTURER:Samsung; COMMAND SET:GDI; $ ll /dev/lp* crw-rw---- 1 root lp 6, 0 Sep 18 05:16 /dev/lp0 any and all suggestions welcome. tia. -- peace out. tc,hago. g . **** in a free world without fences, who needs gates. ** help microsoft stamp out piracy - give linux to a friend today. ** to mess up a linux box, you need to work at it. to mess up an ms windows box, you just need to *look* at it. ** learn linux: 'Rute User's Tutorial and Exposition' http://rute.2038bug.com/index.html 'The Linux Documentation Project' http://www.tldp.org/ 'LDP HOWTO-index' http://www.tldp.org/HOWTO/HOWTO-INDEX/index.html 'HowtoForge' http://howtoforge.com/ ****