Rather than try to summarize this problem, let me just start in with the symptoms and workarounds, which seem related. Background: about 12 FC3 workstations, printing via CUPS with a samba connection to a printer shared by a Win2K server. We use a dummy print user "linuxprint" as the username to connect to the shared printer. Symptom/Workaround 1: when we tried to add this printer to each workstation, we thought we could just ssh over and copy in a new /etc/cups/printers.conf file. Upon restarting CUPS, for example by restarting the computer, we expected users to be able to print to the new printer. But they couldn't; we had to login as root, go into the GUI printers config (System Settings--Printers), and edit the printer. We didn't have to change anything, only go into the printer and click OK. Then they could print. Symptom/Workaround 2: recently we reinstalled some of our Windows servers after a crash, and we forgot, at first, to recreate this "linuxprint" user. So Linux users were getting the NT_STATUS_LOGON_FAILURE message. We recreated the linuxprint user, with the same password as before. Upon restarting CUPS, for example by restarting the computer, we expected this login failure message to go away and for people to be able to print. But again, only by editing the printer and clicking OK (not making any changes) could we get people printing. Is this normal? If so, how can I remotely fix people's CUPS settings? I don't want to keep visiting every station and running the printer config as root every time we have to change something. If it's not normal, what could be going wrong? Thanks, Matt
