On Sun, 2005-10-02 at 18:34 -0700, Art Fore wrote:
Have searched the mail lists, suse knowledge base, and google, but found nothing on this problem.
I have a server set up with CUPS using local printer. I can print to this printer from the server, I can access it via http://localhost:631. Cups server is setup to allow any address on the network or the domain with allow/deny box checked.
I cannot access it from my desktop using print via network cups server. If I setup for CUPS client only, (setting up as server, I get essentially the same thing) I get the dialog box and enter the server address (selecting the Lookup button, it will not find it) Then I click the "test remote IPP access". It hangs there forever or until I open the printer setup on the server and click "Finish" the client then comes up that it is accessable. I click "Finish", and it hangs again until I open the printer setup on the server again and click "Finish" again. There are no errors in the log file, the server does come up with a strange line, "Sending browsing info to c0a800ff:631". I thought this was the hardware address of the network card, but it is not.
Anyone have any idea what is going on?
Art
lpstat -t shows printer accepting jobs on server. lpstat -t on client just lockups up until I do the Yast, Hardware, Printer, then Finish. It then comes up that server-error-server-unavailable. I also noticed that in the error log, it does not show cups as listening as it did on some emails I have seen on the web. According to CUPS website, it should be listening on all interfaces except modem. Any suggestions? Art