similar to: NT PDC authentication failure

Hi all. I have a CentOS server: CentOS release 5.7 (Final) 2.6.18-274.3.1.el5 x86_64 I have two SSD disks attached: smartctl -i /dev/sdc smartctl version 5.38 [x86_64-redhat-linux-gnu] Copyright (C) 2002-8 Bruce Allen Home page is http://smartmontools.sourceforge.net/ === START OF INFORMATION SECTION === Device Model: INTEL SSDSA2CW120G3 Serial Number: CVPR13010957120LGN Firmware

Workstations in our network fail to make ODBC SQL server connections using NT authentication mode. This is our situation: We are running Samba 2.2.7a as PDC. We also have one Windows 2000 server running MSSQL server and being a member of this domain. The MSSQL server is used by an accounting program (Exact Globe 2000) running on several client computers in our network (members of the domain).

Hi all, i've problem with the authentication via winbind on a Windows NT PDC. Environment: Samba Server: z800 Linux SLES8 as VM guest on one LPAR SAMBA 3.0 alpha23 PDC: Windows NT 4.0 SP 6a The samba Server is member of the domain, i can check the secret with net rpc testjoin and wbinfo -t. I see the groups and user from the domain with getent group and getent passwd. When i try to

I've got a 1Tb USB disc that appears to be dying - eg it took about 10 days (!) to run 'badblocks -nsv /dev/sdc' and it only did less than 2% in that time. Read access became _really_ slow. So there's definitely something amiss and I've got it offline. There's no drama about the content as I have other backups and I'm resigned to junking the thing, but I'm curious

I'm relatively new to Samba so please excuse any inconsistencies with my terminology. I'm running Samba 2.0.6 on Solaris 2.6 and having problems creating the Samba server machine account on an NT PDC. I already have an NT based domain 'PCDEV' which consists of a number of NT 4.0 workstations as well as a PDC ('AULE') and BDC running NT 4.0 Server with sp5 (??). My NT

Hi all, I want to make a Samba Sever as amember of a Domain, using a Windows NT 4.0 as PDC. I have my smb.conf configured to do this, but users ca't connect on Samba useing the Windows NT account. Is it possible or I have to create them on a smbpasswd to make them login on it? I have a Samba Server 3.0.7 running under a Slackware Linux 10.0, with Kernel 2.6.8.1. I'm sending my smb.conf

Okay leave it to me to screw crap up! This worked before i started to play with some machine's ip addresses. Now im screwed and its not working at all. I will go through everything i have done from start and hopefully someone can tell me what I need to do to fix it. Please make two notes before you read this, i am not the person who setup the samba server on this linux box(running Debian)

I installed a fresh copy of Debian 4.0 and Xen 3.1.0 SMP PAE from the binaries. I had a few issues getting fully virtualized guests up and running, but finally managed to figure everything out. Now I''m having a problem with paravirtualized guests and hoping that someone can help. My domU config: # # Configuration file for the Xen instance dev.umucaoki.org, created # by xen-tools

I've seen similar cases where a USB drive appears to fail but the SMART reports success. The most recent was a 500 GB disk which had internally a Seagate Barracuda SATA drive. It appeared to work well until I sent it a largish (7GB) tarball. As well as SMART I ran a surface check and exercise, all passed. The tar kept failing. I can't test further, the disk has been broken up for

On Thu, Jul 7, 2016 at 10:00 AM, Bruce F Bading <badingb at us.ibm.com> wrote: > > Hi Gentlemen, > > Thank you both for your valued opinion. I do however agree that public key > authentication cannot be fully considered MFA as have 2 PCI QSAs I have > spoken with. This is because it is not enforceable server side. Many > things can affect client side security. >

Hello all We are experimenting with btrfs and we''ve run into some problems. We are running on two Sun Storage J4400 Arrays containing a total of 48 1 TB disks. With 24 disks in the btrfs: # mkfs.btrfs /dev/sd[b-y] WARNING! - Btrfs Btrfs v0.19 IS EXPERIMENTAL WARNING! - see http://btrfs.wiki.kernel.org before using adding device /dev/sdc id 2 ... adding device /dev/sdy id 24 fs

Forwarded message: >From BMCCULLO at fcc.gov Fri Nov 6 12:50:07 1998 Message-Id: <s642efa3.006 at fcc.gov> X-Mailer: Novell GroupWise 4.1 Date: Fri, 06 Nov 1998 12:51:24 -0500 From: Bruce McCullough <BMCCULLO at fcc.gov> To: mai at ms.uky.edu Subject: S-Plus RNG Mime-Version: 1.0 Content-Type: text/plain Content-Disposition: inline Mai, Someone forwarded to me your e-mail about

mkfs.ext4 fails to create 38TB file system on CentOS 6.4 64bit with this error: mkfs.ext4: Size of device /dev/vg02/vtapes too big to be expressed in 32 bits using a blocksize of 4096. More details follow: # uname -a Linux tzbackup 2.6.32-358.18.1.el6.x86_64 #1 SMP Wed Aug 28 17:19:38 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux # fdisk -l /dev/sdc Disk /dev/sdc: 41996.7 GB, 41996727091200

Hello Samba Gurus, I have configured my Samba install to be a domain member of a NT4-Style domain. The version of samba used is 3.0.13. The domain joining process worked fine (net rpc join). An excerpt of smb.conf is provided at the end for reference. The problem is that when users access this server, they are challenged for the username password. I was of the impression that this process would

Hi all, Like certainly many members of those lists (SAMBA's list), I would like to contribute to SAMBA project. The main reason is because when you write something you must absolutely be familiar with the subject. It will give me oportunity to be (more) familiar with some kinds of SAMBA Spec. Since I read samba mailling list, many questions are post about SAMBA PDC, BDC, etc, interaction

Environment Summary: Samba version 3.0.2-6.3E (Red Hat AS 3.0) Kerberos version 1.3.4 (MIT download - Kerberos 5 release 1.3.4) openLDAP version 2.0.27-11 (Red Hat version - we may try 2.2.13 or 14) pam_smb version 1.1.7-1 (Red Hat version) Red Hat AS 3.0 (2.4.21-15.0.2.ELsmp kernel on a Dell 1750) Windows 2003 using Active Directory One-way trust from Windows 2003 to an NT 4.0 PDC smb.conf

We recently tried the upgrade to 2.0 Beta series (just finished testing Beta 4) on our network. Everything works fine with 1.9.18pl10, but once we start 2.0 in its place we start getting the following in the log files: [1998/12/17 05:00:12, 1] smbd/files.c:file_init(219) file_init: Information only: requested 10000 open files, 246 are available. [1998/12/17 05:07:52, 1]

I thought that it was quite impossible to do that due to the Domain SID as well as the SAM list that currently Samba is unable to retrieve. (Not that it would have helped me any, since our old NT 4.0 PDC took a major Hardware failure.) How would one duplicate the SID, is that possible with 'smbpasswd -S' from the new Samba DC? Regards, Robert Adkins II IT Manager/Buyer Impel

Dear all, When I try to browse the NT client using smbclient -L <NT-Client>, I saw the following output : --------------------------------------------------------------------------- added interface ip=203.154.148.70 bcast=203.154.148.255 nmask=255.255.255.0 Domain=[MECH] OS=[Windows NT 4.0] Server=[NT LAN Manager 4.0] Sharename Type Comment --------- ---- -------

Hello, I have a weird problem after adding new PV do LMV volume group. It seems the error comes out only during boot time. Please read the story. I have couple of 1U machines. They all have two, four or more Fujitsu-Siemens SAS 2,5" disks, which are bounded in Raid1 pairs with Linux mdadm. First pair of disks has always two arrays (md0, md1). Small md0 is used for booting and the rest - md1