similar to: FW: backupexec

I have winbind & samba (2.2.5) set up to provide home shares to users of our Windows NT domain. I have also gotten pam_mkhomedir to work properly to automatically create their home directory. Connecting to \\sambaserver\homes works well for this. However, I have a problem if an NT Domain username contains a space. I cannot figure out how to work around this. Their home directory gets

Hi, Does anyone have experience with BackupExec and Samba? BackupExec refuse to access Samba shares. Windows shares are OK, but all my Samba shares are not. I have Samba on at least 2 Linux 2.4 machines + 1 on Solaris. Neither ones work with BExec. Any idea? Other have experience with BExec and Samba? Thanks a lot -jec _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ Jean-Eric Cuendet

Is there an improved BackupExec Unix agent available that works with Samba? If not, can someone tell me how to work around the lack of the archive bit that Linux has? In particular, RedHat Linux 7.2 is the system I'm looking for help on. I found the following hints in an older version of this newsletter, Samba Digest, Vol. 3, Issue 34, sent March 21, 2003, that had this in it: Yes, we have

Hi Franck, to my knowledge, the Backup Exec service "runs" under a certain user. In most cases it is the user who installed it, so very often "Administrator". Now if you try to backup a Samba share, Backup Exec tries to retrieve the files of this share and has to authenticate to the Samba Server. I suspect it will do this with the "credentials" of the user the Backup

Hi, I've got Samba 2.0.2 and a server NT4 SP3 with Seagate BackupExec 7.0. When I want to backup Samba with Seagate BackupExec, I get a message saying "Unable to connect to server, <F5> to retry", and then another one saying "A device specific error occured". I've read all the Samba archive about that subject, but I do not find any solution. I don't

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 We've just posted another snapshot of the SAMBA_3_0 cvs tree for download. This is a non-production release provided for testing only. The source code can be downloaded from : http://download.samba.org/samba/ftp/alpha/ The uncompressed tarball and patch file have been signed using GnuPG. The Samba public key is available at

Samba Gurus, I've got a Solaris box running samba 2.0.7. A couple of users on Windows XP clients are reporting problems saving files from within MS Word, and Wordpad to the samba share, which of course is a mapped drive. They get an error saying "This is not a valid file name".... These XP boxes do have the reg hacks plainpassword.reg and signorseal.reg installed. The work around

Hopefully a simple question. Does anyone know of .deb or .dsc files for Samba Version 2.2.4, 2.2.5, 2.2.6, or 2.2.7? The only packages available from Debian are: 1. Stable - Samba 2.2.3 2. Testing - Samba 2.2.3 3. Unstable - Samba 30alpha20-4 I've looked on the debian website and in google with no luck. Any help much appreciated? IRV

I am having problems with autocad file corruption. My users are draftsman and access project files via samba over the network. This problem occurs after a file has been worked on and someone attempts open a file that they were working on. There is no indication of a problem while the file is open and being worked on. But when they try to re-open it, autocad thinks the file is corrupt and it

Hi, I'm searching for 2 months on this problem (I've searched in the archive of course and I've sent a message on this mailing list, the suggestions had helped me but I didn't manage to resolve the problem). The problem: ------------ I've got Samba 2.0.2 on a Linux Red Hat 5.2 and a server NT4 SP3 with Seagate BackupExec 7.0. When I want to backup Samba with Seagate

Hi, I've got Samba 2.0.2 on a Linux Red Hat 5.2 and a server NT4 SP3 with Seagate BackupExec 7.0. When I want to backup Samba with Seagate BackupExec, I get a message saying "Unable to connect to server, <F5> to retry", and then another one saying "A device specific error occured". I've read all the Samba archive about that subject, but I do not find any

I dont think its a OS problem, Im using suse 8.1. If you log into the windows box as root you can see the groups and the users in the groups. Any other user including domain admins can not. This would indicate that there is a problem with samba, either with ACLs accessing group information or passing group/user information from the system to a smbd process owned by a user other than root.

OS name and version, MASTER SYSTEM has three APC smart UPS 3000 UPS connected via USB debian 8 "jessie" Linux pdxvhtst01 3.16.0-4-amd64 #1 SMP Debian 3.16.43-2+deb8u5 (2017-09-19) x86_64 GNU/Linux SLAVE SYSTEMS monitoring MASTER via IP debian 8 "jessie" Linux geaaetst01

MASTER SYSTEM nut.conf MODE=netserver ups.conf [TOPAPC] driver = usbhid-ups port = auto pollonly serial = "IS1309002707" desc = "TOPAPC" [MIDAPC] driver = usbhid-ups port = auto pollonly serial = "IS1309001233" desc = "MIDAPC" [BOTAPC] driver = usbhid-ups port = auto

We have just setup Samba 3.0.28 with LDAP support. We are using a Sun One 5.2 LDAP server. We are having a problem when a new machine joins the domain. Here is a snippet of our smb.conf file add machine script = /usr/local/sbin/smbldap-useradd -w "%m" ldap machine suffix = ou=computers ldap user suffix = ou=People When a new machine attempts to join the domain a new entry is

I'm running a new (6 months old) fast server, with an ultra-scsi RAID array . . . some of my workstations, however, are getting elderly: some are 5 year old 350Mhz machines, and my users are finding it faster to put their .pst files on their Samba-shared Linux home directories. (50 users, .pst files from 100mb to 1.5Gb). (yes, yes, I know, 1.5GB is WAY too big for a .pst file; its a constant

Hello, I've compiled and configured Samba 1.9.18p8 on a DEC Alpha running DEC Unix 4.0b for the express purpose of enabling a Windows NT 4.0 server running Seagate BackupExec software to be able to see my Unix filesystems as NT shares and back them up (as of this time BackupExec does not support DEC Unix clients). Test backups have worked OK, but I'm having problems restoring the

So SAMBA no longer supports print driver downloads. That is about the only conclusion that I can come to at this point. I've not been able to get Windows printer driver downloads to work right since Samba 2.2.2. No one but printer admins displays the correct settings for printers, everyone else gets the original printer defaults that they cannot change. I've tried this with

Anyone know the reason RHEL bumped Samba from 3.5.10 to 3.6.9? This version has a regression with BackupExec and Veeam backing up to network shares. I receive access denied errors. Samba is in security=user mode and not joined to a domain. If I downgrade just the Samba packages to the CentOS 6.3 version 3.5.10 everything works again. I've found a couple of bug reports and the one suggested fix

Can anyone suggest a good open source/free backup software that works on CentOS? I was reading through the manuals on how to back things up and it said do 1 of 2 things. Buy a 3rd party software packages or make one from source. Well I have no clue how to do the 2nd option and I don't want to spend any money so I figured I would as you gurus. BTW I am newb so easier the software the better.