similar to: getsmbfilepwent problem - Samba concerned with negative UIDs

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

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

Hi all I am sure that there is some mention of this error in the docs somewhere but I could not find it. So, sorry for repeating it here. I have installed samba 2.0.3 on solaris 2.5.1 I carried out all the tests described in the documentation. They were all successful. Bu from an NT server I can't do this net use z: \\server_name\\tmp System error 86 has occurred The specified network

All, I'm using an LDAP backend for a test PDC/BDC setup. Both the PDC and BDC are using the same LDAP server. Both the PDC and BDC are running 3.0.23c on Sarge, and I've verified that both the PDC and BDC will authenticate users via smbclient. XP clients are able to login to the domain fine, and all is generally swell. My PDC is also my WINS server, and I've verified that XP clients

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

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

Anyone else seeing problems doing pxe boots off the latest dag/rpmforge syslinux packages? Versions 3.35 works, doing the tftp request like this: Jun 18 06:01:19 boothost in.tftpd[25947]: RRQ from 172.16.0.26 filename /centos5-i386/pxelinux.0 Jun 18 06:01:19 boothost in.tftpd[25947]: tftp: client does not accept options Jun 18 06:01:19 boothost in.tftpd[25948]: RRQ from 172.16.0.26

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

Dear Listmembers, apparently my attachement was not distributed via the list, therefore I add it once again to this email; plain text following my question. Many thanks for any suggestion in advance: I am using a SPARC ULTRA 60 / running SuSE sparc linux 7.3 as server for our M$-Network. I recently installed samba-2.2.8a from SuSE (compiled src-rpm), since then I am facing problems when attaching

Ah, yes. One of the many differences between the US and the rest of the world. >>> support@drdos.info 4/3/2007 2:52:16 PM >>> john beaman wrote: > I too was curious about this, so I copied the text into Babel Fish, and this is the result: > > I miss of the 2/04/2007 to the 11/04/2007. I will answer your message as of my return. For any urgency, to contact Emmanuelle

Hi ... I am desperate now to solve this problem ... this is my absolute last resort attempt! I have read of the problem on a number of posts/newsgroups/webpages - but there a very little solutions - or causes - none of the solutions have worked for me! Basically my samba is happily running and I can connect to it fine from 9x clients and from 2k client as a workgroup. However..... If I try to

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

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

Our current environment is Samba 3 with an LDAP backend. I want to move to Samba 4 with an AD backend. We already have the AD servers in place and Samba 3 servers are using AD absolutely perfectly. The last remaining piece is to move Samba 3->4. My existing Samba 3 configuration looks like this: [global] server string = 1220 Boothost Server netbios name = BOOTHOST-1220

Dear samba-users We are experiencing some rather long logon times using SAMBA 3.5.6 on Debian Squeeze + Windows 7 and while trying to find out why we raised the loglevel to 5 resulting in a rather large logfile. But this did give us a hint as to why we experience so long logon times. It seems that samba is going through the whole user-database with all usernames and machine-accounts. Eventually

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'd like to change Samba passwords from win95 and NT4 clients. I use security=user. I don't give shell access to every user, so they can't use smbpasswd. I've tested from a win95 client with the precompiled samba-2.0.4b.i386.rpm: net pass \\greg greg test1 test2 I'd used smbpasswd to change greg's password to test1 on host greg prior to this. Here's the smbpasswd

I know it is a moderated list - just do not know how to get to the moderator. Was just reinstalling suse 9.1 on top of an existing 9.1 (with samba) (it solved another issue with the monitor but created a samba problem) applied all patches reinstallation remembered all settings correctly, even the smb.conf file, but smbd does not start anymore. , I get a