similar to: Problems with SPOOLSS WinNT driver uploads

With XP client printer, when choosing Printer Properties the following error follows, I use samba 3.0.9, 3.0.14a & 3.0.20. I can't print to samba printer server with XP client. but with win2000 and win98 no problems. Thanks in advance. [2005/09/22 00:01:19, 0] rpc_parse/parse_spoolss.c:spoolss_io_devmode(785) spoolss_io_devmode: I've parsed all I know and there is still stuff left|

Can not install printer driver for zebra printers to samba2.2.6 and 3.0alpha20. I got follow error in log.smbd (loglevel 2): --- 2002/10/22 14:33:29, 0] rpc_parse/parse_spoolss.c:spoolss_io_devmode(702) spoolss_io_devmode: Unknown specversion in devicemode [0x0] [2002/10/22 14:33:29, 0] rpc_parse/parse_spoolss.c:spoolss_io_devmode(703) spoolss_io_devmode: please report to

All other drivers download (hp lasers) worked well. There is only = problem with zebra printer drivers (ex. Zebra thermo transfer printer of type = Z4M) link for driver at http://www.zebra.com Best regards, Khiem -----Urspr=FCngliche Nachricht----- Von: Gerald (Jerry) Carter [mailto:jerry@samba.org]=20 Gesendet: Dienstag, 22. Oktober 2002 17:27 An: Quach Van Khiem Cc:

Good morning, I am working with samba-3.0.4 and LPRng 3.8.9 on RedHat 2.4.18-14 kernel. We are setting the server up to act as a print server for our W2K clients. Everything seems to be working as expected except when I try to install the drivers for our Zebra 105Se barcode printers. I am seeing log entries which I have included below. Upon trying to install the printer it seems that the

Hi, samba 2.2.8a freshly compiled cups 1.1.19final-1 (debian) while using cupsaddsmb, all runs well until adddriver, when rpcclient returns a cryptic NT_STATUS_NO_SUCH_DEVICE. I've followed the SambaPrintHowto 3.0 from 7.11.6.1 to 7.11.6.6, and it fails on the latest as well. Here is some more information. ===8<=== cupsaddsmb -a -v Running command: smbclient //localhost/print\$ -N

Editing subject line to reflect current status. On 1/26/06, Nilesh Londhe <lvnilesh@gmail.com> wrote: > Since T616 is not answering (and incoming calls are going to Cingular > voicemail after 30 sec,) I suspect the problem focus area is... > > > -- Executing Answer("BLT/T616", "") in new stack > > Is

I'm having trouble linking Samba 2.0.7 under SCO OpenServer 5.0.5 and GCC 2.7.2.3. All the source files compile without errors. However, when I try to link smbd, swat, or smbpasswd, I get the error message: Undefined first referenced symbol in file uniarray_2_ascarray rpc_parse/parse_spoolss.o I can't seem to find any

SCO Open Server Enterprise 5.06, Samba-2.2.8a I received the following compile errors: smbd/server.c line 302 argument is incompatible with prototype: arg #3 smbd/password.c line 664, argument is incompatible with prototype: arg #1 libsmb/clirap.c line 114 argument is incompatible with prototype arg #9 line 114 argument is incompatible with prototype arg#11

We upgraded from 2.2.3a to 2.2.4 on a SuSE 7.2 server. We compiled Samba just default. The new version seems to work ok with the exception of printer administration. Printer admins are not able to see the properties of the printers (right click on printer gives on error). Our workstations are W2k SP2. But users that are not printer admin are able to see the properties of a printer, but they

Hello, I have a bunch of Windows XP Pro machines, Samba 2.2.4, and several plotters on Jetdirect cards, and several printers on Netport 10/100 Muli-port network print servers. I have successfully configured Samba 2.2.4 to allow Windows XP to join the domain controlled by Samba and automaticaly create its own computer account on Samba. I would now like to setup Samba to share all the printers

I'm having a problem with a Samba PDC box that only lets users who are defined by "admin users =" to print to any of the printers. As an interim solution I just threw my @staff group in there, but of course this lets everyone access everyone elses files :) Here is one of my printer configs: As you can see, I tried to set every flag I could think of to let anyone write to this.

Hi, I tried to upgrade samba on a Linux from 2.2.8a to 3.0.0, and after the upgrade the printer sharing fails. I would like to participate in the search for the bug (if it is a bug), but I don't know how to start. If this is not a bug I would like to know why not, and how to work around, that the printer does not work with the attached smb.conf, while it works with samba version 2.2.8a

Hi, I was wondering if anyone has gotten automatic printer driver downloading to work? The problem I'm seeing here is while trying to upload a printer driver to the Samba print server using Windows 2000 or XP. The Add Printer Driver Wizard runs ok until I click on the Finish button, then it requires a Windows 2000 Advanced Server CD-ROM to be installed, to get a driver out of the

Using Sun Forte C (6.2 I think) on Solaris 2.9 UltraSparc Here's the errors: - Using FLAGS = -O -I./popt -Iinclude -I./include -I./ubiqx -I./smbwrapper -I/usr/local//include -I/usr/local//include -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -DLOGFILEBASE="/usr/local/samba/var" -DCONFIGFILE="/usr/local/samba/lib/smb.conf"

Solaris 9, Sun Forte C (6.2), latest CVS Here's the env ./configure --with-readline=/usr/local/ --with-quotas --with-utmp --with-acl-support --with-syslog --with-libsmbclient --without-winbind Using FLAGS = -O -I./popt -Iinclude -I./include -I./ubiqx -I./smbwrapper -I/usr/local//include -I/usr/local//include -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64

Ok, here's my setup: I've had a samba file server going for about a year now. It's Samba v2.05a on a RH6.0 sys. Currently we have a printer server running on a Winblows NT box. This NT box has the following printers: HP5si, (4) HP4000, and a few HP4s. All of those printers have Jet Direct ports on them. What I want to do is, move all the printers over to the Samba box and KILL the NT

I have a Red Hat Linux release 7.1 (Seawolf) Samba 2.2.4 PDC and fileserver built with --with-ldapsam. The clients are either win9x or WinY2k. Authenitcation, etc... all works great. But print sharing is a real pain. Under 2.2.1a printing worked great, but our VOIP phone system wouldn't joint the domain until we upgraded to 2.2.4. Initial testing of 2.2.4 made it seem like everything

Hello, after one small modification I was able to compile samba. I have not yet tried to use it, but at least swat is working. It would be nice if anyone could modify the current code to resolve the specified problems. Mike The Problems: Only a nuisance: uid_t and gid_t are unsigned: /GNU-Source/samba-2.2.0-alpha1/source/smbd/sec_ctx.c: In function `initialise_groups':

I have SLOW file transfers across samba to my Windows Server 2000 domain. I am using a built in 100bT Intel Pro NIC, I have tried the built in gigabit NIC and a PCI 3com, all with the same results. Using iperf, I get about 45-90Mb of bandwidth from my PC's to my samba server. I can pull it up by \\servername <file:///\\servername> or \\ipaddress <file:///\\ipaddress> with out

--===============1058496754== Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-qmIlUkodIF8QS7EAwqnx" --=-qmIlUkodIF8QS7EAwqnx Content-Type: text/plain Content-Transfer-Encoding: quoted-printable I am using samba version 3.0.2a and cups version 1.1.17. I have a BDC setup with 14 printers. Two of which are Lexmark Optra