[Samba] Re: 'point-and-print' general questions

[Chris McKeever]

On Wed, 8 Sep 2004 12:53:16 +0530, sandeep.sundaram at wipro.com
<sandeep.sundaram at wipro.com> wrote:
> 

> 
> Would like to know which series of TOSHIBA drivers are causing this
> problem.
> 

so - anyone know why they are listed twice?

'enumdrivers'

[Windows NT x86]
Printer Driver Info 1:
        Driver Name: [TOSHIBA e-STUDIO810 srs-PS3UC]

Printer Driver Info 1:
        Driver Name: [HP LaserJet 4]


[Windows NT x86]
Printer Driver Info 1:
        Driver Name: [TOSHIBA e-STUDIO810 srs-PS3UC]

Printer Driver Info 1:
        Driver Name: [HP LaserJet 4]



> Regards,
> Sandy
> 
> 
> 
> 
> -----Original Message-----
> From: Chris McKeever [mailto:techjedi at gmail.com]
> Sent: Wednesday, September 08, 2004 7:56 AM
> To: Sandeep Sundaram (WT01 - EMBEDDED & PRODUCT ENGINEERING SOLUTIONS);
> samba at samba.org
> Subject: Re: [Samba] Re: 'point-and-print' general questions
> 
> On Mon, 6 Sep 2004 14:50:39 +0530, sandeep.sundaram at wipro.com
> <sandeep.sundaram at 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 at lists.samba.org
> > [mailto:samba-bounces+sandeep.sundaram=wipro.com at lists.samba.org] On
> > Behalf Of Chris McKeever
> > Sent: Monday, September 06, 2004 6:08 AM
> > To: John Hewitt; samba at samba.org
> > Subject: Re: [Samba] Re: 'point-and-print' general questions
> >
> > On Mon, 6 Sep 2004 10:27:30 +1000, John Hewitt <johnblade at 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 at gmail.com>
> >
> > > wrote:
> > > > On Sun, 5 Sep 2004 15:07:59 -0500, Chris McKeever
> > > > <techjedi at 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 at 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 at wipro.com immediately
> and destroy all copies of this message and any attachments.
>