similar to: samba printer driver uploading

I'm having a couple of problems getting samba to process /etc/printcap properly. The printer definition lines of my /etc/printcap are: epson|lp|uniprint-letter-auto-mono|Epson Stylus Color 800 (mono, 360x360):\ color|epson_color|lp1|uniprint-letter-auto-mono|Epson Stylus Color 800 (color, 360x360):\ med|epson_med|lp2|uniprint_stc800p-letter-auto-mono|Epson Stylus Color 800 (mono, 720x720):\

I am trying to associate a driver that i installed with mkprintpkg and install_printer_drivers.pl with the printer that its supposed to go with. this is a log of what is happening: nendral:~ # rpcclient nendral -U root -W xxxx Enter Password: session setup ok Domain=[xxxx] OS=[Unix] Server=[Samba 2.2.4] rpcclient $> enumdrivers [Windows NT x86] Printer Driver Info 1: Driver Name:

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, I am running Windows XP and Windows NT workstations on a lan with a samba 2.2.4 server providing files and printers to these workstations. I have the following printers shared by samba: HP LaserJet 1200 Epson Stylus Color 3000 Epson Stylus Pro XL HP DesignJet 755 CM HP DesignJet 2500 CP The problem I am having is that Windows XP and Windows NT are using different drivers for the same

I use [Epson Stylus] path = /var/spool/samba comment = Epson Stylus Photo 750 - PC DO printer name = epson browseable = yes printable = yes public = yes writable = no create mode = 0700 printer driver = EPSON Stylus Photo 750 Printing is ok from win9x. I have filename problems... Suppose I print the file "mydoc.doc": as soon as I print a file, when it still is in /var/spool/samba, I

Greetings, I'm not on the list, so please CC me, thanks. :) Problem: printing a full-page graphic stops 3 inches into the print. System: FreeBSD 3.2 server running Samba 2.0.3 (version that is installed with the distribution) 486DX (4 or 8MB, I don't remember at the moment, I think 8.) 2 parallel ports Epson Color STYLUS 500 Epson Color STYLUS 800 Win95 client

I have an Epson Stylus Color 880, connected to our network via an external ethernet printserver. I used to run lprng on the samba server (which is a domain controller), and the Windows clients had one minor problem accessing this printer via Samba (2.2.3a, then): Every time a client wanted to print, the Epson status monitor on the client would complain about communication problems with the

I can't seem to find an answer or a workaround, and I've received stoney silence on this one. There aren't any answers in the archives (well, I didn't find any in the hours on several days I spent, anyhow). I'm convinced that I can't be the *only* one with this problem, nor am I convinced that there is absolutely no one who can help. Please feel free to jump in with

Hello, I print from a Win2000 Station to a Debian SID with Samba and cups ( [samba 2.999+3.0.alph] [cupsys 1.1.18-1] ), I can print but on the Win2000 I have the message (unable to connect on the printer ....) and this is a part of my error_log file: adPPDs: Read "/etc/cups/ppds.dat", 143 PPDs... I [07/Jan/2003:19:06:31 +0100] LoadPPDs: No new or changed PPDs... E

I set up a new printer on my Linux box, an Epson Stylus Color 740. I had previously been using an EPson Stylus Color IIs. I got the printer working nicely in Linux, but I can not print to the printers I set up in /etc/printcap via samba from NT anymore. I.e., it worked with the IIs, but not with the 740. I didn't change anything in smb.conf. NT lets me install the printers via samba, but

Hi, Having a very odd problem with a printer that I've had up and running for over a year now with no previous issues. There have been no software or hardware updates recently that should have affected it. The printer is managed via CUPS and its details are loaded from the CUPS printcap. At some point late on the afternoon of the 11th, samba started rejecting print jobs sent to it.

Matthew Vanecek wrote: >I set up a new printer on my Linux box, an Epson Stylus Color 740. I >had previously been using an EPson Stylus Color IIs. I got the printer >working nicely in Linux, but I can not print to the printers I set up in >/etc/printcap via samba from NT anymore. I.e., it worked with the IIs, >but not with the 740. I didn't change anything in smb.conf.

well i've tried everything trying to get r/w access to my linux box (debian 2.2.3 running samba 2.0.7) from win2k. can only get readonly. i'm hoping some kind sould might be able to take a look at my samba config and let me know what i'm doing wrong... # Samba config file created using SWAT # from localhost (127.0.0.1) # Date: 2001/11/01 00:39:30 # Global parameters [global]

I have a network which consists of two subnets, each with a linux server providing Samba services. With the configuration listed below, I have successfully achieved Subnet B being able to browse Subnet A but, Subnet A cannot browse Subnet B (sharename not found). Is it a Samba configuration issue or is it DNS? (I have it fixed if I put an /etc/lmhosts file on Linux Server A that has the host

Hello all, I'm trying to set up an Epson Stylus C62 printer for automatic download of windows XP drivers in Samba 3.0.9. I have the printer successfully set up on my Windows XP machine, and I can print from there without a problem. The trouble is when I try to tell samba about the drivers, it fails. This happens if I use the add printer wizard and if I try to do it manually with the

Printing seems like a popular subject here lately. ;) I have an Epson Stylus Color IIs which I had connected to my Linux box. It was mapped on my NT box, and everything worked fairly well (except for the print quality--NT drivers for that printer suck). So, I bought a new printer--an Epson Stylus Color 740. I hooked it up to Linux, made the necessary changes to /etc/printcap, and printed some

Hello, I couldn't find an answer to this small question in google/man/faq: why do I use lose my printer if I use registry backend? config backend = file (full config file below): ... [printers] comment = All Printers path = /var/spool/samba create mask = 0700 printable = Yes browseable = No guest ok = yes ... $ smbclient -kL //venkman ...

I have menaged to setup Samba services to share an IBM 4039 printer and have tested another printer (Epson LX-800) on the PC. It works fine. The weird thing, the IBM4039 will not print anything. All the jpbs will be spooled. For each print job to be printed. I will need to switch off the printer and switch it on again. Have anyone encountered such problems before? I know there is basically

For some reason, I cannot get samba (or Win98, depending on how you look at it...) to allow a win98 client to print. I search the list archives, but I didn't find anything similar. So here goes. Symptoms: - Win98 client can access fileshares OK. The printers show up OK as well in network neighbourhood. - On Linux, printing (lprng) works OK. - In win98, e.g. dir >

Anyone dealt with an Epson Stylus Photo 2200? Disconnected from my machine, it won't even print a self-test page.... mark