Anne Wilson wrote: > One thing you could try - set up keychain authentication with keys. I've > only > used it in an ssh situation, but I believe it can work in lots of others. > You give the keychain password at the start of a session and that is > checked > against known-hosts on the remote machine. That's certainly worth a try. Thanks to Tim Waugh, who told me how to create the diagnostic file troubleshoot.txt, I have worked out the cause of my problem. Firstly, I thought that on my laptop (192.168.2.7) I had to go to <http://localhost:631> and add my printer, which is attached to the computer 192.168.2.1, giving the URI <http://192.168.2.1:631/printers/HP_LaserJet_5L>. I now see that it is not necessary to do anything on the laptop, apart from start cups. The printer can then be seen in the CUPS web interface. (I thought I had set the printer to be shared, but perhaps I failed to do this originally.) The actual problem arose because my server, running httpd, is 192.168.2.2 . It seems that either CUPS or hp-setup substituted 192.168.2.2 for 192.168.2.1 in its internal working, as shown in the diagnostic file. -- Timothy Murphy e-mail: gayleard /at/ eircom.net tel: +353-86-2336090, +353-1-2842366 s-mail: School of Mathematics, Trinity College, Dublin 2, Ireland -- fedora-list mailing list fedora-list@xxxxxxxxxx To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
