similar to: Samba 3.0.4 + Veritas Backup Exec

Displaying 20 results from an estimated 2000 matches similar to: "Samba 3.0.4 + Veritas Backup Exec"

2004 Jul 27
0
PANIC: internal error; winbind daemon (3.0.4) crashes
Hello, I'm using samba 3.0.4, compiled with Kerberos 1.3.1-7, in an W2k3 ADS environment and Kerberos and the Winbind daemon are used for authentication. While checking a winbindd.log file I saw the following PANIC internal error: winbindd.log ========= [2004/07/21 12:15:00, 1] nsswitch/winbindd_group.c:winbindd_getgroups(1032) user 'root' does not exist [2004/07/21 12:15:00, 1]
2004 Sep 01
0
Issues after upgrade to 3.0.6 from 3.0.4; fixed in 3.0.7?
Hello, I run samba 3.0.4 on a RHL9 server. Samba is a domain member of a W2k3 ADS and I use CUPS as printing mechanism; therefore Samba is compiled with Kerberos 1.3.1-7 and cups-devel. 3.0.4 runs pretty good, printing via CUPS runs well too, only the following messages I see constantly (this flooding my logs) while using 3.0.4: winbindd.log ========= [2004/07/27 16:07:04, 1]
2005 Apr 25
1
wbinfo -t fails but other wbinfo and getent items work.
Problem: wbinfo -t fails. As long as it fails, I am unable to map sids to Group Names. I need this functionality for my application. I can use just about everyother function of wbinfo at least partially... Distro: Debian woody. Packages: ii samba 3.0.11-0woody1 a LanManager-like file and printer server fo ii samba-common 3.0.11-0woody1 Samba common files used by both the server a
2004 May 10
0
"user 'root' does not exist" in winbindd.log after upgrade from 3.0.2a to 3.0.3
Dear list, After the upgrade from 3.0.2a to 3.0.3 I see in my winbindd.log file all the time "user 'root' does not exist" messages. I didn't get these messages with my 3.0.2a samba setup, but after the upgrade to 3.0.3 it is flooding my winbindd.log file, sometimes I get this message every minute in my log file. winbindd.log ========== [2004/05/10 00:01:00, 1]
2005 Jun 16
0
repeating 'lp' group lookup.
hello. i have configured samba 3.0.14a for sharing users homes with winbind authenticate. winbind works fine, but i cannot start smbd. it just hatled on startup with following messages: -------- [2005/06/16 12:04:10, 4] param/loadparm.c:lp_load(3938) pm_process() returned Yes [2005/06/16 12:04:10, 3] param/loadparm.c:lp_add_ipc(2401) adding IPC service [2005/06/16 12:04:10, 3]
2004 Feb 26
0
Winbind log question.
Hi. I got samba-3.0.2a-1 on fedora core 1 working as a domain member. We have some shares there and the domain users is authentificated by a windows 2003 DC. Everything runs smooth but this comes up in the log every time a cronjob By root is runned. The samt thing if I log in.. ------- winbindd.log ----------- [2004/02/26 23:01:01, 1] nsswitch/winbindd_group.c:winbindd_getgroups(954) user
2005 Apr 18
1
\PIPE\NETLOGON (NT_STATUS_DOMAIN_CONTROLLER_NOT_FOUND)
Help, wbinfo -t fails with the error in subject, and getting sids of groups that aren't BUILTIN fail. Everything else seems to work. Note: I am not converting my kerberos tickets to krb4, is this necessary? (It used to work without it..but now it seems not to work.) I get no errors from kinit. all other wbinfo requests succeed with the exception of looking up the SIDS of groups that
2004 Aug 31
4
winbind problem (?) on samba 3 ADS
Hi, I have installed samba 3.0.6 based on the "Official HOWTO" to join out Active Directory environment, with winbind and pam support. I have join the samba to the domain using "net ads join -Umyloginame". I can do the "wbinfo -g", "getent passwd" and "getent group" correctly. I also can list shares on other machine, using kerberos: # kinit
2006 Feb 22
2
Samba 3.0.21b winbind crash
I'm using Samba 3.0.21b on SuSE 9.3 Pro (x86) with the binary RPMs from samba.org/suse.com (3.0.21b-1.1.2-SUSE-SL9.3) on a Domain Member Server in ADS mode with winbind against W2K3 SP1 AD servers and idmap uids/gids stored in a central OpenLDAP directory. Unfortunately, winbind gives me a hard time and reproducibly dies with a PANIC on a "wbinfo -g", although I think I've
2007 Aug 24
1
Samba, Winbind and Active Directory
Hi, I am trying to set up Samba joining Active Directory. I have done this successfully before and have most of my previous files. Here is the issue I am seeing. I can "kinit administrator@HQ.MYDOMAIN.COM" I cannot "net ads join -U administrator" I get thus message: "Failed to join domain: Invalid credentials" The only error I seem to find is in my winbind log
2003 Jul 23
1
Samba 3.0 beta 3 issues
Hi there, I'm using Samba 3.0 beta 3 on RH 9 (connecting to a Windows 2000 domain, as a member server) and I'm having trouble keeping samba running reliably. At random times it seems to stop recognising names from the domain. Restarting winbind fixes the problem, but then it occurs randomly again, usually once or twice a day. At least once it has fixed itself after being broken overnight
2003 Nov 04
1
Samba 3/ADC/Winbind problem
Greetings all. I am banging my head about this one, I will try to be as specific as possible, bear with me please. I have a W2KDC ADC, and trying to join a Samba 3 linux workstation to it. What works: net join: succeeded wbinfo -t: checking the trust secret via RPC calls succeeded wbinfo -m: return to prompt, no output wbinfo -u: correct list of local + AD members
2004 Dec 21
1
Winbind problem revisited
Okay, I started over from scratch with my samba server rebuild, but I am still getting some weird issues. Here are my config files of importance: --------------/etc/samba/smb.conf-------------------- # Samba Configuration File [global] workgroup = WAYNE realm = WAYNE.LOCAL server string = Samba Server security = ADS password server =
2005 Jul 22
1
winbind lookup errors
Hello Samba folks, I have recently begun seeing some disturbing behavior from winbind. Winbind will fail to look up users and groups. Examples: The machine is configured to use winbind as a nss module. "getent passwd <username>" will yield no results. "wbinfo -n <username>" will yield "Could not lookup name <username>" "wbinfo -g"
2004 May 25
0
upgrade from 1.x to 3.0.0.4 : veritas backup exec cannot connect
I figured out a previous issue to allow you to connect veritas BE to a samba system. You basically just defind a c$ share, and it was happy (Veritas BE version 8.5 Rev 3572) Now, I cannot get the user defined share to connect for the life of me anymore. The backup user can connect using windows shares, but within the application, I'm out of luck. It keeps asking for a username/password
2004 Jan 07
0
Samba3.0.1pre1 winbind failing against domain groups(ADS)
Winbindd is having trouble finding the Domain Admins group in my domain. It appears to be searching for the group but does not show what domain it's looking into - then it tries the local PC (ANC-Gentoo): log.winbind: [2004/01/07 13:20:43, 3] nsswitch/winbindd_group.c:winbindd_getgrnam(237) [23792]: getgrnam Domain Admins [2004/01/07 13:20:43, 5] nsswitch/winbindd_acct.c:wb_getgrnam(522)
2004 Feb 12
0
Veritas Backup Exec 8.6 & Samba: Take Two!
Hi, gang, There have been numerous postings, scattered across various Internet forums (including this one), about problems encountered using Veritas Backup Exec 8.6 and higher with Samba-sourced shares from *nix servers. In my particular case, I have a Windows NT Server 4.0-based backup system, which is supposed to be able to back up the other Windows systems on the LAN, plus several SPARC boxes
2000 Jul 04
0
REQUEST: Veritas Backup Exec 8.0
On Mon, Jul 03, 2000 at 02:48:59PM -0700, Richard Fox wrote: > > Running the SAMBA that is released with RedHat 6.2, Veritas Backup Exec > 8.0 does not work. However, when running the latest dev version of SAMBA > Backup Exec does work. What files were changed to fix this bug? I would > like to update what I am running without having to go to the dev version. > > I have
2009 Apr 01
0
Symantec Backup Exec (formerly Veritas) agent
I'm just wondering if anyone else here is using this? The majority of jobs on our CentOS5 server "fail" by "Communications failure" right at the end, apparently on the very last file which, however, is recoverable, as is the whole archive. In more than half these failures, the Linux agent has stopped and, in about half of those, crashes leaving a backtrace. I had similar
2008 Jul 17
0
Interdomain Trust, wbinfo works on both servers, getent doesn't work on one server
Hi I have a problem with an interdomain trust where on the PDC for DomainA, everything works perfectly. getent returns local and DomainB usernames. On the PDC for DomainB, it's DomainB works fine, but getent only returns local usernames and groups, it doesn't return the usernames or groups for DomainA. wbinfo -u and wbinfo -g work fine and return all DomainA's usernames and groups.