I have gotten 'point-and-print' working, but there are a couple small issues/questions I am trying to get my grasp around: - rpcclient print-1201 -U root%secret -c 'enumdrivers' this lists the drivers twice (I saw one other post about this, without any followup) - When adding drivers via the Windows APW, after uploading the drivers and the APW closing - are you supposed to CANCEL out of the printers property window? If not, the printer on the server get renamed with how the driver wants to name it - When the above happens, I have only found the ability to delete the printer from windows, I have'n't found a rpcclient (or similar) to delete the printer (ie addprinter opposite) - Lastly, what happens _if_ two separate print drivers have a same file name? Everything gets tucked into the same directory?? Thank You - Chris
On Sun, 5 Sep 2004 15:07:59 -0500, Chris McKeever <techjedi@gmail.com> wrote:> I have gotten 'point-and-print' working, but there are a couple small > issues/questions I am trying to get my grasp around: > > - rpcclient print-1201 -U root%secret -c 'enumdrivers' > this lists the drivers twice (I saw one other post about this, > without any followup) > > - When adding drivers via the Windows APW, after uploading the drivers > and the APW closing - are you supposed to CANCEL out of the printers > property window? If not, the printer on the server get renamed with > how the driver wants to name it >I have figured out that if you dont apply, only the drivers are uploadined, but they are not associated with the printer - however, when I do hit OK or apply - the printer property window hangs (it does however do the association) - but it also changes the name of the printer to that of the driver in both enumprinters and \\sambaserver\printers -- but not as what it is shared as in \\sambaserver\original-sharename Is this hanging window preventable?> - When the above happens, I have only found the ability to delete the > printer from windows, I have'n't found a rpcclient (or similar) to > delete the printer (ie addprinter opposite) > > - Lastly, what happens _if_ two separate print drivers have a same > file name? Everything gets tucked into the same directory?? > > Thank You - > Chris >
On Mon, 6 Sep 2004 10:27:30 +1000, John Hewitt <johnblade@gmail.com> wrote:> What version of windows printer driver are you using? Are you using > the adobe drivers or the cups drivers? > I understand the current cups drivers have some big issues (hanging > windows, unable to print landscape) and the cups boys are dumping the > current code completely and writing from scratch for the new 6 > version. In the meantime using the adobe drivers is advisable. >I am using SAMBA/CUPS in the raw mode, so each of the printers has its own WINDOWS drivers --- I have been playing with this a bunch - it seems to work when selecting APPLY after uploading the drivers - it hangs for a little while, but eventually finishes and closes out the dialog box...I can also change the name of the printer via that dialog as well, and it changes it on the SAMBA server. How one deletes a printer from the command line, I am not sure, other than editing the smb.conf and removing the specific printer I am testing this with Windows 2000 - and notieced something rather strange..after installing the printer for two different accounts, if I go int oone and edit the preferences using an account with PRINT ADMIN priviledges, it actually updates the defaults on the other users preferences --- I dont know if this is just smoe strange things via TSRV. From the reading, it sounds like once the driver is installed, the server defaults are whatever it was set with at time of download (section 17.8 SAMBA HOWTO) -- it is very interesting ...> > > > On Sun, 5 Sep 2004 15:19:07 -0500, Chris McKeever <techjedi@gmail.com> wrote: > > On Sun, 5 Sep 2004 15:07:59 -0500, Chris McKeever <techjedi@gmail.com> wrote: > > > I have gotten 'point-and-print' working, but there are a couple small > > > issues/questions I am trying to get my grasp around: > > > > > > - rpcclient print-1201 -U root%secret -c 'enumdrivers' > > > this lists the drivers twice (I saw one other post about this, > > > without any followup) > > > > > > - When adding drivers via the Windows APW, after uploading the drivers > > > and the APW closing - are you supposed to CANCEL out of the printers > > > property window? If not, the printer on the server get renamed with > > > how the driver wants to name it > > > > > > > I have figured out that if you dont apply, only the drivers are > > uploadined, but they are not associated with the printer - however, > > when I do hit OK or apply - the printer property window hangs (it does > > however do the association) - but it also changes the name of the > > printer to that of the driver in both enumprinters and > > \\sambaserver\printers -- but not as what it is shared as in > > \\sambaserver\original-sharename > > > > Is this hanging window preventable? > > > > > > > > > > > - When the above happens, I have only found the ability to delete the > > > printer from windows, I have'n't found a rpcclient (or similar) to > > > delete the printer (ie addprinter opposite) > > > > > > - Lastly, what happens _if_ two separate print drivers have a same > > > file name? Everything gets tucked into the same directory?? > > > > > > Thank You - > > > Chris > > > > > -- > > To unsubscribe from this list go to the following URL and read the > > instructions: http://lists.samba.org/mailman/listinfo/samba > > >
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Chris McKeever wrote: | I have gotten 'point-and-print' working, but there are | a couple small issues/questions I am trying to get my | grasp around: | | - rpcclient print-1201 -U root%secret -c 'enumdrivers' | this lists the drivers twice Twice? or once for 'Windows 4.0' and once for "Windows NT x86'? | - When adding drivers via the Windows APW, after | uploading the drivers and the APW closing - are you | supposed to CANCEL out of the printers property window? If | not, the printer on the server get renamed with how the driver | wants to name it The Windows client is renaming the printer. You can just rename it again. | - When the above happens, I have only found the | ability to delete the printer from windows, I have'n't found | a rpcclient (or similar) to delete the printer | (ie addprinter opposite) There's not one currently i don't think. | - Lastly, what happens _if_ two separate print | drivers have a same file name? Everything gets tucked | into the same directory?? The is a problem in the Windows printing design. Yes there could be naming collisions, but most responsible driver writers manage their namespace to avoid this. cheer,s jerry - --------------------------------------------------------------------- Alleviating the pain of Windows(tm) ------- http://www.samba.org GnuPG Key ----- http://www.plainjoe.org/gpg_public.asc "If we're adding to the noise, turn off this song"--Switchfoot (2003) -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFBPErVIR7qMdg1EfYRAmeQAJ9UIJyhjvMwxi4lGla8xb4gq+cFUwCfbwbB ZBGQyqFfXVjqH+TX30U9Q+I=u/+x -----END PGP SIGNATURE-----
On Mon, 6 Sep 2004 14:50:39 +0530, sandeep.sundaram@wipro.com <sandeep.sundaram@wipro.com> wrote:> > Hi, > > >I am using SAMBA/CUPS in the raw mode, so each of the printers has its > own WINDOWS >.drivers --- > > >I have been playing with this a bunch - it seems to work when selecting > APPLY after > >uploading the drivers - it hangs for a little while, but eventually > finishes and closes > >out the dialog box... > > > One possible reason for this could be that the devmode information > (Printer specific) might not be available and hence you see that delay > in the Properties window closing. You could probably confirm this by > sniffing out the network packets.... You might see repeated "Open > Printer" and "Get Printer" calls. You might also see an increase in the > memory usage by the Samba daemons. >I ran an ethereal...granted this is one of the first times using it - I didnt seem to find anything as straight forward as what you said to look for. I did notice that the SMB daemon does crank up on its CPU load while the conversation is going on. I tried this all with an HP4 and it seemed to work much smoother - it was when I tried it with a TOSHIBA that is hangs. Almost 10 minutes waiting after uploading the DRIVER files and trying to close out of the window using APPLY .. any hints on ETHEREAL to packet sniff more telling, or why in general this hangs?? thanks> > >I am testing this with Windows 2000 - and notieced something rather > strange..after > >installing the printer for two different accounts, if I go int oone and > edit the > >preferences using an account with PRINT ADMIN priviledges, it actually > updates the > >defaults on the other users preferences > > Changes made to the printing defaults (Advanced Tab) will be reflected > on the other machines where the drivers have been downloaded. Changes > made to the printing preferences will be local to that machine only. > > The settings stored on the Samba server will be reflected in > "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows > NT\CurrentVersion\Print\Providers\LanMan Print Services\Servers" > > This is what you see when you invoke the Advanced properties. > > Sandy > > > > > -----Original Message----- > From: samba-bounces+sandeep.sundaram=wipro.com@lists.samba.org > [mailto:samba-bounces+sandeep.sundaram=wipro.com@lists.samba.org] On > Behalf Of Chris McKeever > Sent: Monday, September 06, 2004 6:08 AM > To: John Hewitt; samba@samba.org > Subject: Re: [Samba] Re: 'point-and-print' general questions > > On Mon, 6 Sep 2004 10:27:30 +1000, John Hewitt <johnblade@gmail.com> > wrote: > > What version of windows printer driver are you using? Are you using > > the adobe drivers or the cups drivers? I understand the current cups > > drivers have some big issues (hanging windows, unable to print > > landscape) and the cups boys are dumping the current code completely > > and writing from scratch for the new 6 version. In the meantime using > > > the adobe drivers is advisable. > > > > I am using SAMBA/CUPS in the raw mode, so each of the printers has its > own WINDOWS drivers --- > > I have been playing with this a bunch - it seems to work when selecting > APPLY after uploading the drivers - it hangs for a little while, but > eventually finishes and closes out the dialog box...I can also change > the name of the printer via that dialog as well, and it changes it on > the SAMBA server. How one deletes a printer from the command line, I am > not sure, other than editing the smb.conf and removing the specific > printer > > I am testing this with Windows 2000 - and notieced something rather > strange..after installing the printer for two different accounts, if I > go int oone and edit the preferences using an account with PRINT ADMIN > priviledges, it actually updates the defaults on the other users > preferences --- I dont know if this is just smoe strange things via > TSRV. From the reading, it sounds like once the driver is installed, > the server defaults are whatever it was set with at time of download > (section 17.8 SAMBA HOWTO) -- it is very interesting ... > > > > > > > > > On Sun, 5 Sep 2004 15:19:07 -0500, Chris McKeever <techjedi@gmail.com> > > > wrote: > > > On Sun, 5 Sep 2004 15:07:59 -0500, Chris McKeever > > > <techjedi@gmail.com> wrote: > > > > I have gotten 'point-and-print' working, but there are a couple > > > > small issues/questions I am trying to get my grasp around: > > > > > > > > - rpcclient print-1201 -U root%secret -c 'enumdrivers' > > > > this lists the drivers twice (I saw one other post about this, > > > > without any followup) > > > > > > > > - When adding drivers via the Windows APW, after uploading the > > > > drivers and the APW closing - are you supposed to CANCEL out of > > > > the printers property window? If not, the printer on the server > > > > get renamed with how the driver wants to name it > > > > > > > > > > I have figured out that if you dont apply, only the drivers are > > > uploadined, but they are not associated with the printer - however, > > > when I do hit OK or apply - the printer property window hangs (it > > > does however do the association) - but it also changes the name of > > > the printer to that of the driver in both enumprinters and > > > \\sambaserver\printers -- but not as what it is shared as in > > > \\sambaserver\original-sharename > > > > > > Is this hanging window preventable? > > > > > > > > > > > > > > > > - When the above happens, I have only found the ability to delete > > > > the printer from windows, I have'n't found a rpcclient (or > > > > similar) to delete the printer (ie addprinter opposite) > > > > > > > > - Lastly, what happens _if_ two separate print drivers have a same > > > > > file name? Everything gets tucked into the same directory?? > > > > > > > > Thank You - > > > > Chris > > > > > > > -- > > > To unsubscribe from this list go to the following URL and read the > > > instructions: http://lists.samba.org/mailman/listinfo/samba > > > > > > -- > To unsubscribe from this list go to the following URL and read the > instructions: http://lists.samba.org/mailman/listinfo/samba > > > Confidentiality Notice > > The information contained in this electronic message and any attachments to this message are intended > for the exclusive use of the addressee(s) and may contain confidential or privileged information. If > you are not the intended recipient, please notify the sender at Wipro or Mailadmin@wipro.com immediately > and destroy all copies of this message and any attachments. >
sandeep.sundaram@wipro.com
2004-Sep-08 07:23 UTC
[Samba] Re: 'point-and-print' general questions
Chris, Ethereal might show it to you as packets from the "SPOOLSS" protocol or as "DCERPC" packets. If it shows as SPOOLSS, then you would be able to see the "OpenPrinter" and "GetPrinter" calls. On the other hand, if the packets are displayed as DCERPC calls, then you should be looking at the "Opnum". 69 -> OpenPrinter 8 -> GetPrinter 29 -> ClosePrinter. If you are able to see these repeatedly, on clicking the APPLY button, then it *COULD* be a problem with the entries in the TDB file. (or rather the lack of entries...) As you have already gathered, this is specific to certain drivers.. Mainly due to the way they have been designed / coded. Some drivers are dependent on the correct "Private Devmode" data to be given by the Printer server (Samba in our case). The Private devmode is data pertaining to the capabilities of the driver and hence there is no standard / specifications attributed to this (AFAIK !!). So, if this data is not available or is incomplete then some of the drivers go into an insane loop of querying the server for these settings. I have noticed this while downloading the drivers. I had used the rpcclient utility to upload the drivers on to the Samba server. After downloading, some times the property window used to take ages to come up. Even on clicking the Apply button, it used to take about 10 minutes for the UI to close. But this was only on the first or second download. Once the entries were made in the TDB, everything worked smoothly. One possible work around for this is to use the rpcclient tool with the "SetPrinter" and "SetPrinterData" commands, provided you already know what entries need to be set. This will demand a small tweak in the rpcclient sources. Would like to know which series of TOSHIBA drivers are causing this problem. Regards, Sandy -----Original Message----- From: Chris McKeever [mailto:techjedi@gmail.com] Sent: Wednesday, September 08, 2004 7:56 AM To: Sandeep Sundaram (WT01 - EMBEDDED & PRODUCT ENGINEERING SOLUTIONS); samba@samba.org Subject: Re: [Samba] Re: 'point-and-print' general questions On Mon, 6 Sep 2004 14:50:39 +0530, sandeep.sundaram@wipro.com <sandeep.sundaram@wipro.com> wrote:> > Hi, > > >I am using SAMBA/CUPS in the raw mode, so each of the printers has > >its > own WINDOWS >.drivers --- > > >I have been playing with this a bunch - it seems to work when > >selecting > APPLY after > >uploading the drivers - it hangs for a little while, but eventually > finishes and closes > >out the dialog box... > > > One possible reason for this could be that the devmode information > (Printer specific) might not be available and hence you see that delay> in the Properties window closing. You could probably confirm this by > sniffing out the network packets.... You might see repeated "Open > Printer" and "Get Printer" calls. You might also see an increase in > the memory usage by the Samba daemons. >I ran an ethereal...granted this is one of the first times using it - I didnt seem to find anything as straight forward as what you said to look for. I did notice that the SMB daemon does crank up on its CPU load while the conversation is going on. I tried this all with an HP4 and it seemed to work much smoother - it was when I tried it with a TOSHIBA that is hangs. Almost 10 minutes waiting after uploading the DRIVER files and trying to close out of the window using APPLY .. any hints on ETHEREAL to packet sniff more telling, or why in general this hangs?? thanks> > >I am testing this with Windows 2000 - and notieced something rather > strange..after > >installing the printer for two different accounts, if I go int oone > >and > edit the > >preferences using an account with PRINT ADMIN priviledges, it > >actually > updates the > >defaults on the other users preferences > > Changes made to the printing defaults (Advanced Tab) will be reflected> on the other machines where the drivers have been downloaded. Changes > made to the printing preferences will be local to that machine only. > > The settings stored on the Samba server will be reflected in > "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows > NT\CurrentVersion\Print\Providers\LanMan Print Services\Servers" > > This is what you see when you invoke the Advanced properties. > > Sandy > > > > > -----Original Message----- > From: samba-bounces+sandeep.sundaram=wipro.com@lists.samba.org > [mailto:samba-bounces+sandeep.sundaram=wipro.com@lists.samba.org] On > Behalf Of Chris McKeever > Sent: Monday, September 06, 2004 6:08 AM > To: John Hewitt; samba@samba.org > Subject: Re: [Samba] Re: 'point-and-print' general questions > > On Mon, 6 Sep 2004 10:27:30 +1000, John Hewitt <johnblade@gmail.com> > wrote: > > What version of windows printer driver are you using? Are you using> > the adobe drivers or the cups drivers? I understand the current cups> > drivers have some big issues (hanging windows, unable to print > > landscape) and the cups boys are dumping the current code completely> > and writing from scratch for the new 6 version. In the meantime > > using > > > the adobe drivers is advisable. > > > > I am using SAMBA/CUPS in the raw mode, so each of the printers has its> own WINDOWS drivers --- > > I have been playing with this a bunch - it seems to work when > selecting APPLY after uploading the drivers - it hangs for a little > while, but eventually finishes and closes out the dialog box...I can > also change the name of the printer via that dialog as well, and it > changes it on the SAMBA server. How one deletes a printer from the > command line, I am not sure, other than editing the smb.conf and > removing the specific printer > > I am testing this with Windows 2000 - and notieced something rather > strange..after installing the printer for two different accounts, if I> go int oone and edit the preferences using an account with PRINT ADMIN> priviledges, it actually updates the defaults on the other users > preferences --- I dont know if this is just smoe strange things via > TSRV. From the reading, it sounds like once the driver is installed, > the server defaults are whatever it was set with at time of download > (section 17.8 SAMBA HOWTO) -- it is very interesting ... > > > > > > > > > On Sun, 5 Sep 2004 15:19:07 -0500, Chris McKeever > > <techjedi@gmail.com> > > > wrote: > > > On Sun, 5 Sep 2004 15:07:59 -0500, Chris McKeever > > > <techjedi@gmail.com> wrote: > > > > I have gotten 'point-and-print' working, but there are a couple > > > > small issues/questions I am trying to get my grasp around: > > > > > > > > - rpcclient print-1201 -U root%secret -c 'enumdrivers' > > > > this lists the drivers twice (I saw one other post about this,> > > > without any followup) > > > > > > > > - When adding drivers via the Windows APW, after uploading the > > > > drivers and the APW closing - are you supposed to CANCEL out of > > > > the printers property window? If not, the printer on the server> > > > get renamed with how the driver wants to name it > > > > > > > > > > I have figured out that if you dont apply, only the drivers are > > > uploadined, but they are not associated with the printer - > > > however, when I do hit OK or apply - the printer property window > > > hangs (it does however do the association) - but it also changes > > > the name of the printer to that of the driver in both enumprinters> > > and \\sambaserver\printers -- but not as what it is shared as in > > > \\sambaserver\original-sharename > > > > > > Is this hanging window preventable? > > > > > > > > > > > > > > > > - When the above happens, I have only found the ability to > > > > delete the printer from windows, I have'n't found a rpcclient > > > > (or > > > > similar) to delete the printer (ie addprinter opposite) > > > > > > > > - Lastly, what happens _if_ two separate print drivers have a > > > > same > > > > > file name? Everything gets tucked into the same directory?? > > > > > > > > Thank You - > > > > Chris > > > > > > > -- > > > To unsubscribe from this list go to the following URL and read the > > > instructions: http://lists.samba.org/mailman/listinfo/samba > > > > > > -- > To unsubscribe from this list go to the following URL and read the > instructions: http://lists.samba.org/mailman/listinfo/samba > > > Confidentiality Notice > > The information contained in this electronic message and any > attachments to this message are intended for the exclusive use of the > addressee(s) and may contain confidential or privileged information. > If you are not the intended recipient, please notify the sender at > Wipro or Mailadmin@wipro.com immediately and destroy all copies of > this message and any attachments. >Confidentiality Notice The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain confidential or privileged information. If you are not the intended recipient, please notify the sender at Wipro or Mailadmin@wipro.com immediately and destroy all copies of this message and any attachments.