RE: [Samba] Cannot enable Enable advanced printing features
Hi, As far as my understanding goes, the EMF is more of a data type support for printing. In Samba's case, this will never hold good, since it is always defaulted to the RAW data type. The Enable Advanced printing features is more to do with the attributes. The Spool sub system on windows uses certain printer related structures, whose values are reflected in the printer properties UI. The attributes is one such value, which actually holds the value for the Enable Advanced printing features. I am not sure whether Samba is defaulting this to some value. Will have to get into the code for that. But what ever I have noticed with Windows specific printer drivers are that the attributes typically take a value of 0x0xxx when the Enable Advanced printing features is selected. But when this is not checked, the value is 0x1xxx. I guess you can enable the debug level (set to 10) and specifically search for the attributes in the log and see the value. If this is the case, we can maybe think on lines of changing that particular entry in the tdb file. Regards, Sandy -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Manuel Capinha Sent: Tuesday, September 28, 2004 3:12 PM To: Pierre Dinh-van Cc: [EMAIL PROTECTED] Subject: Re: [Samba] Cannot enable Enable advanced printing features Hey. I've just been bitten by the same problem recently. What happens is that when you click on the Enable advanced printer features option on windows, what it does is enable EMF support. EMF works by letting the printer driver embbed some printer commands that will be executed by the print server. For this to work, the print server must be running on Windows, since cups+samba don't do EMF (and from what i've gathered this will _never_ work). I'm currently investigating if there's some other way to achieve the n-pages-to-1 print option under the cups+samba combo... this will have to go through some sort of filter on the cups backend but all of this is still a sketch in my head.. Hope this helps. On Tue, 28 Sep 2004 11:22:20 +0200, Pierre Dinh-van [EMAIL PROTECTED] wrote: Le mardi 28 Septembre 2004 11:15, Kent B. Hansen a écrit : Hi all. Hi I'm trying to use Samba to replace an old Windows print server, and everything works just like a charm - almost... There's one thing, which prevents my organization from accepting this new printerserver, and that is that I'm unable to activate and save the Enable advanced printing features setting for the printers - this is used to allow for printing multiple pages onto one page etc. Samba doesn't give any errors, the settings is just cleared the next time I open the preferences... I have the same problem with a Xerox DocuColor 1632. When the driver is downloaded by the client from the print$ share, I can't activate the finition module of the printer. If I install the printer driver locally by hand, it works... I'm still looking for a solution... I'm using cups for the backend, and all printers are configured as raw queues. The click'n'print feature are working nicely, and I can change and save all other settings beside this crusual advanced features setting (so it doesn't seem like a persission problem). Same configuration... I hope someone can help us :-) Pierre Dinh-van -- --- Racisme --- Le casse-tête de Toubon : comment pondre une loi anti-raciste qui n'envoie pas Debré en prison ? +-- Brèves Charlie Hebdo n°223 (25/09/96) --+ -- 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 [EMAIL PROTECTED] immediately and destroy all copies of this message and any attachments. -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
RE: [Samba] ADS membership with Samba 3.0.4
Hi, Thanks for that information. So, now if I am to include Winbind, I would like to know what other system libraries (Linux based) winbind uses. The deciding factor now would be on how easy or tough it would be to get these libraries running on some thing like VxWorks. As far as I remember, in the 2.2.x series, if Samba was configured with security = DOMAIN, then smbd would connect to the password server / PDC and get the user authenticated. Is there any way I can configure the 3.x series to do this ?!! Even if I can get a small hint, pointing to the code I need to touch upon, I can take it up from there. I have seen this kind of a code in the auth_domain.c file. But I'm not sure how to configure Samba, with security set to ADS, to get to use this mechanism. Would really appreciate it if some one could help me out on this. Thanks and Regards, Sandy -Original Message- From: Christoph Scheeder [mailto:[EMAIL PROTECTED] Sent: Wednesday, August 11, 2004 12:43 PM To: Sandeep Sundaram (WT01 - EMBEDDED PRODUCT ENGINEERING SOLUTIONS) Cc: [EMAIL PROTECTED] Subject: Re: [Samba] ADS membership with Samba 3.0.4 Hi, 1.) Yes you definitly need the winbind/nss stuff, as it is the part of samba that does what you want: ask an ADS server to verify the credentials a user supplys when logging in to samba. 2.) no, it is not sufficient. But you need a working Kerberos library to get winbind to work. Christoph [EMAIL PROTECTED] schrieb: Hi, We are in the process of evaluating the possibility of porting Samba 3.0.4 to VxWorks. Features wise we don't see any problems. But our main concern is on the security. Since we do not have the concept of Users and Groups on VxWorks, we cannot have any authentications as such. So, the other possibility is to pass on the authentication to another Server on the network, typically a AD server (since Samba is required to be a part of a domain) All the documents that we have seen so far, regarding the ADS membership, talk about winbind and NSS. My question here is, 1. Do I really need winbind or NSS since I am not maintaining any Users or Groups locally ?! 2. Is it sufficient if I get the Kerberos and sasl support to work on VxWorks ?! Regards, Sandeep Sundaram 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 [EMAIL PROTECTED] 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 [EMAIL PROTECTED] immediately and destroy all copies of this message and any attachments. -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
RE: [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:[EMAIL PROTECTED] Sent: Wednesday, September 08, 2004 7:56 AM To: Sandeep Sundaram (WT01 - EMBEDDED PRODUCT ENGINEERING SOLUTIONS); [EMAIL PROTECTED] Subject: Re: [Samba] Re: 'point-and-print' general questions On Mon, 6 Sep 2004 14:50:39 +0530, [EMAIL PROTECTED] [EMAIL PROTECTED] 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: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Chris McKeever Sent: Monday, September 06, 2004 6:08 AM To: John Hewitt; [EMAIL PROTECTED] Subject: Re: [Samba] Re: 'point-and-print' general questions On Mon, 6 Sep 2004 10:27:30 +1000, John Hewitt [EMAIL PROTECTED] 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
[Samba] ADS membership with Samba 3.0.4
Hi, We are in the process of evaluating the possibility of porting Samba 3.0.4 to VxWorks. Features wise we don't see any problems. But our main concern is on the security. Since we do not have the concept of Users and Groups on VxWorks, we cannot have any authentications as such. So, the other possibility is to pass on the authentication to another Server on the network, typically a AD server (since Samba is required to be a part of a domain) All the documents that we have seen so far, regarding the ADS membership, talk about winbind and NSS. My question here is, 1. Do I really need winbind or NSS since I am not maintaining any Users or Groups locally ?! 2. Is it sufficient if I get the Kerberos and sasl support to work on VxWorks ?! Regards, Sandeep Sundaram 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 [EMAIL PROTECTED] immediately and destroy all copies of this message and any attachments. -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
