similar to: Printing not working with Samba 2.2.4

I have Samba 2.2.4 installed on Redhat 7.3. I was trying to set up printers through it and everything works great on from a Windows 2000 Professional Client, but a Windows XP Client dies a miserable death when trying to view the properties of a printer. On the Windows XP Client side, I get: Properties clould not be displayed, procedure could not be finished On the Redhat 7.3 side, I'm seeing:

I cannot print to my Samba-printer from Win NT. Printing works fine under X-windows. What could be wrong? //Michael

Ello -- For the past few months our Samba installation, currently at Version 3.0.28 has filling the log. file with [2008/04/17 13:25:30, 0] smbd/notify_inotify.c:inotify_handler(234) No data on inotify fd?! This is started to happen almost weekly and it continues to output those lines until the log partition is full, then leaves a single process spiked to 100% until I kill it. There is

I have just compiled Samba 2.2.4 with the following configure. ./configure --with-pam --with-winbind I used the same instructions as I did go get Samba 2.2.2 working. I noticed the winbind daemon dies after about a minute. I set the debug to 10 for it and I found some confusing things. Why is it trying to connect to GIGDC1 with a null username? Is this why the connection is refused?

I'm having a problem authenticating to my Samba server. I'm NOT using winbind, and I have setup local users in the smbpasswd file. My w2k workstation works as I would expect and when I connect I see the following in the log.smbd. [2002/05/14 10:38:23, 2] smbd/reply.c:reply_sesssetup_and_X(980) Defaulting to Lanman password for administrator [2002/05/14 10:38:23, 3]

I'm converting my NT 4.0 Print Servers to Samba Print Servers. Which printing system should I be using? LPR, LPRng or CUPS. I would love to have some feedback on the advantages and disadvantages or what the Samba Team recommends as a standard for working wih Samba. In case you need it, my system is SuSE 7 kernel 2.2.16 running under VM on s/390. Thanks, Josh Konkol, CNE MCSE Senior

I'm running Samba 3.0.11. Compiled with: ./configure '--with-ads' '--with-pam' '--with-winbind' '--with-smbmount' '--with-shared-modules=idmap_rid' It configured, make and make installed fine. I configured the idmap_rid using the following directives in the smb.conf. ; IDMap Stuff idmap backend = idmap_rid:<DOMAINNAME>=500-100000000

Is there a mod_ntlm_winbind for apache or is that just for squid? I want to use NTLM authentication for our intranet apache server. TIA, Josh Konkol, CCSA CNE MCSE Technical Research Specialist .~. GuideOne Insurance /V\ /( )\ ^^-^^ samba@guidemail.com This message and accompanying documents are covered by the Electronic Communications Privacy Act, 18 U.S.C. ?? 2510-2521, and

I'm trying to get Samba to compile on SLES8 SP3 (Linux under z/VM) and I'm getting the following error. Configure ran fine with "./configure --with-ads --with-winbind --with-krb5", but when I run make I get the following output and error. Using FLAGS = -O -I/usr/local/include -I./popt -Iinclude -I/usr/local/downloads/samba-3.0.2a/source/include

Eric, I started as you instructed and when I get to this command, ./bin/update-packageinfo 2.2.6pre 20020730 I receive the error: no such file or directory next I changed to the RedHat dir. and executed sh makerpms.sh...this appeared to work fine. i could not execute rpm -Uvh samba-2.2.6pre-20020730.i386.rpm what I did execute is: rpm -Uvh samba-2.2.5-1i386.rpm and received the

Samba 3.0.11 on SLES8 on z/VM The system will be running fine then every few days the Winbind daemon will stop. Below are the last lines of the log file. [2005/03/03 14:15:00, 0] sam/idmap_rid.c:rid_idmap_get_id_from_sid(475) rid_idmap_get_id_from_sid: no suitable range available for sid: S-1-5-32-545 [2005/03/03 14:15:00, 0] sam/idmap_rid.c:rid_idmap_get_id_from_sid(475)

Since upgrading to 3.6.1 in Debian testing, I receive a panic/segfault message with each print job. Printing succeeds and continues to work, but an email with the info below is sent each time. The system is standalone. Kernel is 3.1.0-1-686-pae, and the system is fully updated. testparm returns no errors. Does this mean anything to anyone? Dale [Thread debugging using libthread_db

I wonder if there is any resolution to this problem. I'm encountering similar situation with the Nashuatec DSC338 and P7325 printers from Ricoh using RPCS drivers. After uploading those drivers and performing basic printing preferences configuration, the print server crashed and become inaccessible. Here is the error from samba.log: [2005/07/23 12:14:19, 0]

Hi all, After building Samba 4.1.20 for Ubuntu 14.04 x64 I encountered this issue when using shared printers: every time a client prints or changes printer settings, this message is logged in the log: dcerpc_spoolss_ReplyClosePrinter failed [NT_STATUS_RPC_PROCNUM_OUT_OF_RANGE]. Printers print fine, so it is probably harmless, but I still wonder why this happens. With log level = 3 I get

I only have limited Samba experience, and expect this is a silly mistake, but have been unable to find a solution I have installed Samba and Winbind on my desktop Linux (Debian) machine (SPARKSTONELX), aiming to unify logins with other windows machines accessing the PDC, again samba/Debian, with tdbsam password backend. All is well, joining the domain, and getting account details using wbinfo -u,

Installed Samba 3.0.10 via 'pkgadd' on Solaris 2.6 workstation s080 (137.223.31.80) - previously running Samba 2.2.8 which has worked for a long time. Samba 3.0.10 smb.conf file - changed to security =DOMAIN from SERVER at 2.2.8 version password server = 137.223.33.45, 137.223.33.72 - these are DCs # Samba config file created using SWAT # from 127.0.0.1 (127.0.0.1) # Date:

We recently upgraded our PDC from Debian 4 to Debian 5. That entailed an upgrade of Samba from 3.0.24 to 3.2.5. Since the upgrade we've had a very specific problem connecting to shares on a commercial NAS running Samba 3.0.34. The problem happens when users try to connect to shares from standalone servers--e.g., Windows XP Pro boxes that we use for testing. From those boxes users should be

Hello, I'm having some trouble with the winbind process I'm getting a lot of error: [2005/07/04 14:14:48, 0] libsmb/clientgen.c:cli_send_smb(155) Error writing 494 bytes to client. -1 (Broken pipe) [2005/07/04 14:14:48, 0] rpc_client/cli_pipe.c:rpc_api_pipe(435) cli_pipe: return critical error. Error was Write error: Broken pipe [2005/07/04 14:14:49, 0]

Hi, we have a problem with your Samba4 Domain Member as with Shares. when i would connect i got an Error. In Samba Logs it tells me ==> /var/log/samba/computerid349.log <== [2016/02/10 14:39:50.313835, 1] ../source3/printing/printer_list.c:226(printer_list_get_last_refresh) Failed to fetch record! [2016/02/10 14:39:50.313949, 1]

Hi! I've set up a Samba server (running winbind) as a Win domain member server. Users authenticated from win domain and mapped to NIS uids and gids. Everything was working well, but the next morning winbind stopped to respond. I reset it, so now I get wbinfo, ypbind (ypcat) results ok as before, but users suddenly cannot authenticate any more. My <client>.log files are empty,