Graham Smith wrote:
On Wed, 27 Apr 2005 02:16, you wrote:
Graham Smith wrote:
The easiest way to solve this problem would be for myself to look at
your
settings in /etc/cups.
Attached
Server: IP Address 192.168.0.1 Hostname Umalusi
Client: IP Address 192.168.0.2 Hostname Spy
Printer: Epson Stylus 800+ with ESCP2 using the Linux module for the 800 as there was not one for 800+.
I will have a look at the settings and send back the files with any mods required.
Please comment the changes as then I can learn for next time.
Very much appreciated!!
I have looked at the files. The client.conf is OK. I have added a number of comments to the cupsd.conf. There were a few settings wrong which I have fixed. Also there was a few lines right at the end of the file which were definitely crap, which I have commented out.
There are two main errors as far as I can tell, firstly the ServerName setting looked incorrect, replaced it with its IP address. Secondly you had missed the BrowseAddress setting.
Just replace the /etc/cups/cupsd.conf with the one attached. You don't need to replace the client.conf in the other machine as it has the correct settings.
See how you go and get back to me if it still doesn't work.
For your information the security section in cupsd.conf has a certain syntax which starts with <Location / ........ > and ends with </Location>
For example <Location /> Order Allow,Deny Allow From 127.0.0.1 Allow From 127.0.0.2 Allow From @LOCAL </Location>
A large number of the security options are commented out and are only required if you want to further limit access to certain functions. Thank you again Graham for looking at and editing the necessary files. I have reverted back to the list in case it helps others.
I know, from Windows days, that the server must be booted first, ten the clients. I did this specifically making sure the printer initialized. I figured now, with the correct conf files, it would a simple matter of pressing print on the Mozilla GUI on the client and the page would automagically eject from the printer connected to the server. Alas I was wrong. :( I 'checked' the client settings via the Yast printer configuration but all was in place. I noticed that the test failed when I tested connectivity to the server in Yast. Assuming it was still going to work I soldiered on... ...When I did press 'Print' on the Mozilla GUI I was presented with a KPrinter GUI that said it was initialising and that it was connected to Umalusi:631. NO amount of clicking on the close option or even looking for kprinter under a terminal screen could get the KPrinter dialogs to disappear. I also tried the printer manager from the printer icon on the task bar with the same result. It actually took 2 reboots to rid myself of the Kprinter dialogs. So, now what needs tweaking? Especially since I get a 100msec ping reply from the server when I ping 192.168.0.1 on the client side. I assume that because I am getting a reply back on the ping that the machines are 'talking' to one another. Where should I check error messages after I have tried to print? Where to next? -- ======================================================================== Hylton Conacher - Linux user # 229959 at http://counter.li.org Currently using SuSE 9.0 Professional with KDE 3.1 ========================================================================