similar to: Windoze Printer and Linux Box Setup Woes

Please answer if anybody has solved this problem: [1999/07/19 20:59:41, 1] smbd/files.c:file_init(216) file_init: Information only: requested 10000 open files, 246 are available. Thanks in advance.

I am trying to allow printing from my linux box to my win98 box, to which my epson stylus printer is attached. It's just not happening...something tells me I'm flirting with a world of pain. I *can* print a file by going: smbclient //rory/EPSON translate print /etc/group but I cannot print from applications, nor can i use smbprint. I tried going: cat /etc/passwd | sh -x smbprint

Hello people, ok just a small problem I have with my samba settings. I have a RH 6.0 file/printer server that is connected to some Windoze 98 machines and a couple of Macs. The linux machine also has one printer on its local port lpt1. Ok...I have set up everything and currently I can print from the Windozes and the Mac to the printer that is localy connected on the Linux server. What I want

At 16:58 23/07/99 +1000, you wrote: > SAMBA Digest 2177 > >For information on unsubscribing see http://samba.org/listproc/ >Topics covered in this issue include: > > 1) rookie needs help > by "Page, Jon T" <Jon.Page@pnl.gov> > 2) genrand.c > by Mark_Noel@cch.com > 3) Wincenter 3.1.13/Winframe 1.7 - ACLs: > by Hanns-Peter Ermert

I have been unable to make smbpasswd work on my new Samba version 2.0.3 (HPUX 10.20). The smb.conf was modified from a working version on Linux (version 1.9.18p8). The relevant (I hope) output from smbpasswd, smb.log and testparms follow below. Are the log messages about "Couldn't set effective gid to -24 currently set to (real=0,eff=0)" and "Can't become connected

I seem to have some issues coming to terms with the new smbprint configuration. Not that it is all that new, but I have worked on a ton of AIX Samba systems that are runing 1.9.x and the smbprint worked great in all aspects. The box's couldn't be upgraded (or so said the company that did application builds related to Samba). The printers were and are hosted from windows95 workstations

Well, I finally managed to setup samba printing... almost. smbprint seems well and good... if you have a postscript printer, which I don't. So, I just see stair-stepping, raw postscript on the win98 box printer I'm sending to. I've configured magicfilter to handle postscript with gs, but I'm having trouble integrating magicfilter with smbprint. I'm not much of an expert on

Well, I finally managed to setup samba printing... almost. smbprint seems well and good... if you have a postscript printer, which I don't. So, I just see stair-stepping, raw postscript on the win98 box printer I'm sending to. I've configured magicfilter to handle postscript with gs, but I'm having trouble integrating magicfilter with smbprint. I'm not much of an expert on

Previously I have a working print server using samba with below setting: [global] printcap name = cups printing = cups security = share [printers] browseable = yes printable = yes public = yes create mode = 0700 guest only = yes use client driver = yes guest account = smbprint path = /home/smbprint I could print both from linux and windows XP. But recently (Samba 3.0.22),

Dear Samba Team, the smbprint script as provided with Suse7.2 for Samba Version 2.2.0 did not work. The problem was that the file to be printed was not transfered via stdin after the print - command. I changed the smbprint script to pass the commands via the -c option. My changes and comments are marked with MR27092001MR in the smbprint attached. I did not find this in the lists, so I hope this

Hello. I have been trying to print to a windows printer share with no success. So far I have found out that the smbprint does not execute. I verified this by looking at the logfile=/tmp/smb-print.log (from smbprint script) after printing from windows - this logfile was not created. Also, i verified the path of smbclient and it points to the proper directory. I am using Debian , and samba

I'm trying to figure out an intelligent way to install apps on the network server, and be able to install once and have all the clients use this. However, it seems like most installations modify the registry and seem to demand a client-by-client installation. Am I missing something on this? Can someone provide me some hints or references to help this? (And is anyone thinking about a SMS/ZEN

Hi, Maybe someone can help me. I am running FreeBSD 3.2 with Samba 2.0.4b and NT Server 4.0 with SP3 and I added the BSD machine to its server list. My printer is setup on my NT for print sharing. Well if I connect to the share name of the printer via smbclient ( ./smbclient \\\\ESAU\\EPSON -U login%password) I am able to successfully access it and even print. However, when I use the

Greetings All: I hope everyone had a fun Halloween weekend (I carved 4 big pumpkins and gave out a bucket full of rubber eyeballs and stuff). I'm hoping somebody can explain the password behavior I've been seeing (and a couple of other things). Here's my setup: An isolated LAN (most clients have modems for dialling out) with one linux/samba machine (RedHat 4.2, kernel 2.0.30,

I have been using the "username map" parameter for some time on various versions of Samba 2, and it has worked nicely. Last week I upgraded to Samba 3 and integrated with Active Directory. Since I am using Solaris 8, and "nsswitch.conf" doesn't support winbindd, I am using the "add user script" parameter to add users. What is happening is that users in

I am printing from linux to a printer attached to a win98 computer. I send a text file directly to the printer such as 'lpr -P BJC <file.txt>', the printer prints all the text as it should then fails to eject the last page and then goes off line. When I push the online button, it ejects the page and then is ready again. I am using a Cannon BJC4304. This printer supposedly can

Sorry, I guess I should have been more specific, I am printing from linux to a printer attached to a win98 computer. When I say text I mean when I send a text file directly to the printer such as 'lpr -P BJC <file.txt>'. When I say 'hang' what I mean is that the printer prints all the text as it should then fails to eject the last page and then goes off line. When I push

While trying to configure my *nix box to print to windows, I discovered my samba build does not have the smbprint utility. I saw no option in the configure/make script to build with the smprint utility. Is there an option that will build this tool? Thanks! Joe Cipale -- #----------------------------------------------------------# # "Don't fear the penguin!"

I am currently investigating using samba on a Linux box to provide file server services on our NT LAN (I'm a bit sick of NT doing dummy spits on me). I'm running RH5.1, and have just upgraded samba to samba-1.9.18p8-51.3 (using the rpm from http://samba.anu.edu.au/samba/ftp/Binary_Packages/redhat/RPMS/5.1/samba- 1.9.18p8-51.3.i386.rpm) The setup includes several NT servers, one set up as

I ran into something like this in 3.10.4 and filed two bugs for it: https://bugzilla.redhat.com/show_bug.cgi?id=1491059 https://bugzilla.redhat.com/show_bug.cgi?id=1491060 Please see the above bugs for full detail. In summary, my issue was related to glusterd's pid handling of pid files when is starts self-heal and bricks. The issues are: a. brick pid file leaves stale pid and brick fails