similar to: NT4 PDC and Samba 3 issues...

I upgraded an old Samba 2.x install on Debian that I had at a customer location. Authentication to the PDC was via winbind. Everything worked fine in the past except the RAID died so I rebuilt the RAID, copied over the old volume, and ran apt-get update && apt-get upgrade. Now I have some really weird Samba problems: I can connect to my share on Samba. I can create a dir, a file,

I have been asked to set up a customer with Exchange 2000. I have tried to convert them, so please don't suggest it. We have 3 boxes we can use to do this with. We want to use Samba 3 as the PDC (ldap backend) and Samba 3 as BDC (ldap backend), with the exchange box as a domain member. Will this work? If not, what is the best way to ensure that : a. We have PDC and BDC for authentication

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 am running a fileserver with smbd here. The server is a 64bit 2.8 GHz Celeron D with 2GB RAM, running 64bit Debian, Samba version 3.0.23c. It is running as a pure fileserver so its only CPU load is serving files. The client I am doing the tests from is WinXP Pro SP2. It is connected via Intel e1000 gbit ethernet (both the server and client use e1000 chipsets). I have done a raw tcp

Dear all I have 2 server: samba server on fedora core 2 and windows NT 4 server. Each server have different ip address 1.samba PDC server on fedora with ip: 192.168.0.xxx 2.windows NT 4 PDC server with ip: 192.168.1.xxx I want to all user in samba server can sharing file and browse network share in NT4 server , and all user in NT4 server can sharing file and browse network share in

Hi, I have one NT4 PDC that needs to be migrated to Samba-PDC. No Active Directory. Just users, groups, windows shares... the works. I'm seeing that Samba-3.x is "very PDC-oriented". I like that. But, so far, Samba-3 is still in beta/pre-release versions and in my "stock" distribution, Samba is on 2.2.7a version (2.2.7a-security-rollup-fix). Should I wait for Samba-3?

Okay Ive had a day of it today , and I thought I would share this little support event experienced today. A Client site of mine runs Samba 2.2.8a connecting to a series of Windows XP boxes via a Netgear Switch/Hub. Earlier in the week they reported that certain applications, most notorously Symantec ACT were performing at super slow speeds. A non site investigation showed that any file

Hello, I want to migrate from an old NT4 PDC to a Samba version 3.0.26a. My BDC configuration for migration is [global] workgroup = DOMAIN server string = %h server Samba %v interfaces = eth0, 192.168.1.0/24, lo bind interfaces only = Yes security = DOMAIN map to guest = Bad User passdb backend = tdbsam passwd program =

I have an urgent need, Is it possible to connect an NT4 Standalone server to a Samba-LDAP PDC ?? I am trying to do that but keep getting the same error when trying to change an NT4 standalone server to the Samba-LDAP PDC. Error message : The machine account for this computer either does not exist or is inaccessible. log.smbd : [2004/08/10 22:29:03, 5] lib/smbldap.c:smbldap_search(932)

I'm having a really strange problem with winbind and my NT4 PDC. The PDC was here before I started working here, so I'm not sure what all has been done to it. Here's the layout: * NT4 PDC (no BDC)- Up to date with all service packs and hotfixes. Running Cyberwall-Plus firewall. * RHL 7.2 (2.4.9-31custom) with Samba 2.2.4 (compiled from src). I was able to join the domain. The

Hello everyone! I'm having a strange issue with Samba. Here's the setup: WindowsNT 4 PDC Windows 2000 clients. Samba 2.2.7 on a Mandrake 9 system that has successfully joined the domain and is visible when the client systems browse the network. (config files and error log samples below) The problem is getting the Win2k clients to authenticate when they try to connect to shares that

Hi ! We're trying to migrate our NT4 PDC into a Samba one. Our env : NT4_PDC is in subnet A and also provide WINS service SAMBA_SRV is in subnet B and is running : * samba-3.0alpha23 * openldap-2.1.16 * smbldap-tools-0.7 from IDEALX samba is compiled with --with-ldap --with-ldapsam --with-syslog openldap is first populated with : # ldapadd -x -h localhost -D "ROOTDN" -W -f

Hello, I have a little problem with samaba... well... with windows nt, samba works fine. I'll try to explain it: My net has 2 servers with NT4, a pdc and a bdc. Well, my intentions is to eliminate de NT4 PDC and put a Samba PDC. So I made the next steps: 1-. In BDC, Administrative Tools - Server Administrators (i think) and there i select the BDC and click in the menu to "Eliminate

Hi all I am attempting to install winbind on a Redhat 9 machine with an NT4 PDC. The winbind version is samba-2.2.7a-7.9.0 as a stock RH install. I have followed the install instructions on the man page and I still get the errors shown below. I have searched google for the STATUS_BUFFER_OVERFLOW (0x80000005)error and the plaintext password authentication failed error but nothing I've found

Guess I'm a bit dense here. No problems with Winbind working with Samba 3.0, 'getent' and 'net groupmap list' all reveal good stuff. I'm able to use user and group names just fine in the shares, given that the group names don't have spaces in them. How in the world do I get the groupmapped name of 'domadmin' to work as an alias of 'Domain Admins'? That

Hi. I'm evaluating the possibility of migrating my network from NT4 to Samba 3. I have a PDC on my main office running WINS, a BDC on a branch office 200Km away also running WINS, and another BDC on a branch office 450Km away also running WINS. I have the following constraints: -I must have a BDC on each branch office, and PDC on my main office. -I must have a WINS server each office. -I

I have 2 different shares one with [Share1] valid users = @"DOMAINA+Domain Users" [Share2] valid users = @"DOMAINA+SpecialGroup" Members of the latter group cannot access Share2. No one can. #getent group |grep Special DOMAINA+SpecialGroup:x:10001:DOMAINA+User1,DOMAINA+User2,DOMAINA+User3 #wbinfo -g |grep Special DOMAINA+SpecialGroup I changed the

After upgrading to samba-3.0.30 on domain member servers using NT4 as PDC and running winbind users can no longer access the shares, they get prompted for passwords (which shouldn't happen) yet still cannot connect. Dropping back to 3.0.28a works (even after adding the recent security patch) fine. What can I provide to get this fixed? Thank you, -- Chris

Is anyone here running Samba 3.0 successfully with an NT4 style domain, with the Samba box operating as the PDC? -- Jason A. Nunnelley JasonN.com is my website - all opinions expressed were mine at some point.

Reading through the Samba3 -By Example guide and I'm confused with the statement section 9.2 http://www.samba.org/samba/docs/man/Samba-Guide/ntmigration.html#id2594565 about accessing the SAM and Security sections of the registry will render the PDC non operable. Its clear from the text if you go and edit the registry(regedit etc..) so you can read the entries your PDC will not work.