search for: nickp

Hello all, I've got a strange problem with Samba 2.2.4. I'm able to associate print drivers to printers (raw queue in cups). My clients are able to see that the drivers belong to the printers, and they download them, but as soon as the server reboots, I lose my driver associations and I need to once again specify a driver on the windows end. The Print server was an upgrade from Samba

------- Forwarded message follows ------- Subject: Re: [Samba] Ack! No Answer for my Printer Troubles? From: Nick Pietraniec <nickp@campbellco.com> To: Christian Barth <barth@cck.uni-kl.de> Date sent: 15 Feb 2002 11:09:00 -0500 On Fri, 2002-02-15 at 10:59, Christian Barth wrote: > > I'm hoping my desperate post yesterday just didn't make it across. Does > > anyone have any sugge...

There seems to be some discrepancy between rpcclient's man page and "rpcclient --help" in regards to the servername. It seems that the proper usage of rpcclient is rpcclient [options] server this is the format that is specified in "rpcclient --help." rpcclient's man page, however specifies that the servername should come directly after rpcclient. I.E.

Samba version 2.2.3a doesn't seem to work with the "cupsaddsmb" program available in CUPS... cupsaddsmb merely runs a few rpcclient commands. The verbose output from cupsaddsmb is printed below. This output is from cups version 1.1.14, but I received the same error from version 1.1.12. On 2 different computers - both clean installs. When run on Samba version 2.2.2, the command

Hello all, I'm trying to use CUPSADDSMB to add some printer shares. Using the verbose output, everything looks good except the following line. session setup ok Domain=[WHEELZ] OS=[Unix] Server=[Samba 2.2.3a] cmd = addprinter kubrick_linux kubrick_linux "kubrick_linux" "" addprinter kubrick_linux kubrick_linux "kubrick_linux" "" result was NT code