Re: [Samba] W9x print driver download problems with Samba 2.2.3a and CUPS
Found the thread on the CUPS ng, applied the patch at http://www.cups.org/newsgroups.php?s1+gcups.bugs+v3. Now 9x errors out with 'No more files (error #12)' while copying the ppd. Oddly, it seems to get to the end of the list of files while copying. I think this is the last stumbling block before everything works, any ideas? David Morel ([EMAIL PROTECTED]) wrote: > of CUPS are you using (and which platform?) if you see > > this? > > > > Could you post this to the CUPS mailing list at www.cups.org, please, > > if it still prevails after upgrading CUPS (or ripping off a "cupsaddsmb" > > binary from a more current CUPS installation)? > > > > > > checked the cups ng, it says it'll be fixed for 1.1.16 > > David > > > -- > To unsubscribe from this list go to the following URL and read the > instructions: http://lists.samba.org/mailman/listinfo/samba -- Adam Glasgall Disobedience was Man's Original Virtue msg05345/pgp0.pgp Description: PGP signature
Re: [Samba] W9x print driver download problems with Samba 2.2.3a and CUPS
On Sun, 29 Sep 2002 14:09:19 -0400, Adam Glasgall <[EMAIL PROTECTED]> wrote: >I've set up Samba and CUPS on our testing server here, and used >smbcupsadd to upload the Adobe PS drivers to the server as directed in >Win9x is another story altogether. It's clearly trying to get the >drivers from the server, but at the beginning of the process, it pops up run cupsaddsmb with "-v". You'll probably see that it mistakenly uses smbclient in place of rpcclient when setting up win9x drivers and fails. You can do it by hand seeing what's trying to do or wait for release of cups-1.1.16 which solves this. -- [EMAIL PROTECTED] -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] W9x print driver download problems with Samba 2.2.3a and CUPS
Curioser and curioser, running the exact same rpcclient command which
cupsaddsmb runs :
rpcclient localhost -N -U'root%' -c 'adddriver "Windows 4.0"
":ADOBEPS4.DRV:.PPD:NULL:ADOBEPS4.HLP:PSMON.DLL:RAW:ADFONTS.MFM,DEFPRTR2.PPD,ICONLIB.DLL"
results in:
result was NT_STATUS_INVALID_LOCK_SEQUENCE
with debuglevel 2. Going to debuglevel 3 doesn't increase verbosity to
any extent.
I'm thinking this is a serious bug in Samba 2.2.3a, I'm wondering why on
earth Samba 2.2.5 or at least 2.2.4 hasn't made it into Debian testing
(at least!) yet, and I'm trying 2.2.5 tomorrow.
Adam Glasgall ([EMAIL PROTECTED]) wrote:
> Kurt Pfeifle ([EMAIL PROTECTED]) wrote:
> > Glasgall wrote on samba-digest:
> >
> > >Message: 3
> > >Date: Sun, 29 Sep 2002 14:09:19 -0400
> > >From: Adam Glasgall <[EMAIL PROTECTED]>
> > >To: [EMAIL PROTECTED]
> > >Subject: [Samba] W9x print driver download problems with Samba 2.2.3a and
> > >CUPS
> > >
> > >
> > >--JgQwtEuHJzHdouWu
> > >Content-Type: text/plain; charset=us-ascii
> > >Content-Disposition: inline
> > >Content-Transfer-Encoding: quoted-printable
> > >
> > >I've set up Samba and CUPS on our testing server here, and used
> > >smbcupsadd to upload the Adobe PS drivers to the server as directed in
> > >the HOWTO (The CUPS and Samba HOWTOs differ on this point, by the way -
> > >the latter claims that PSMON.DLL is needed in addition to the eight
> > >other files.
> >
> > You are right, somehow this got lost in the Samba HOWTO Collection and
> > should be listed.
> >
> > >I played it safe and had it upload that, too).
> > >With the caveat that I first have to connect to each printer on a w2k
> > >machine and select the driver from the list manually (driver is clearly
> > >installed, just not associated with the printer - rpcclient setdriver
> > >will probably do it, too, I guess), printing from win2k machines works
> > >perfectly - drivers get autodownloaded and everything Just Works.
> > >
> > >Win9x is another story altogether. It's clearly trying to get the
> > >drivers from the server, but at the beginning of the process, it pops up
> > >a box asking for a file whose name is one unprintable character -
> > >Windows prints it as a bold vertical bar in the box. It IS looking in
> > >the right place (\\\print$\win40\0), but, clearly, the file
> > >isn't there,
> >
> > Are you saying there is no content in /WIN40/0/
> > at all?
> WIN40/0 is fully populated with the Adobe PS drivers and the PPDs.
>
> > >and it's certainly not trying to get the right file.
> > >Watching communications between the two machines with ethereal yielded
> > >no useful information.
> > >What's going on here?
> >
> > I guess your "cupsaddsmb" command didn't work as intended. Try to run
> > it again. Use the "-v" parameter for verbose output. Are you seeing the
> > line
> >
> > "Printer Driver successfully installed."
> >
> > *twice* (once for each architecture, W32X86 [=WinNT/2K/XP], and WIN40
> > [=Win9x]) ?
> Yes, the drivers for both NT and 9x get installed right.
> > Are you seeing a line of
> >
> > "Succesfully set to driver ."
> >
> > at the end?
> >
> > If any of the "rpcclient adddriver|setdriver" commands fails (they are
> > printed by the "-v" output of cupsaddsmb), you can try to run them
> > manually from the console, with debuglevel increased ("-d 3" or "-d 5")
> > to troubleshoot this...
> Oddly, rpcclient setdriver doesn't seem to be run at all during the
> process. I suspect this to be a bug in the version of cupsaddsmb.
> I've run it manually, and I'll test when I get into the office today.
> More later.
> > My final advice: Upgrade 2.2.3a to the latest 2.2.5 (with additional
> > print patches applied as to the advices on the website) or to 2.2.6 if
> > it is released
> Yes, that is my next planned step. It's complicated somewhat by the fact
> that our servers here run Debian stable, and the versions of Samba and
> CUPS in that are both rather elderly...well, I'll try and see if that
> fixes matters.
> >
> > >Adam Glasgall
> >
> > Cheers,
> > Kurt
> >
> > --
> > To unsubscribe from this list go to the following URL and read the
> > instructions: http://lists.samba.org/mailman/listinfo/samba
>
> --
> Adam Glasgall
> Disobedience was Man's Original Virtue
--
Adam Glasgall
Disobedience was Man's Original Virtue
msg05277/pgp0.pgp
Description: PGP signature
Re: [Samba] W9x print driver download problems with Samba 2.2.3a and CUPS
Kurt Pfeifle ([EMAIL PROTECTED]) wrote:
> Glasgall wrote on samba-digest:
>
> >Message: 3
> >Date: Sun, 29 Sep 2002 14:09:19 -0400
> >From: Adam Glasgall <[EMAIL PROTECTED]>
> >To: [EMAIL PROTECTED]
> >Subject: [Samba] W9x print driver download problems with Samba 2.2.3a and
> >CUPS
> >
> >
> >--JgQwtEuHJzHdouWu
> >Content-Type: text/plain; charset=us-ascii
> >Content-Disposition: inline
> >Content-Transfer-Encoding: quoted-printable
> >
> >I've set up Samba and CUPS on our testing server here, and used
> >smbcupsadd to upload the Adobe PS drivers to the server as directed in
> >the HOWTO (The CUPS and Samba HOWTOs differ on this point, by the way -
> >the latter claims that PSMON.DLL is needed in addition to the eight
> >other files.
>
> You are right, somehow this got lost in the Samba HOWTO Collection and
> should be listed.
>
> >I played it safe and had it upload that, too).
> >With the caveat that I first have to connect to each printer on a w2k
> >machine and select the driver from the list manually (driver is clearly
> >installed, just not associated with the printer - rpcclient setdriver
> >will probably do it, too, I guess), printing from win2k machines works
> >perfectly - drivers get autodownloaded and everything Just Works.
> >
> >Win9x is another story altogether. It's clearly trying to get the
> >drivers from the server, but at the beginning of the process, it pops up
> >a box asking for a file whose name is one unprintable character -
> >Windows prints it as a bold vertical bar in the box. It IS looking in
> >the right place (\\\print$\win40\0), but, clearly, the file
> >isn't there,
>
> Are you saying there is no content in /WIN40/0/
> at all?
WIN40/0 is fully populated with the Adobe PS drivers and the PPDs.
> >and it's certainly not trying to get the right file.
> >Watching communications between the two machines with ethereal yielded
> >no useful information.
> >What's going on here?
>
> I guess your "cupsaddsmb" command didn't work as intended. Try to run
> it again. Use the "-v" parameter for verbose output. Are you seeing the
> line
>
> "Printer Driver successfully installed."
>
> *twice* (once for each architecture, W32X86 [=WinNT/2K/XP], and WIN40
> [=Win9x]) ?
Yes, the drivers for both NT and 9x get installed right.
> Are you seeing a line of
>
> "Succesfully set to driver ."
>
> at the end?
>
> If any of the "rpcclient adddriver|setdriver" commands fails (they are
> printed by the "-v" output of cupsaddsmb), you can try to run them
> manually from the console, with debuglevel increased ("-d 3" or "-d 5")
> to troubleshoot this...
Oddly, rpcclient setdriver doesn't seem to be run at all during the
process. I suspect this to be a bug in the version of cupsaddsmb.
I've run it manually, and I'll test when I get into the office today.
More later.
> My final advice: Upgrade 2.2.3a to the latest 2.2.5 (with additional
> print patches applied as to the advices on the website) or to 2.2.6 if
> it is released
Yes, that is my next planned step. It's complicated somewhat by the fact
that our servers here run Debian stable, and the versions of Samba and
CUPS in that are both rather elderly...well, I'll try and see if that
fixes matters.
>
> >Adam Glasgall
>
> Cheers,
> Kurt
>
> --
> To unsubscribe from this list go to the following URL and read the
> instructions: http://lists.samba.org/mailman/listinfo/samba
--
Adam Glasgall
Disobedience was Man's Original Virtue
msg05241/pgp0.pgp
Description: PGP signature
Re: [Samba] W9x print driver download problems with Samba 2.2.3a and CUPS
David Morel wrote: > Le lun 30/09/2002 à 12:53, Kurt Pfeifle a écrit : > >>Glasgall wrote on samba-digest: >> >> >>>Message: 3 >>>Date: Sun, 29 Sep 2002 14:09:19 -0400 >>>From: Adam Glasgall <[EMAIL PROTECTED]> >>>To: [EMAIL PROTECTED] >>>Subject: [Samba] W9x print driver download problems with Samba 2.2.3a and CUPS >>> >>> >>>--JgQwtEuHJzHdouWu >>>Content-Type: text/plain; charset=us-ascii >>>Content-Disposition: inline >>>Content-Transfer-Encoding: quoted-printable >>> >>>I've set up Samba and CUPS on our testing server here, and used >>>smbcupsadd to upload the Adobe PS drivers to the server as directed in >>>the HOWTO (The CUPS and Samba HOWTOs differ on this point, by the way - >>>the latter claims that PSMON.DLL is needed in addition to the eight >>>other files. >>> > > would it be related to : > > http://bugs.samba.org/cgi-bin/samba-bugs/incoming?id=25090 > > by any chance ? I guess so. You mean the *wrong* command rpcclient localhost -N -U'root%pass' -c 'adddriver "Windows 4.0" "printer_name:ADOBEPS4.DRV:printer_name.PPD: NULL:ADOBEPS4.HLP:PSMON.DLL:RAW: ADFONTS.MFM,DEFPRTR2.PPD,ICONLIB.DLL" is sent for you instead of the *right* one rpcclient localhost -N -U'root%pass' -c 'adddriver "Windows 4.0" "printer_name:ADOBEPS4.DRV:printer_name.PPD: NULL:ADOBEPS4.HLP:PSMON.DLL:RAW: ADOBEPS4.DRV: ADFONTS.MFM,DEFPRTR2.PPD,ICONLIB.DLL" But this looks not like a Samba bug; it is rather "cupsaddsmb" duing the wrong thing. "cupsaddsmb" is basing itself on "rpcclient" and the sole responsible source for issuing the parameters which are handed to "rpcclient". Anyway, I am *not* seeing this with my last few versions of cupsaddsmb. Likely, this is fixed *long* ago. Which version of CUPS are you using (and which platform?) if you see this? Could you post this to the CUPS mailing list at www.cups.org, please, if it still prevails after upgrading CUPS (or ripping off a "cupsaddsmb" binary from a more current CUPS installation)? -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] W9x print driver download problems with Samba 2.2.3a and CUPS
Glasgall wrote on samba-digest:
> Message: 3
> Date: Sun, 29 Sep 2002 14:09:19 -0400
> From: Adam Glasgall <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED]
> Subject: [Samba] W9x print driver download problems with Samba 2.2.3a and CUPS
>
>
> --JgQwtEuHJzHdouWu
> Content-Type: text/plain; charset=us-ascii
> Content-Disposition: inline
> Content-Transfer-Encoding: quoted-printable
>
> I've set up Samba and CUPS on our testing server here, and used
> smbcupsadd to upload the Adobe PS drivers to the server as directed in
> the HOWTO (The CUPS and Samba HOWTOs differ on this point, by the way -
> the latter claims that PSMON.DLL is needed in addition to the eight
> other files.
You are right, somehow this got lost in the Samba HOWTO Collection and
should be listed.
> I played it safe and had it upload that, too).
> With the caveat that I first have to connect to each printer on a w2k
> machine and select the driver from the list manually (driver is clearly
> installed, just not associated with the printer - rpcclient setdriver
> will probably do it, too, I guess), printing from win2k machines works
> perfectly - drivers get autodownloaded and everything Just Works.
>
> Win9x is another story altogether. It's clearly trying to get the
> drivers from the server, but at the beginning of the process, it pops up
> a box asking for a file whose name is one unprintable character -
> Windows prints it as a bold vertical bar in the box. It IS looking in
> the right place (\\\print$\win40\0), but, clearly, the file
> isn't there,
Are you saying there is no content in /WIN40/0/
at all?
> and it's certainly not trying to get the right file.
> Watching communications between the two machines with ethereal yielded
> no useful information.
> What's going on here?
I guess your "cupsaddsmb" command didn't work as intended. Try to run
it again. Use the "-v" parameter for verbose output. Are you seeing the
line
"Printer Driver successfully installed."
*twice* (once for each architecture, W32X86 [=WinNT/2K/XP], and WIN40
[=Win9x]) ?
Are you seeing a line of
"Succesfully set to driver ."
at the end?
If any of the "rpcclient adddriver|setdriver" commands fails (they are
printed by the "-v" output of cupsaddsmb), you can try to run them
manually from the console, with debuglevel increased ("-d 3" or "-d 5")
to troubleshoot this...
My final advice: Upgrade 2.2.3a to the latest 2.2.5 (with additional
print patches applied as to the advices on the website) or to 2.2.6 if
it is released
> Adam Glasgall
Cheers,
Kurt
--
To unsubscribe from this list go to the following URL and read the
instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] W9x print driver download problems with Samba 2.2.3a and CUPS
I've set up Samba and CUPS on our testing server here, and used smbcupsadd to upload the Adobe PS drivers to the server as directed in the HOWTO (The CUPS and Samba HOWTOs differ on this point, by the way - the latter claims that PSMON.DLL is needed in addition to the eight other files. I played it safe and had it upload that, too). With the caveat that I first have to connect to each printer on a w2k machine and select the driver from the list manually (driver is clearly installed, just not associated with the printer - rpcclient setdriver will probably do it, too, I guess), printing from win2k machines works perfectly - drivers get autodownloaded and everything Just Works. Win9x is another story altogether. It's clearly trying to get the drivers from the server, but at the beginning of the process, it pops up a box asking for a file whose name is one unprintable character - Windows prints it as a bold vertical bar in the box. It IS looking in the right place (\\\print$\win40\0), but, clearly, the file isn't there, and it's certainly not trying to get the right file. Watching communications between the two machines with ethereal yielded no useful information. What's going on here? -- Adam Glasgall Disobedience was Man's Original Virtue msg05163/pgp0.pgp Description: PGP signature
