Re: Windows via samba tips?
On Wed, Mar 17, 2004 at 04:36:47PM -0600, Frank Smith wrote: > > DS> Nope. My samba is version 2.0.7-3.4, as packaged by Debian. > > The current Samba package is 2.2.3a-12.3 in stable (woody) and > 3.0.2a-1 in testing (sarge). Perhaps it's about time to do an > apt-get upgrade. Gah! I tend to ignore the tapehost since that's the only thing it does. Turns out that I still have it running potato... I'll try bringing it up to woody and see what happens. Or maybe I'll try sarge... IIRC, autoflush was added in 2.4 and I'd like to have that available. Will a 3.0.x server run happily with 2.2.x clients our would I have to upgrade them as well?
Re: Windows via samba tips?
--On Wednesday, March 17, 2004 23:06:38 +0100 "Stefan G. Weichinger" <[EMAIL PROTECTED]> wrote: > Hi, Dave, > > on Mittwoch, 17. März 2004 at 22:49 you wrote to amanda-users: > > DS> On Wed, Mar 17, 2004 at 09:58:18PM +0100, Stefan G. Weichinger wrote: >>> I have to say first that I don't have the solution, but maybe we can >>> add another piece to the whole picture ... >>> >>> Please let me know, what Samba-release you use. >>> I bet it is > 2.2.x > > DS> Nope. My samba is version 2.0.7-3.4, as packaged by Debian. The current Samba package is 2.2.3a-12.3 in stable (woody) and 3.0.2a-1 in testing (sarge). Perhaps it's about time to do an apt-get upgrade. Frank > > Ooooh, failed again ... > > ;-) > > 2.0.7 is gone some years now, there has been a lot of improvement > inbetween. > > You don't tell us which AMANDA-release you use, either ... > > If it is nearly as old, I would recommend some updating. > If the problems persist, tell us. > -- > best regards, > Stefan > > Stefan G. Weichinger > mailto:[EMAIL PROTECTED] > > > > -- Frank Smith [EMAIL PROTECTED] Sr. Systems Administrator Voice: 512-374-4673 Hoover's Online Fax: 512-374-4501
Re: Windows via samba tips?
Hi, Dave, on Mittwoch, 17. März 2004 at 22:49 you wrote to amanda-users: DS> On Wed, Mar 17, 2004 at 09:58:18PM +0100, Stefan G. Weichinger wrote: >> I have to say first that I don't have the solution, but maybe we can >> add another piece to the whole picture ... >> >> Please let me know, what Samba-release you use. >> I bet it is > 2.2.x DS> Nope. My samba is version 2.0.7-3.4, as packaged by Debian. Ooooh, failed again ... ;-) 2.0.7 is gone some years now, there has been a lot of improvement inbetween. You don't tell us which AMANDA-release you use, either ... If it is nearly as old, I would recommend some updating. If the problems persist, tell us. -- best regards, Stefan Stefan G. Weichinger mailto:[EMAIL PROTECTED]
Re: Windows via samba tips?
On Wed, Mar 17, 2004 at 09:58:18PM +0100, Stefan G. Weichinger wrote: > I have to say first that I don't have the solution, but maybe we can > add another piece to the whole picture ... > > Please let me know, what Samba-release you use. > I bet it is > 2.2.x Nope. My samba is version 2.0.7-3.4, as packaged by Debian.
Re: Windows via samba tips?
Hi, Dave, on Mittwoch, 17. März 2004 at 16:51 you wrote to amanda-users: DS> Along with several Linux boxes, I have one Windows NT 4 server which DS> I'm using amanda to back up using tar over samba. [..] DS> The failed/strange dump reports tend to be extremely long, but here's DS> one of the shorter ones as an example: DS> /-- peterbilt //server/f$ lev 1 STRANGE DS> sendbackup: start [peterbilt://server/f$ level 1] DS> sendbackup: info BACKUP=/usr/bin/smbclient DS> sendbackup: info RECOVER_CMD=/bin/gzip -dc |/usr/bin/smbclient -f... - DS> sendbackup: info COMPRESS_SUFFIX=.gz DS> sendbackup: info end DS> | added interface ip=192.168.23.31 bcast=192.168.23.255 nmask=255.255.255.0 DS> | directory \LM600\ DS> ? Expected SMBtrans2 response, got command 0x2d DS> ? ERRDOS - ERRbadfid opening remote file \LM600\C5clax.dll (\LM600\) DS> ? ERRDOS - ERRbadfid opening remote file \LM600\C5dosx.dll (\LM600\) This sounds somewhat familiar to me. I have to say first that I don't have the solution, but maybe we can add another piece to the whole picture ... Please let me know, what Samba-release you use. I bet it is > 2.2.x -- best regards, Stefan Stefan G. Weichinger mailto:[EMAIL PROTECTED]
Windows via samba tips?
Along with several Linux boxes, I have one Windows NT 4 server which I'm using amanda to back up using tar over samba. The DLEs, in case anyone's curious, are simply: peterbilt //server/e$ comp-high-tar peterbilt //server/f$ comp-high-tar (peterbilt is the tapehost, and, yes, some unimaginative soul actually did name the NT box "server" before I got here.) For whatever reason, these two DLEs come up strange pretty regularly, maybe 70-80% of the time, and occasionally fail. I do keep 3 weeks of tape, so I always have at least _a_ backup of each, but it would be nice to reliably get them every night. What can I do to get them to start behaving properly? The failed/strange dump reports tend to be extremely long, but here's one of the shorter ones as an example: /-- peterbilt //server/f$ lev 1 STRANGE sendbackup: start [peterbilt://server/f$ level 1] sendbackup: info BACKUP=/usr/bin/smbclient sendbackup: info RECOVER_CMD=/bin/gzip -dc |/usr/bin/smbclient -f... - sendbackup: info COMPRESS_SUFFIX=.gz sendbackup: info end | added interface ip=192.168.23.31 bcast=192.168.23.255 nmask=255.255.255.0 | directory \LM600\ ? Expected SMBtrans2 response, got command 0x2d ? ERRDOS - ERRbadfid opening remote file \LM600\C5clax.dll (\LM600\) ? ERRDOS - ERRbadfid opening remote file \LM600\C5dosx.dll (\LM600\) ? ERRDOS - ERRbadfid opening remote file \LM600\C5tpsx.dll (\LM600\) ? ERRDOS - ERRbadfid opening remote file \LM600\CLOCKINI.BAK (\LM600\) ? ERRDOS - ERRbadfid opening remote file \LM600\CW2DOS16.DLL (\LM600\) | directory \LM600\data\ ? Expected SMBtrans2 response, got command 0x2d ? code 0 listing \LM600\data\* | directory \LM600\Doc\ ? Expected SMBtrans2 response, got command 0x04 ? code 0 listing \LM600\Doc\* ? ERRDOS - ERRbadfid opening remote file \LM600\DOWNLOAD.PIF (\LM600\) ? ERRDOS - ERRbadfid opening remote file \LM600\Flash.TPS (\LM600\) | directory \msdownld.tmp\ ? Expected SMBtrans2 response, got command 0x04 ? code 0 listing \msdownld.tmp\* | directory \Project 130 D Line\ ? Expected SMBtrans2 response, got command 0x2d ? code 0 listing \Project 130 D Line\* | directory \RECYCLER\ | directory \TEMP\ ? Expected SMBtrans2 response, got command 0x2d ? code 0 listing \TEMP\* ? ERRSRV - ERRerror opening remote file \test.iso (\) | directory \trudy.000\ | directory \trudy.000\AAL 130D\ ? Expected SMBtrans2 response, got command 0x2d ? code 0 listing \trudy.000\AAL 130D\* ? ERRDOS - ERRbadfile opening remote file \trudy.000\Bearing 130 D.xls (\trudy.000\) ? ERRDOS - ERRbadfile opening remote file \trudy.000\SRE Housing 130 D.xls (\trudy.000\) | directory \vnc_x86_win32\ ? Expected SMBtrans2 response, got command 0x2d ? ERRDOS - ERRbadfile listing \vnc_x86_win32\* ? ERRDOS - ERRbadfile opening remote file \west6.3.zip (\) ? ERRDOS - ERRbadfile opening remote file \Westling053001.zip (\) | directory \Work Instructions\ | directory \Work Instructions\vncviewer\ ? Expected SMBtrans2 response, got command 0x2d ? code 0 listing \Work Instructions\vncviewer\* | directory \Work Instructions\winvnc\ ? Expected SMBtrans2 response, got command 0x2d ? code 0 listing \Work Instructions\winvnc\* | tar: dumped 396 files and directories | Total bytes written: 311787008 sendbackup: size 304480 sendbackup: end \