search for: rpunt

Hey list, I've got a problem with my PDC/BDC setup. They're both running 3.0.23c on Sarge, and I've verified that both the PDC and BDC will authenticate users. test-pdc:/etc/samba# testparm Load smb config files from /etc/samba/smb.conf Processing section "[netlogon]" Loaded services file OK. Server role: ROLE_DOMAIN_PDC test-bdc:/var/log/samba# testparm Load smb config

...OLE_DOMAIN_PDC test-bdc:/var/log/samba# testparm Load smb config files from /etc/samba/smb.conf Processing section "[netlogon]" Loaded services file OK. Server role: ROLE_DOMAIN_BDC smb.conf is pretty similar on both machines; the full file is included below. Here are the differences: rpunt@rpunt:~/documents/Samba3/backup$ diff pdc.smb.conf bdc.smb.conf 3,4c3,4 < netbios name = GSS-PDC < server string = Samba 3 PDC --- > netbios name = GSS-BDC > server string = Samba 3 BDC 13c13 < os level = 255 --- > os level = 200 15,16c15,16 &lt...

I have joined samba to a 2003 active directory server. If a samba shared dir is owned by root, how does active directory manage it? more specifically, how are the permissions mapped? administrator to root? i have seen reference to a parameter in smb.conf to "username map", but i don't see reference to it in either of the John Terpstra Samba books so that can't be the bridge

All, I've got a Samba 3 PDC serving numerous XP clients, and I'm getting an error I wouldn't have expected. When trying to rename an XP machine joined to the domain (via "netdom renamecomputer"), the command fails unless the specified domain user has UID 0. The command in question: netdom renamecomputer %COMPUTERNAME% /newname:%NEWNAME% /userD:DOMAIN\USER

Hi, A few days ago PDC crashed and I setup a new PDC with the same domain name. I have recreated the user accounts but when the users login, windows xp clients create a new profile. Is there a way to make the windows clients use the old profiles? Thanks. -- Erol

I'm not even sure this is a problem with Samba, but here goes* >From smb.conf: log file = /opt/samba/var/log/%m.log As I understand it, this option will create $CLIENT_NETBIOS_NAME.log whenever a client contacts the Samba server in any way. However, I've got clients from outside this samba server's subnet contacting the samba server. I can prove that because a PCs NetBIOS name

Regarding yesterday's message about repeated "signal 11" errors in 2.2.12, I was able to capture a backtrace. #0 0x401543ae in waitpid () from /lib/tls/libc.so.6 #1 0x400e9d12 in system () from /lib/tls/libc.so.6 #2 0x0815ea98 in smb_panic () #3 0x0814d885 in fault_report () #4 0x0814d8e2 in sig_fault () #5 <signal handler called> #6 ldap_free_urllist (ludlist=0x185) at

All: I'm running Samba 2.2.8 as a PDC, using Netscape Directory Server (don't ask :) for an LDAP backend. Is there any technical reason why Samba and LDAP services have to reside on the same server? My predecessors had a lot of trouble getting the two to play nicely when the services were split between two servers, to the point that "don't split samba and LDAP" is now the

All, Since upgrading to 3.0.23d on several linux servers, I'm seeing the following error repeatedly in my logs: Jan 2 15:05:49 boothost smbd[27935]: [2007/01/02 15:05:49, 0] smbd/nttrans.c:call_nt_transact_ioctl(2332) Jan 2 15:05:49 boothost smbd[27935]: call_nt_transact_ioctl(0x90078): Currently not implemented. Aside from the obvious, what does this error mean? I've googled for

All, Since installing my shiny new Samba3 PDC (3.0.23d, ldapsam backend), I've had one recurring issue that's been driving me nuts. Once a minute, Samba on one of the client servers logs the following: getsmbfilepwent: user name cmeyer2 has a negative uid. getsmbfilepwent: user name jhundley has a negative uid. Running pdbedit does the same thing: boothost:/var/log# pdbedit -Lvu

All, I found the solution. By stopping NSCD and THEN purging the passwd table, the bad entries were cleared. Ryan -------------- next part -------------- ------------------------------------------------- This email transmission and any documents, files or previous email messages attached to it may contain information that is confidential or legally privileged. If you are not the intended

What does the list think of setting "locking = no" on the netlogon share for a PDC? The man page for smb.conf says we should never need to set the parameter, but given that it's a read-only share for most users, I have a hard time discerning any downside to this. Thoughts? Ryan -------------- next part -------------- ------------------------------------------------- This email

You could do what we do - just replace the local machine policies each time you rev the policy set. They're stored in c:\windows\system32\grouppolicy. Using gpscript.exe (Google for it, don't have a specific site) you can dump the contents of either registry.pol file to text. You can also recombine textfiles back into a .pol file, and subsequently rev the gpt.ini file so your new .pol

I'm in the process of replacing a Samba 2.2.12 PDC with Samba 3.0.14a-Debian. An LDAP database serves as the user data store, and I've made no changes to the Samba 2.2.x-compatible LDAP records. Since I don't relish LDAP schema changes, I've specified ldapsam_compat as my passdb backend; I figured that since I was already running a compatible LDAP schema, there was no need to make

Debian Sarge, Samba 2.2.12 (legacy install), openLDAP 2.2.17, connecting to a PDC running Samba 2.2.8a. The machine in question failed DIAGNOSIS.txt step 3. I've got a really odd issue -- a Samba server that can "smbclient -L" everyone but itself. Samba still serves shares and PDC authentication works fine, but this failure is annoying, and as such, must be fixed. :) -- issued