similar to: Solaris8 (Intel) smbtar command to F:

Hello Family, My RedHat-7.2 box prints perfectly to an Epson777 color injet printer which I gave an IP address via a mini printserver attached to the back of the printer. I have a Windows2000 computer hooking into the same RedHat-7.2 box via Samba-2.2.2 fine. I have not been able to get my Windows2000 box to print to the Epson777 color injet via Samba. [question] Since Linux already

The attached message is 2001, but was the top of the list in a Google search for the error message. The same solution fixed a SuSE 9.3 Samba/Cups problem for a Brother MFC 3360C printer. Thanks! Original message: Bill Schoolcraft bill at wiliweld.com Sat Dec 29 13:36:02 GMT 2001 Gustavo Courault <courault at gigared.com> has solved this for me with the following advice

Hello Family, (smd.conf file attached) Having had great success with 2.2.2 and my Linux box and Windows-2000 machines I switched to CUPS and now can't print again having made some slight edits in my smb.conf file (attached) for the change to CUPS. [1] I have to reloaded all the Windows drivers again on the Windows-2000 machines and still get the "Startdoc..." error. [2] The

Hello Family, I had encounted that as "user" I couldn't change my own passwd with "smbpasswd" and noticed the permission differences between smbpasswd and passwd. This is Samba-2.2.2 -rwxr-xr-x 1 root root 782415 Dec 28 03:14 /usr/local/samba/bin/smbpasswd -r-s--x--x 1 root root 12244 Feb 7 2000 /usr/bin/passwd Is there a reason why the

This is a hard one. I can set up cups & samba fine to print ok on FreeBSD and to print from W2K on BSD - ahh, but only with the windows printer driver for Epson - which sucks - there is no way to clean heads, the color is horrible, print area is limited, etc. The major problem is that there does not seem to be any documentation that explains clearly how the configuration works either for

Hello Family, It took my wife calling me at work to ask for some copies of our wedding pictures (trapped on Windows machine) that are next to the Solaris-8 machine I'm typing this on. Well I said, let me look for "smbmount" and I don't have it compiled on this system so I was going to recompile and saw this: --with-smbmount Include SMBMOUNT (Linux only) support (default=no)

I am attempting to integrate a Linux Samba Server with an NT 4.0 PDC. Ideally I am looking to authenticate the users on the PDC, and then permit access to the Samba Shares on the Linux Box. I have several issues, but the one which is presenting itself currently is when I attempt to Browse the PDC using smbclient. I get the following: smbclient -L dumbo added interface ip=192.168.0.11

Hello Family, [day 2.5] Well, thanks to "Gerald (Jerry) Carter" there has been progress in attempting to print from my Windows2000 machine to my Linux machine running 2.2.2 to an Epson777 inkjet printer on the LAN with a mini print-server on the back of it. I've now got no more RED "access denied" warnings in my Win2k printer setup screen, there is a GREEN "Status:

Hello Family, Our sysadmin at work demands that no one have any Samba projects other than the single one on our network due to the "NOISE" that is emitted by Samba. [question] Can I still use the current 2.2.2 with my little test setup and not fall prey to the order to "cease and desist" Samba ? It's one Solaris-8(Intel) and Win2000 and Win98, three total machines. --

Hi all, I want to move a filesystem off of my NT server over to my Network Appliance NFS server to then be shared via Samba. I assume the easiest way to accomplish this would be to use smbtar. Do I then use smbtar to extract the tar file I create with smbtar, or, can I use gnutar? Does it matter? Am I safer sticking with smbtar? I'm guessing that since smbtar is a wrapper around

To all, Can SambaTar backup multiple "pc's" at once ? I have 5 Win95 machines with 9 different drive partitions. What would be the proper syntax ( if any) to specify multiple pc and multiple share names ? I would like to do one complete backup on a single 4mm DAT tape. Is there a better way to do this using Samba ? I am using Samba version 1.9.17p4 running on Sun Solaris 2.5.1

I am attempting to pipe the output of smbtar into gzip in a script. The problem that I have is that smbtar echo's out "Params count: 11" before sending the information out to gzip. This causes the tar file to have a "tar: directory checksum error" error. Is there any way I can get smbtar not to report the Params count? The following is the command I am using.

Hi all, Situation: We use smbtar for backups, incrementals done using -N <last date file>, and this has worked well with samba 2.2.x After upgrading to 3.0b3, using the -N (newer) option to smbtar causes a bad interaction with smbclient. Eg,: # smbtar -s PC -x Share -u User -p Pwd -d / -t - -N last-backup -v gives (if you print out the eval at the end of smbtar script): eval

Actually I'm using the following versions: smbd -V output: "Version 2.2.1a" nmbd -V output: "Version 2.2.1a" Stefano -----Messaggio originale----- Da: Mark Cooke [mailto:mpc@star.sr.bham.ac.uk] Inviato: gioved? 31 luglio 2003 12.14 A: Stefano Del Negro Oggetto: Re: [Samba] smbtar Samba not liking the accented 'i' character ? Just a guess, Warning - don't

I was using smbtar to test backing up an NT server, everything works fine except that for quite a lot of the files it has an error downloading them(probably 2/3 of them actually). All it says is : Error reading file \dir\dir\file. Got 0 bytes Didn't get entire file. size=533, nread=0 I could see this happening if the file were opened exclusively such as the paging file, but to my knowledge

Hi, I recently upgraded to 1.9.18p8, and noticed that smbtar no longer automatically includes system files. I can't seem to find a way to include the 'tarmode system' command in the smbtar shell script. If I add a -c "tarmode system" to the $SMBCLIENT command line at the end of the smbtar shell script, I get no tarred files at all. Can anybody help me with this?

Hello Family, I'm having a hell of a time just trying to "see" the shared printer on a Win-XP(pro) box here at home. All my other Windows boxes can not only see it but print to it, my Unix family (all of the relatives) of machines are having no luck. I apologize if this is something simple for Samba has evolved so much that one barely needs to do anything to get stuff working for

Hi! I have moved our samba configuration to a new hardware. Old config: PII 266 MHz 96MB memory RedHat 7.2 20Gb ide hard drive for samba shares samba-*-2.2.7-3.7.2 packages installed kernel-2.4.20-28.7 New config: P4 2.4GHz 512MB memory RedHat 9.0 60GB scsi hard drive for samba shares and OS 40GB ide hard drive for backups samba-*-2.2.7a-8.9.0

Hello. I'm trying to use smbtar/smbclient (2.0.3) to copy an NTFS share on an NT Server, onto a Solaris 2.5 system. The NTFS partition is 10Gb. At the 2Gb mark, the tar stops. No errors, the file just stops. The process (smbtar) returns. Is this a problem with Solaris 2.5 ? I believe it is, and if I upgrade to 2.6, I can create larger tar files. However, does anyone know if

I have been regularly crashing my NT boxen trying to back them up via an smbtar (smbclient). The crash is not complete - the network layer on NT goes away. You can still operate the console, but no net traffic. This is NT workstation and server 4.0 with sp3. The UNIX samba server is Solaris 2.5 with the latest samba version (1.9.18p8?) also with other samba versions. I tried updating the NT