Re: [Samba] Solaris 11 can't join Active Directory Domain
On 02/04/2013 03:31 AM, Jake Carroll wrote: Do you have an Oracle support contract for OS/integration? I'd log it in MOS if I were you, and see what they say. Approach this from two angles ;). I've contacted Oracle in the first place. According to them, it's not a Solaris issue. Ihsan -- ih...@dogan.ch http://blog.dogan.ch/ -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Solaris 11 can't join Active Directory Domain
Hi, On 02/06/2013 11:46 AM, Andrew Bartlett wrote: I'm running a Active Directory domain on Samba 4.0.1 and I'm trying to join a Solaris 11 machine this domain: # smbadm join -u Administrator DOMAIN After joining DOMAIN the smb service will be restarted automatically. Would you like to continue? [no]: yes Enter domain password: Locating DC in DOMAIN ... this may take a minute ... Joining DOMAIN ... this may take a minute ... failed to join DOMAIN: UNSUCCESSFUL Please refer to the system log for more information. In /var/adm/messages: Jan 30 21:33:34 host smbd[827]: [ID 232655 daemon.notice] ldap_modify: Insufficient access Jan 30 21:33:34 host smbd[827]: [ID 702911 daemon.notice] Workstation trust account update failed Windows 7 clients are able to join, but Solaris 11 fails. Kerberos seems to be fine: # kinit oskar Password for os...@domain.com: Warning: Your password will expire in 41 days on Wed Mar 13 19:44:52 2013 But if I run it for Administrator: # kinit Administrator Password for administra...@domain.com: Warning: Your password will expire in 41 days on Wed Mar 13 18:36:46 2013 kinit: no ktkt_warnd warning possible Any idea what is going wrong here? Does this work against a freshly provisioned Samba 4.0.3 domain? We fixed a lot of ACL related things with that release. Haven't tried. I'm running the AD now on a 2008R2 server. Ihsan -- ih...@dogan.ch http://blog.dogan.ch/ -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
[Samba] Password Expiration Notice
Hello All. I've installed a new Samba4 server acting like Active Directory Domain Controller. I've joined the domain with a windows 7 and a mac os x workstations. When user password is near to expiration, I'd like that, at login time, it advice that password is near to expiration date. If I user kinit from console it advice me, but it doesn't advice by network login. Is there an option that I must add to smb.conf? I've googled but I've not found an answer. Thanks a lot. Daniele Gallarato __ Gli animali sono miei amici...e io non mangio i miei amici. -- George Bernard Shaw -- http://www.saicosamangi.info/ -- -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Trust problems after upgrade from 3.5 to 3.6
Hello, I think I stumbled over the same issue when testing winbind and interdomain trusts on samba 3.6 these days. It is a bit hard to find, but man idmap_ldap says that the secret must be stored with net idmap secret DOMAIN SECRET and I think I used '*' as DOMAIN (for any domain) That made winbind with ldap work for me. Bye, Oliver Am 05.02.2013 09:04, schrieb Andrea Venturoli: On 02/04/13 19:25, Andrea Venturoli wrote: Hello. My setup: _ one Samba 3.5 domain (), with a PDC and a BDC, both running FreeBSD; _ one AD domain () running on two Windows 2003 DCs; _ bidirectional trust between the two domains. Everything used to work until I moved the PDC from Samba 3.5 (EOL'ed) to 3.6; now, users from domain cannot access the PDC's shares. I used to have in smb.conf: idmap backend=ldap:ldap://localhost/ idmap alloc backend=ldap idmap alloc config:ldap_url=ldap://localhost idmap alloc config:ldap_base_dn=ou=idmap,dc=,dc=xx idmap alloc config:ldap_user_dn=cn=root,dc=,dc=xx idmap cache time=120 idmap uid=15-20 idmap gid=15-20 template shell=/sbin/nologin idmap config :backend=nss idmap config :range=1000-99 After the upgrade I changed it this way: idmap config *:backend=ldap idmap config *:range=15-20 idmap config *:ldap_url=ldap://localhost/ idmap config *:ldap_base_dn=ou=idmap,dc=,dc=xx idmap config *:ldap_user_dn=cn=root,dc=,dc=xx idmap cache time=120 template shell=/sbin/nologin idmap config :backend=nss idmap config :range=1000-99 I see many errors like the following in log.winbindd-idmap: [2013/02/04 19:22:20.847184, 1] winbindd/idmap.c:249(idmap_init_domain) idmap initialization returned NT_STATUS_ACCESS_DENIED In log.wb- [2013/02/04 19:20:59.364510, 0] rpc_client/cli_pipe.c:3240(cli_rpc_pipe_open_spnego_ntlmssp) cli_rpc_pipe_bind failed with error NT_STATUS_ACCESS_DENIED Please, any help is appreciated. bye Thanks av. P.S. I'm also seeing this: winbindd[65589]: get_credentials: Unable to fetch auth credentials for cn=root,dc=,dc=xx in * Connection to LDAP works form smbd (for which I had set credentials with smbpasswd -w); how whould I do it for winbindd? bye Thanks av. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
[Samba] NTLM autentication problems
I'm trying to configure Squid ntlm autentication on Samba4 DC. I followed Squid and Samba's documentation and i got success when I login with user natalia.silva, but if I log with natalia.vaz i get the error -- Natália Vaz Silva Administradora de redes -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
[Samba] Reverse lookup Zone not update
Dear all I have setup samba4 ad. It is working correctly. I have used internal DNS with samba. Forward lookup zone is ok. but not create reverse lookup zone. if i manualy created reverse zone. it is working. But it not update automatically. what is the reason for that. any body help me. Thank You Samith -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Strange winbindd messages
Hi Andrew,
Thanks for getting back to me.
On 02/07/2013 04:52 PM, Andrew Bartlett wrote:
On Fri, 2013-02-08 at 08:43 +1100, Andrew Bartlett wrote:
On Wed, 2013-01-23 at 11:59 -0500, John Center wrote:
Hi,
We are running samba v3.6.3 on Ubuntu 12.04 server. This is being used
with FreeRADIUS for wireless authentication with AD. We just logged a
set of messages from winbindd that I don't understand:
Jan 23 10:35:28 as3 winbindd[25371]: [2013/01/23 10:35:28.056846, 0]
rpc_client/cli_netlogon.c:677(rpccli_netlogon_set_trust_password)
Jan 23 10:35:28 as3 winbindd[25371]: dcerpc_netr_ServerPasswordSet{2}
failed: NT code 0xc2a5
Jan 23 10:35:28 as3 winbindd[26636]: [2013/01/23 10:35:28.105143, 0]
rpc_client/cli_netlogon.c:671(rpccli_netlogon_set_trust_password)
Jan 23 10:35:28 as3 winbindd[26636]: credentials chain check failed
Jan 23 10:35:28 as3 winbindd[25518]: [2013/01/23 10:35:28.310288, 0]
rpc_client/cli_netlogon.c:671(rpccli_netlogon_set_trust_password)
Jan 23 10:35:28 as3 winbindd[25518]: credentials chain check failed
Jan 23 10:36:28 as3 winbindd[25371]: [2013/01/23 10:36:28.121861, 0]
rpc_client/cli_netlogon.c:671(rpccli_netlogon_set_trust_password)
Jan 23 10:36:28 as3 winbindd[25371]: credentials chain check failed
Authentications went through ok at 10:35:23 again at 10:35:29. We
haven't seen them before, searching, I couldn't find much info. What
do these messages mean? What would have caused them? Do we need to be
concerned? Any help would be greatly appreciated.
What is happening here is that we are trying and failing to change our
machine account password. Can you try Samba 3.6.12 and see if the
changes in the meantime have fixed this?
Can winbindd change the machine account password? This isn't being done
by us manually.
Looking into this some more these links suggest a server-side error:
http://www.tek-tips.com/viewthread.cfm?qid=1487092
http://support.microsoft.com/kb/306091/en-us
Looking at these links, are you suggesting that the DC database is being
locked at this point in time, so when an auth request is being made, it
fails?
Is there anything in the server event log to match this error?
I'm trying to get access to the DC event logs to look into this.
Thanks.
-John
--
John Center
Villanova University
--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Trust problems after upgrade from 3.5 to 3.6
On 02/08/13 13:48, Oliver Freyd wrote: Hello, I think I stumbled over the same issue when testing winbind and interdomain trusts on samba 3.6 these days. It is a bit hard to find, but man idmap_ldap says that the secret must be stored with net idmap secret DOMAIN SECRET and I think I used '*' as DOMAIN (for any domain) That made winbind with ldap work for me. Hello. First off, thanks for answering. After my previous message, I had already found out the above and did it. I saw some improvement: _ the logs about winbind not being able to fetch auth credentials are gone; _ smbclient -L ... succeeds, so authentication is in fact working; _ however, access to shares still is denied to users from the trusted domain. It looks like Samba authenticates the user (against the DCs of the trusted domain) and accepts it, but somehow fails to recognize him, so he won't be correctly matched against valid users. Just to be clear: users from the trusted domain can access public shares, as long as they provide a correct password. I'm still investigating this and I'll report anything I'll find. Any further suggestion is still appreciated. bye Thanks av. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Trust problems after upgrade from 3.5 to 3.6
Am 08.02.2013 17:54, schrieb Andrea Venturoli: On 02/08/13 13:48, Oliver Freyd wrote: Hello, I think I stumbled over the same issue when testing winbind and interdomain trusts on samba 3.6 these days. It is a bit hard to find, but man idmap_ldap says that the secret must be stored with net idmap secret DOMAIN SECRET and I think I used '*' as DOMAIN (for any domain) That made winbind with ldap work for me. Hello. First off, thanks for answering. After my previous message, I had already found out the above and did it. I saw some improvement: _ the logs about winbind not being able to fetch auth credentials are gone; _ smbclient -L ... succeeds, so authentication is in fact working; _ however, access to shares still is denied to users from the trusted domain. It looks like Samba authenticates the user (against the DCs of the trusted domain) and accepts it, but somehow fails to recognize him, so he won't be correctly matched against valid users. Just to be clear: users from the trusted domain can access public shares, as long as they provide a correct password. I'm still investigating this and I'll report anything I'll find. Any further suggestion is still appreciated. bye Thanks av. Hello, does wbinfo -u list the users of the trusted domain? and getent passwd, too? By valid users you mean the parameter in smb.conf? I'm usually using ACLs on shares (in the filesystem), so I haven't tried that. But I suppose it worked before... bye, Oliver -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Trust problems after upgrade from 3.5 to 3.6
On 02/08/13 19:18, Oliver Freyd wrote: Hello, does wbinfo -u list the users of the trusted domain? No; however it doesn't do this with Samba 3.5 either (which works). and getent passwd, too? Same as above. Do you think I've got a config problem which only by chance does not show up with 3.5? By valid users you mean the parameter in smb.conf? Exactly: the one that controls which users can access a share. I'm usually using ACLs on shares (in the filesystem), so I haven't tried that. I'm not using ACL and the share I'm doing my tests with has 777 permissions; so I'm sure it's Samba that denies access. But I suppose it worked before... I can confirm this: it did work as expected with Samba 3.5. Actually it still does in the other server I have in the same site (on which I'm holding the upgrade until I find a solution). bye Thanks av. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
[Samba] BDC Rejecting auth request from client + Windows 7
Just some background: In our environment, we are running both a PDC and BDC. The local network setup has static ips on a different subnet from dhcp ips, thus the PDC has a static ip and the BDC has a dynamic one so the Windows machines are able to see the domain without hardcoding in the ip of the PDC as a wins on each machine. This has worked fine for Windows XP. We are also using ldap as the backend. Now we have a Windows 7 box and I have followed various instructions and modified entries within the registry as everyone else has specified. While I can join the domain, after reboot I get the trust relationship failed error(or on a rare occasion it will say no logon servers available). Checking the logs I have mapped out the following: 1. Win7 client asks to join the domain 2. PDC responds and adds machine to ldap 3. Win7 accepts and tests machine account 4. BDC rejects auth request 5. Win7 logs this, but still shows successful join message and reboots 6. Win7 then refused to login on the domain. I can type in gibberish and still get the trust relationship failed message. Here is the following from the BDC: [2013/02/08 13:11:05.458750, 2] lib/smbldap.c:950(smbldap_open_connection) smbldap_open_connection: connection opened [2013/02/08 13:11:05.504483, 2] ../libcli/auth/credentials.c:307(netlogon_creds _server_check_internal) credentials check failed [2013/02/08 13:11:05.504529, 0] rpc_server/srv_netlog_nt.c:714(_netr_ServerAuth enticate3) _netr_ServerAuthenticate3: netlogon_creds_server_check failed. Rejecting auth request from client CLASSROOM machine account CLASSROOM$ [2013/02/08 13:11:05.524195, 2] ../libcli/auth/credentials.c:307(netlogon_creds _server_check_internal) credentials check failed [2013/02/08 13:11:05.524235, 0] rpc_server/srv_netlog_nt.c:714(_netr_ServerAuth enticate3) _netr_ServerAuthenticate3: netlogon_creds_server_check failed. Rejecting auth request from client CLASSROOM machine account CLASSROOM$ [2013/02/08 13:11:15.914207, 0] lib/util_sock.c:474(read_fd_with_timeout) [2013/02/08 13:11:15.914316, 0] lib/util_sock.c:1441(get_peer_addr_internal) getpeername failed. Error was Transport endpoint is not connected read_fd_with_timeout: client 0.0.0.0 read error = Connection reset by peer. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] samba Digest, Vol 122, Issue 8
Estimados, Estoy fuera de la oficina por vacaciones desde el 11.02.2013 hasta el 1.03.2013, ambas fechas inclusive. Ante cualquier requerimiento favor generar el ticket respectivo o comunicarse con roberto.var...@pyaing.cl , freddy.arev...@pyaing.cl o frederick.esco...@pyaing.cl atte Luis Aravena -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
[Samba] trust relationship whit samba 4.3 ldap backend and Active Directory
Good afternoon, it is possible make a two way trust relationship between samba 4.3 and active directory? best regards Germán Waisvol SR. Linux Unix System administrator -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] BDC Rejecting auth request from client + Windows 7
I don't quite understand- why does the BDC have a dynamic IP address. Or have a I misunderstood? The DHCP server can provide the IP of the WINS servers to DHCP clients.Are the XP and Win 7 workstations on a separate subnet than the servers? What version are the samba servers?Do both samba server point to a single LDAP server or do they each have their own LDAP server in replication?Does pdbedit -Lv show the same accounts on each DC? Is it possible that the Windows 7 machine accounts have not replicated to the BDC? Have to specificied the ports in the smb.conf file- by default samba uses ports 137,138, and 445. In theory you can disable port 445 (it reduces some the transport warnings) but I find that causes problems with name resolution when a router or vpn is involved. So better off just sticking with the defaults. -Original Message- From: samba-boun...@lists.samba.org [mailto:samba-boun...@lists.samba.org] On Behalf Of David Noriega Sent: Friday, February 08, 2013 1:56 PM To: samba@lists.samba.org Subject: [Samba] BDC Rejecting auth request from client + Windows 7 Just some background: In our environment, we are running both a PDC and BDC. The local network setup has static ips on a different subnet from dhcp ips, thus the PDC has a static ip and the BDC has a dynamic one so the Windows machines are able to see the domain without hardcoding in the ip of the PDC as a wins on each machine. This has worked fine for Windows XP. We are also using ldap as the backend. Now we have a Windows 7 box and I have followed various instructions and modified entries within the registry as everyone else has specified. While I can join the domain, after reboot I get the trust relationship failed error(or on a rare occasion it will say no logon servers available). Checking the logs I have mapped out the following: 1. Win7 client asks to join the domain 2. PDC responds and adds machine to ldap 3. Win7 accepts and tests machine account 4. BDC rejects auth request 5. Win7 logs this, but still shows successful join message and reboots 6. Win7 then refused to login on the domain. I can type in gibberish and still get the trust relationship failed message. Here is the following from the BDC: [2013/02/08 13:11:05.458750, 2] lib/smbldap.c:950(smbldap_open_connection) smbldap_open_connection: connection opened [2013/02/08 13:11:05.504483, 2] ../libcli/auth/credentials.c:307(netlogon_creds _server_check_internal) credentials check failed [2013/02/08 13:11:05.504529, 0] rpc_server/srv_netlog_nt.c:714(_netr_ServerAuth enticate3) _netr_ServerAuthenticate3: netlogon_creds_server_check failed. Rejecting auth request from client CLASSROOM machine account CLASSROOM$ [2013/02/08 13:11:05.524195, 2] ../libcli/auth/credentials.c:307(netlogon_creds _server_check_internal) credentials check failed [2013/02/08 13:11:05.524235, 0] rpc_server/srv_netlog_nt.c:714(_netr_ServerAuth enticate3) _netr_ServerAuthenticate3: netlogon_creds_server_check failed. Rejecting auth request from client CLASSROOM machine account CLASSROOM$ [2013/02/08 13:11:15.914207, 0] lib/util_sock.c:474(read_fd_with_timeout) [2013/02/08 13:11:15.914316, 0] lib/util_sock.c:1441(get_peer_addr_internal) getpeername failed. Error was Transport endpoint is not connected read_fd_with_timeout: client 0.0.0.0 read error = Connection reset by peer. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
[Samba] having issues with shares
We recently migrated our install from an ancient fedora 11 install of samba and openldap to a centos 6.3 setup with its openldap and samba. The domain has been totally recreated from scratch as the person that did the previous setup has not been employed here in many years. After fighting with shares for a while we mostly got them fixed and working. However the biggest issue now is when our GIS people try to connect to their samba share. Previously two pople could be editing different feature classes, different files, but now it will not let the second person do anything but view. Here is a brief explanation from our head GIS guy: We currently have 5 data sets in one feature class in the GIS. site_point site_poly survey_point survey_line survey_poly Before the conversion to the new Domain: User A could open up the GIS on computer 1 and begin to edit one of the data set. (site_point for example) and User B could open up the GIS on computer 2 and begin to edit any other data set except what User A was editing (in this example site_point). As long a two people didn't try and edit the same data set it worked. After the Domain conversion: User A opens up the GIS on computer 1 and begins to edit any of our data sets. User B opens up the GIS on computer 2 and attempts to edit any of our data sets a window opens up with several errors about file locks. ( I can send up screen shots in the morning) As we saw in the samba logs it appears that once User A begins editing the one data set all the other data sets in the feature class get .lock files along with the one that User A is actually editing. The only way User B can edit data is if User A exits the GIS completely. So with that we have been trying everything we can think of to get it working correctly again. When I setup the share I copied the existing share from the old domain and put it in the new one making only the domain name change to the section. Here is the old setup: [pictures] comment = Shared Folder for Pictures path = /samba/pictures read only = No create mask = 0667 directory mask = 0770 csc policy = disable nt acl support = no force security mode = 777 valid users = @hpres force group = @ADMIN\hpres #inherit permissions = yes write list = @ADMIN\hpres Here is the new: [hp-pictures] comment = Shared Folder for Historic Preservation Pictures path = /samba/arrowhead/hp-pictures read only = No create mask = 0667 directory mask = 0770 csc policy = disable nt acl support = no force security mode = 777 valid users = @hpres force group = @MDAH\hpres write list = @MDAH\hpres Anyone have an idea why this could be happening? -- Donny B. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
[Samba] work-around on ipv6 samba 4 internal dns
you can disable ipv6 at a machine level echo net.ipv6.conf.all.disable_ipv6=1 /etc/sysctl.d/disableipv6.conf which I did. quote So. Installed my first Samba 4.03 PDC Kept it simple, used samba's internal DNS forwarding to the main DNS server. Edited resolv.conf to query localhost. All was well until I tried to pull down ntp from my debian (6.0) apt source. Suddenly, no can do. all the DNS supplied was in IPV6 which my router doesn't pass. Can I disable ipv6 in the Samba internal DNS server? /quote -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] having issues with shares
I would start by disabling oplocks. - Original Message - From: Donny Brooks dbro...@mdah.state.ms.us To: samba@lists.samba.org Cc: Sent: Friday, 8 February 2013, 12:56 Subject: [Samba] having issues with shares We recently migrated our install from an ancient fedora 11 install of samba and openldap to a centos 6.3 setup with its openldap and samba. The domain has been totally recreated from scratch as the person that did the previous setup has not been employed here in many years. After fighting with shares for a while we mostly got them fixed and working. However the biggest issue now is when our GIS people try to connect to their samba share. Previously two pople could be editing different feature classes, different files, but now it will not let the second person do anything but view. Here is a brief explanation from our head GIS guy: We currently have 5 data sets in one feature class in the GIS. site_point site_poly survey_point survey_line survey_poly Before the conversion to the new Domain: User A could open up the GIS on computer 1 and begin to edit one of the data set. (site_point for example) and User B could open up the GIS on computer 2 and begin to edit any other data set except what User A was editing (in this example site_point). As long a two people didn't try and edit the same data set it worked. After the Domain conversion: User A opens up the GIS on computer 1 and begins to edit any of our data sets. User B opens up the GIS on computer 2 and attempts to edit any of our data sets a window opens up with several errors about file locks. ( I can send up screen shots in the morning) As we saw in the samba logs it appears that once User A begins editing the one data set all the other data sets in the feature class get .lock files along with the one that User A is actually editing. The only way User B can edit data is if User A exits the GIS completely. So with that we have been trying everything we can think of to get it working correctly again. When I setup the share I copied the existing share from the old domain and put it in the new one making only the domain name change to the section. Here is the old setup: [pictures] comment = Shared Folder for Pictures path = /samba/pictures read only = No create mask = 0667 directory mask = 0770 csc policy = disable nt acl support = no force security mode = 777 valid users = @hpres force group = @ADMIN\hpres #inherit permissions = yes write list = @ADMIN\hpres Here is the new: [hp-pictures] comment = Shared Folder for Historic Preservation Pictures path = /samba/arrowhead/hp-pictures read only = No create mask = 0667 directory mask = 0770 csc policy = disable nt acl support = no force security mode = 777 valid users = @hpres force group = @MDAH\hpres write list = @MDAH\hpres Anyone have an idea why this could be happening? -- Donny B. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] having issues with shares
I second disabling oplocks however I would check whether they have had any software updates or anything to change their GIS software as I'm not too sure that an oplock would create a .lock file, and it sounds like it maybe the GIS software doing that. On 8 February 2013 20:56, Donny Brooks dbro...@mdah.state.ms.us wrote: We recently migrated our install from an ancient fedora 11 install of samba and openldap to a centos 6.3 setup with its openldap and samba. The domain has been totally recreated from scratch as the person that did the previous setup has not been employed here in many years. After fighting with shares for a while we mostly got them fixed and working. However the biggest issue now is when our GIS people try to connect to their samba share. Previously two pople could be editing different feature classes, different files, but now it will not let the second person do anything but view. Here is a brief explanation from our head GIS guy: We currently have 5 data sets in one feature class in the GIS. site_point site_poly survey_point survey_line survey_poly Before the conversion to the new Domain: User A could open up the GIS on computer 1 and begin to edit one of the data set. (site_point for example) and User B could open up the GIS on computer 2 and begin to edit any other data set except what User A was editing (in this example site_point). As long a two people didn't try and edit the same data set it worked. After the Domain conversion: User A opens up the GIS on computer 1 and begins to edit any of our data sets. User B opens up the GIS on computer 2 and attempts to edit any of our data sets a window opens up with several errors about file locks. ( I can send up screen shots in the morning) As we saw in the samba logs it appears that once User A begins editing the one data set all the other data sets in the feature class get .lock files along with the one that User A is actually editing. The only way User B can edit data is if User A exits the GIS completely. So with that we have been trying everything we can think of to get it working correctly again. When I setup the share I copied the existing share from the old domain and put it in the new one making only the domain name change to the section. Here is the old setup: [pictures] comment = Shared Folder for Pictures path = /samba/pictures read only = No create mask = 0667 directory mask = 0770 csc policy = disable nt acl support = no force security mode = 777 valid users = @hpres force group = @ADMIN\hpres #inherit permissions = yes write list = @ADMIN\hpres Here is the new: [hp-pictures] comment = Shared Folder for Historic Preservation Pictures path = /samba/arrowhead/hp-pictures read only = No create mask = 0667 directory mask = 0770 csc policy = disable nt acl support = no force security mode = 777 valid users = @hpres force group = @MDAH\hpres write list = @MDAH\hpres Anyone have an idea why this could be happening? -- Donny B. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba Edward Ashley Developer e. n...@redmonkeysoftware.com u. www.redmonkeysoftware.com t. 0845 867 3849 f. 0845 867 4127 Red Monkey Software | Superior Software Solutions Red Monkey Software Ltd, 24 The Layne, Elmer Sands, Bognor Regis, West Sussex. PO22 6JL Registered in England and Wales no 5923420 Registered Office: 20 Springfield Road, Crawley, West Sussex, RH11 8AD -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] having issues with shares
Everything oplocks related has been disabled. Still the same issue. There have been no updates to the software as the GIS guy or I would have had to applied them. Also on the old domain it created the lock files also but it worked. Thanks for the quick replies. On Friday, February 8, 2013 03:17 PM CST, Edward Ashley n...@redmonkeysoftware.com wrote: I second disabling oplocks however I would check whether they have had any software updates or anything to change their GIS software as I'm not too sure that an oplock would create a .lock file, and it sounds like it maybe the GIS software doing that. On 8 February 2013 20:56, Donny Brooks dbro...@mdah.state.ms.us wrote: We recently migrated our install from an ancient fedora 11 install of samba and openldap to a centos 6.3 setup with its openldap and samba. The domain has been totally recreated from scratch as the person that did the previous setup has not been employed here in many years. After fighting with shares for a while we mostly got them fixed and working. However the biggest issue now is when our GIS people try to connect to their samba share. Previously two pople could be editing different feature classes, different files, but now it will not let the second person do anything but view. Here is a brief explanation from our head GIS guy: We currently have 5 data sets in one feature class in the GIS. site_point site_poly survey_point survey_line survey_poly Before the conversion to the new Domain: User A could open up the GIS on computer 1 and begin to edit one of the data set. (site_point for example) and User B could open up the GIS on computer 2 and begin to edit any other data set except what User A was editing (in this example site_point). As long a two people didn't try and edit the same data set it worked. After the Domain conversion: User A opens up the GIS on computer 1 and begins to edit any of our data sets. User B opens up the GIS on computer 2 and attempts to edit any of our data sets a window opens up with several errors about file locks. ( I can send up screen shots in the morning) As we saw in the samba logs it appears that once User A begins editing the one data set all the other data sets in the feature class get .lock files along with the one that User A is actually editing. The only way User B can edit data is if User A exits the GIS completely. So with that we have been trying everything we can think of to get it working correctly again. When I setup the share I copied the existing share from the old domain and put it in the new one making only the domain name change to the section. Here is the old setup: [pictures] comment = Shared Folder for Pictures path = /samba/pictures read only = No create mask = 0667 directory mask = 0770 csc policy = disable nt acl support = no force security mode = 777 valid users = @hpres force group = @ADMIN\hpres #inherit permissions = yes write list = @ADMIN\hpres Here is the new: [hp-pictures] comment = Shared Folder for Historic Preservation Pictures path = /samba/arrowhead/hp-pictures read only = No create mask = 0667 directory mask = 0770 csc policy = disable nt acl support = no force security mode = 777 valid users = @hpres force group = @MDAH\hpres write list = @MDAH\hpres Anyone have an idea why this could be happening? -- Donny B. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba Edward Ashley Developer e. n...@redmonkeysoftware.com u. www.redmonkeysoftware.com t. 0845 867 3849 f. 0845 867 4127 Red Monkey Software | Superior Software Solutions Red Monkey Software Ltd, 24 The Layne, Elmer Sands, Bognor Regis, West Sussex. PO22 6JL Registered in England and Wales no 5923420 Registered Office: 20 Springfield Road, Crawley, West Sussex, RH11 8AD -- Donny B. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] having issues with shares
What does smbstatus give you when you have a user using their GIS software? Any locks? On 8 February 2013 21:40, Donny Brooks dbro...@mdah.state.ms.us wrote: Everything oplocks related has been disabled. Still the same issue. There have been no updates to the software as the GIS guy or I would have had to applied them. Also on the old domain it created the lock files also but it worked. Thanks for the quick replies. On Friday, February 8, 2013 03:17 PM CST, Edward Ashley n...@redmonkeysoftware.com wrote: I second disabling oplocks however I would check whether they have had any software updates or anything to change their GIS software as I'm not too sure that an oplock would create a .lock file, and it sounds like it maybe the GIS software doing that. On 8 February 2013 20:56, Donny Brooks dbro...@mdah.state.ms.us wrote: We recently migrated our install from an ancient fedora 11 install of samba and openldap to a centos 6.3 setup with its openldap and samba. The domain has been totally recreated from scratch as the person that did the previous setup has not been employed here in many years. After fighting with shares for a while we mostly got them fixed and working. However the biggest issue now is when our GIS people try to connect to their samba share. Previously two pople could be editing different feature classes, different files, but now it will not let the second person do anything but view. Here is a brief explanation from our head GIS guy: We currently have 5 data sets in one feature class in the GIS. site_point site_poly survey_point survey_line survey_poly Before the conversion to the new Domain: User A could open up the GIS on computer 1 and begin to edit one of the data set. (site_point for example) and User B could open up the GIS on computer 2 and begin to edit any other data set except what User A was editing (in this example site_point). As long a two people didn't try and edit the same data set it worked. After the Domain conversion: User A opens up the GIS on computer 1 and begins to edit any of our data sets. User B opens up the GIS on computer 2 and attempts to edit any of our data sets a window opens up with several errors about file locks. ( I can send up screen shots in the morning) As we saw in the samba logs it appears that once User A begins editing the one data set all the other data sets in the feature class get .lock files along with the one that User A is actually editing. The only way User B can edit data is if User A exits the GIS completely. So with that we have been trying everything we can think of to get it working correctly again. When I setup the share I copied the existing share from the old domain and put it in the new one making only the domain name change to the section. Here is the old setup: [pictures] comment = Shared Folder for Pictures path = /samba/pictures read only = No create mask = 0667 directory mask = 0770 csc policy = disable nt acl support = no force security mode = 777 valid users = @hpres force group = @ADMIN\hpres #inherit permissions = yes write list = @ADMIN\hpres Here is the new: [hp-pictures] comment = Shared Folder for Historic Preservation Pictures path = /samba/arrowhead/hp-pictures read only = No create mask = 0667 directory mask = 0770 csc policy = disable nt acl support = no force security mode = 777 valid users = @hpres force group = @MDAH\hpres write list = @MDAH\hpres Anyone have an idea why this could be happening? -- Donny B. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba Edward Ashley Developer e. n...@redmonkeysoftware.com u. www.redmonkeysoftware.com t. 0845 867 3849 f. 0845 867 4127 Red Monkey Software | Superior Software Solutions Red Monkey Software Ltd, 24 The Layne, Elmer Sands, Bognor Regis, West Sussex. PO22 6JL Registered in England and Wales no 5923420 Registered Office: 20 Springfield Road, Crawley, West Sussex, RH11 8AD -- Donny B. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba Edward Ashley Developer e. n...@redmonkeysoftware.com u. www.redmonkeysoftware.com t. 0845 867 3849 f. 0845 867 4127 Red Monkey Software | Superior Software Solutions Red Monkey Software Ltd, 24 The Layne, Elmer Sands, Bognor Regis, West Sussex. PO22 6JL Registered in England and Wales no 5923420 Registered Office: 20 Springfield Road, Crawley, West Sussex, RH11 8AD
[Samba] Smaba 4.0.3 replication: Warning: No NC replicated for Connection!
Hi folks, I think I've read every thread on this issue and don't seem to be able to resolve it. It doesn't appear to be affecting anything, however I'm not entirely sure what the implications are either way. What should I do to troubleshoot it? I have BIND9_FLAT updating a BIND server, all of the records appear correct, regular AD objects are replicated fine as well. Any help appreciated. Thanks! samba-tool drs showrepl: Default-First-Site-Name\dc01 DSA Options: 0x0001 DSA object GUID: 79ebd974-91c5-4cd8-a318-9c4c17bc12d3 DSA invocationId: feead75a-ca92-442d-89e7-b0aa8dd63af8 INBOUND NEIGHBORS DC=mdomain,DC=com Default-First-Site-Name\dc02 via RPC DSA object GUID: 9ef06e55-d6db-4128-8c4e-acbecbaa720c Last attempt @ Sat Feb 9 01:04:32 2013 UTC was successful 0 consecutive failure(s). Last success @ Sat Feb 9 01:04:32 2013 UTC CN=Schema,CN=Configuration,DC=mdomain,DC=com Default-First-Site-Name\dc02 via RPC DSA object GUID: 9ef06e55-d6db-4128-8c4e-acbecbaa720c Last attempt @ Sat Feb 9 01:04:32 2013 UTC was successful 0 consecutive failure(s). Last success @ Sat Feb 9 01:04:32 2013 UTC CN=Configuration,DC=mdomain,DC=com Default-First-Site-Name\dc02 via RPC DSA object GUID: 9ef06e55-d6db-4128-8c4e-acbecbaa720c Last attempt @ Sat Feb 9 01:04:32 2013 UTC was successful 0 consecutive failure(s). Last success @ Sat Feb 9 01:04:32 2013 UTC OUTBOUND NEIGHBORS DC=mdomain,DC=com Default-First-Site-Name\dc02 via RPC DSA object GUID: 9ef06e55-d6db-4128-8c4e-acbecbaa720c Last attempt @ NTTIME(0) was successful 0 consecutive failure(s). Last success @ NTTIME(0) CN=Schema,CN=Configuration,DC=mdomain,DC=com Default-First-Site-Name\dc02 via RPC DSA object GUID: 9ef06e55-d6db-4128-8c4e-acbecbaa720c Last attempt @ NTTIME(0) was successful 0 consecutive failure(s). Last success @ NTTIME(0) CN=Configuration,DC=mdomain,DC=com Default-First-Site-Name\dc02 via RPC DSA object GUID: 9ef06e55-d6db-4128-8c4e-acbecbaa720c Last attempt @ NTTIME(0) was successful 0 consecutive failure(s). Last success @ NTTIME(0) KCC CONNECTION OBJECTS Connection -- Connection name: 6fa21055-8daf-4351-80a7-7615f2b8ca96 Enabled: TRUE Server DNS name : dc02.mydomain.com Server DN name : CN=NTDS Settings,CN=dc02,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Conf iguration,DC=mdomain,DC=com TransportType: RPC options: 0x0001 Warning: No NC replicated for Connection! -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Unable to re-connect to roaming profile in samba4
Still can't figure this out.
The client-side logs show two entries:
1. The error in the first message The processing of Group Policy failed.
2. A DNS processing failure:
The system failed to register host (A or ) resource records
(RRs) for network adapter with settings ...
At debug level 5, Samba4 shows no DNS problems, and says Got a dns
update request. All updates allowed. http://pastebin.com/fYrd9F1W
- Nick
On Thu, Feb 7, 2013 at 8:59 PM, Nick Semenkovich seme...@syndetics.net wrote:
I've just configured Samba4 on Ubuntu (4.0.0+dfsg1-1), and can't seem
to get roaming profiles working (I followed the guide at
https://wiki.samba.org/index.php/Samba_AD_DC_HOWTO )
1. Logons work just fine.
2. DNS is configured and working, running through SAMBA_INTERNAL
3. Clients can talk to the server and see/access shares at
\\server.corp.domain.com
4. Clients are all Windows 8 and NTP time synced
5. Permissions seem OK (the profiles directory is currently chmod
777 -- without that, only the Administrator seemed to be able to
create their own profile ...)
6. General users can log in/out (which creates a profile, if profiles
is chmod 777) but a subsequent login can't access it, with a generic
Windows 8 roaming profile error.
Not really sure where to go from here. I've tried:
- Rebuilding the domain re-joining machines
- Ultra-lax permissions
- Adding users via the samba-tool versus AD tools in Windows
At client logon, the samba4 logs (with a debug level of 4) show a collection
of:
Terminating connection - 'NT_STATUS_CONNECTION_DISCONNECTED'
single_terminate: reason[NT_STATUS_CONNECTION_DISCONNECTED]
and a few
Terminating connection - 'kdc_tcp_call_loop:
tstream_read_pdu_blob_recv() - NT_STATUS_CONNECTION_DISCONNECTED'
single_terminate: reason[kdc_tcp_call_loop:
tstream_read_pdu_blob_recv() - NT_STATUS_CONNECTION_DISCONNECTED]
(Not sure if they're related)
Notably, the client machines (all on Win 8) show nearly nothing in the
Event Log, except a Group Policy failure:
The processing of Group Policy failed. Windows attempted to read the
file
\\corp.domain.com\sysvol\corp.domain.com\Policies\{31B2F340-016D-11D2-945F-00C04FB984F9}\gpt.ini
from a domain controller and was not successful. Group Policy settings
may not be applied until this event is resolved. This issue may be
transient and could be caused by one or more of the following:
a) Name Resolution/Network Connectivity to the current domain controller.
b) File Replication Service Latency (a file created on another domain
controller has not replicated to the current domain controller).
c) The Distributed File System (DFS) client has been disabled.
(Manually connecting to that gpi.ini file works perfectly)
Not really sure what's going on here. The only oddities I see are:
* I can't get the old add user script function to work.
As a result, client usernames seem to just have a UID on the linux
side (their profiles show up as: drwxr-xr-x 14 315 users 4.0K Feb
7 20:34 test.V2)
Any way around that?
* When profiles are created, they're appended with .V2 -- Do I need
to add .V2 to the profile path setting, e.g. %USERNAME%.V2? (I can't
imagine that's the case ...)
I've pasted my smb.conf to: http://pastebin.com/DQDkGxsv
Any advice?
Thanks!
Nick
--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/options/samba
autobuild: intermittent test failure detected
The autobuild test system has detected an intermittent failing test in the current master tree. The autobuild log of the failure is available here: http://git.samba.org/autobuild.flakey/2013-02-08-1420/flakey.log The samba3 build logs are available here: http://git.samba.org/autobuild.flakey/2013-02-08-1420/samba3.stderr http://git.samba.org/autobuild.flakey/2013-02-08-1420/samba3.stdout The source4 build logs are available here: http://git.samba.org/autobuild.flakey/2013-02-08-1420/samba.stderr http://git.samba.org/autobuild.flakey/2013-02-08-1420/samba.stdout The top commit at the time of the failure was: commit 554ba5ebbf1d2e520883cfad6f8a2ed6eb9b2b0f Author: Matthieu Patou m...@matws.net Date: Tue Jan 8 00:09:32 2013 -0800 ldb: Add more data test data for one level test cases Reviewed-by: Andrew Bartlett abart...@samba.org Autobuild-User(master): Andrew Bartlett abart...@samba.org Autobuild-Date(master): Fri Feb 8 06:46:40 CET 2013 on sn-devel-104
[SCM] Samba Shared Repository - branch master updated
The branch, master has been updated
via beb6c13 winbind: Fix an incompatible pointer type warning
via c03d5c5 dbwrap: Prevent transactions on non-persistent dbs
via dc2e475 torture: We use transactions for CLEAR_IF_FIRST db
from 554ba5e ldb: Add more data test data for one level test cases
http://gitweb.samba.org/?p=samba.git;a=shortlog;h=master
- Log -
commit beb6c13e9a8c317bca240e875d9e3bcd940a02fb
Author: Volker Lendecke v...@samba.org
Date: Mon Feb 4 15:52:49 2013 +0100
winbind: Fix an incompatible pointer type warning
Signed-off-by: Volker Lendecke v...@samba.org
Reviewed-by: Stefan Metzmacher me...@samba.org
Autobuild-User(master): Stefan Metzmacher me...@samba.org
Autobuild-Date(master): Fri Feb 8 15:27:51 CET 2013 on sn-devel-104
commit c03d5c5740f9d1894a971110029e8f567d300d8a
Author: Volker Lendecke v...@samba.org
Date: Fri Jan 11 15:32:39 2013 +0100
dbwrap: Prevent transactions on non-persistent dbs
dbwrap_ctdb does not allow this anyway. This patch will avoid suprises
when going non-clustered to clustered. Not everybody is developing
against a clustered environment :-)
Signed-off-by: Volker Lendecke v...@samba.org
Reviewed-by: Stefan Metzmacher me...@samba.org
commit dc2e47508d7075cf6507e0dea03da6999ef9097e
Author: Volker Lendecke v...@samba.org
Date: Fri Jan 11 17:29:01 2013 +0100
torture: We use transactions for CLEAR_IF_FIRST db
This does not work in the ctdb case
Signed-off-by: Volker Lendecke v...@samba.org
Reviewed-by: Stefan Metzmacher me...@samba.org
---
Summary of changes:
lib/dbwrap/dbwrap.c |5 +
source3/torture/test_idmap_tdb_common.c |2 +-
source3/winbindd/wb_getgrsid.c |2 +-
3 files changed, 7 insertions(+), 2 deletions(-)
Changeset truncated at 500 lines:
diff --git a/lib/dbwrap/dbwrap.c b/lib/dbwrap/dbwrap.c
index 15eb239..f0b7a9a 100644
--- a/lib/dbwrap/dbwrap.c
+++ b/lib/dbwrap/dbwrap.c
@@ -452,6 +452,11 @@ int dbwrap_get_seqnum(struct db_context *db)
int dbwrap_transaction_start(struct db_context *db)
{
+ if (!db-persistent) {
+ DEBUG(1, (transactions not supported on non-persistent
+ database %s\n, db-name));
+ return -1;
+ }
return db-transaction_start(db);
}
diff --git a/source3/torture/test_idmap_tdb_common.c
b/source3/torture/test_idmap_tdb_common.c
index d081660..5681eef 100644
--- a/source3/torture/test_idmap_tdb_common.c
+++ b/source3/torture/test_idmap_tdb_common.c
@@ -89,7 +89,7 @@ static bool open_db(struct idmap_tdb_common_context *ctx)
return false;
}
- ctx-db = db_open(ctx, db_path, 0, TDB_DEFAULT | TDB_CLEAR_IF_FIRST,
+ ctx-db = db_open(ctx, db_path, 0, TDB_DEFAULT,
O_RDWR | O_CREAT, 0600,
DBWRAP_LOCK_ORDER_1);
diff --git a/source3/winbindd/wb_getgrsid.c b/source3/winbindd/wb_getgrsid.c
index fa376da..f3899b0 100644
--- a/source3/winbindd/wb_getgrsid.c
+++ b/source3/winbindd/wb_getgrsid.c
@@ -143,7 +143,7 @@ static void wb_getgrsid_sid2gid_done(struct tevent_req
*subreq)
* mapped to ID_TYPE_BOTH:
* create a group with the sid/xid as only member
*/
- char *name;
+ const char *name;
if (xid.type != ID_TYPE_BOTH) {
tevent_req_nterror(req, NT_STATUS_NO_SUCH_GROUP);
--
Samba Shared Repository
autobuild: intermittent test failure detected
The autobuild test system has detected an intermittent failing test in the current master tree. The autobuild log of the failure is available here: http://git.samba.org/autobuild.flakey/2013-02-08-1812/flakey.log The samba3 build logs are available here: http://git.samba.org/autobuild.flakey/2013-02-08-1812/samba3.stderr http://git.samba.org/autobuild.flakey/2013-02-08-1812/samba3.stdout The source4 build logs are available here: http://git.samba.org/autobuild.flakey/2013-02-08-1812/samba.stderr http://git.samba.org/autobuild.flakey/2013-02-08-1812/samba.stdout The top commit at the time of the failure was: commit beb6c13e9a8c317bca240e875d9e3bcd940a02fb Author: Volker Lendecke v...@samba.org Date: Mon Feb 4 15:52:49 2013 +0100 winbind: Fix an incompatible pointer type warning Signed-off-by: Volker Lendecke v...@samba.org Reviewed-by: Stefan Metzmacher me...@samba.org Autobuild-User(master): Stefan Metzmacher me...@samba.org Autobuild-Date(master): Fri Feb 8 15:27:51 CET 2013 on sn-devel-104
[SCM] Samba Shared Repository - branch master updated
The branch, master has been updated
via 233b32b s3: Make SMB2_GETINFO multi-volume aware.
from beb6c13 winbind: Fix an incompatible pointer type warning
http://gitweb.samba.org/?p=samba.git;a=shortlog;h=master
- Log -
commit 233b32b771188a6b9ee730a2a202023370e80746
Author: Ira Cooper i...@samba.org
Date: Wed Feb 6 13:35:25 2013 +
s3: Make SMB2_GETINFO multi-volume aware.
Not all shares are a single volume. Some actually
expose multiple volumes under a single share. In these
cases showing the amount of space free as the space free
at the base of the directory heirarchy is wrong.
Reviewed-by: Jeremy Allison j...@samba.org
Autobuild-User(master): Jeremy Allison j...@samba.org
Autobuild-Date(master): Fri Feb 8 21:44:37 CET 2013 on sn-devel-104
---
Summary of changes:
source3/smbd/globals.h |1 +
source3/smbd/smb2_getinfo.c |1 +
source3/smbd/trans2.c | 27 ++-
3 files changed, 20 insertions(+), 9 deletions(-)
Changeset truncated at 500 lines:
diff --git a/source3/smbd/globals.h b/source3/smbd/globals.h
index 4a86697..6ead962 100644
--- a/source3/smbd/globals.h
+++ b/source3/smbd/globals.h
@@ -155,6 +155,7 @@ NTSTATUS smbd_do_qfsinfo(connection_struct *conn,
uint16_t info_level,
uint16_t flags2,
unsigned int max_data_bytes,
+struct smb_filename *smb_fname,
char **ppdata,
int *ret_data_len);
diff --git a/source3/smbd/smb2_getinfo.c b/source3/smbd/smb2_getinfo.c
index 33cee99..5616c84 100644
--- a/source3/smbd/smb2_getinfo.c
+++ b/source3/smbd/smb2_getinfo.c
@@ -413,6 +413,7 @@ static struct tevent_req *smbd_smb2_getinfo_send(TALLOC_CTX
*mem_ctx,
file_info_level,
STR_UNICODE,
in_output_buffer_length,
+fsp-fsp_name,
data,
data_size);
if (!NT_STATUS_IS_OK(status)) {
diff --git a/source3/smbd/trans2.c b/source3/smbd/trans2.c
index 92d047a..8cffc15 100644
--- a/source3/smbd/trans2.c
+++ b/source3/smbd/trans2.c
@@ -3021,6 +3021,7 @@ NTSTATUS smbd_do_qfsinfo(connection_struct *conn,
uint16_t info_level,
uint16_t flags2,
unsigned int max_data_bytes,
+struct smb_filename *fname,
char **ppdata,
int *ret_data_len)
{
@@ -3029,10 +3030,17 @@ NTSTATUS smbd_do_qfsinfo(connection_struct *conn,
const char *vname = volume_label(talloc_tos(), SNUM(conn));
int snum = SNUM(conn);
char *fstype = lp_fstype(talloc_tos(), SNUM(conn));
+ char *filename = NULL;
uint32 additional_flags = 0;
- struct smb_filename smb_fname_dot;
+ struct smb_filename smb_fname;
SMB_STRUCT_STAT st;
+ if (fname == NULL || fname-base_name == NULL) {
+ filename = .;
+ } else {
+ filename = fname-base_name;
+ }
+
if (IS_IPC(conn)) {
if (info_level != SMB_QUERY_CIFS_UNIX_INFO) {
DEBUG(0,(smbd_do_qfsinfo: not an allowed
@@ -3044,15 +3052,15 @@ NTSTATUS smbd_do_qfsinfo(connection_struct *conn,
DEBUG(3,(smbd_do_qfsinfo: level = %d\n, info_level));
- ZERO_STRUCT(smb_fname_dot);
- smb_fname_dot.base_name = discard_const_p(char, .);
+ ZERO_STRUCT(smb_fname);
+ smb_fname.base_name = discard_const_p(char, filename);
- if(SMB_VFS_STAT(conn, smb_fname_dot) != 0) {
+ if(SMB_VFS_STAT(conn, smb_fname) != 0) {
DEBUG(2,(stat of . failed (%s)\n, strerror(errno)));
return map_nt_error_from_unix(errno);
}
- st = smb_fname_dot.st;
+ st = smb_fname.st;
*ppdata = (char *)SMB_REALLOC(
*ppdata, max_data_bytes + DIR_ENTRY_SAFETY_MARGIN);
@@ -3069,7 +3077,7 @@ NTSTATUS smbd_do_qfsinfo(connection_struct *conn,
{
uint64_t
dfree,dsize,bsize,block_size,sectors_per_unit,bytes_per_sector;
data_len = 18;
- if (get_dfree_info(conn,.,False,bsize,dfree,dsize)
== (uint64_t)-1) {
+ if
(get_dfree_info(conn,filename,False,bsize,dfree,dsize) == (uint64_t)-1) {
return map_nt_error_from_unix(errno);
}
@@ -3193,7 +3201,7 @@ cBytesSector=%u, cUnitTotal=%u, cUnitAvail=%d\n,
(unsigned int)st.st_ex_dev, (u
{
uint64_t
Re: [SCM] Samba Shared Repository - branch master updated
On Thu, Feb 07, 2013 at 03:51:05PM +0100, Andreas Schneider wrote: The branch, master has been updated via 62e6ea4 s3-rpc_server: Fix password encoding in _netr_ServerGetTrustInfo(). via 823a25f s3-rpc_server: Dont wipe out ref pointers in _netr_ServerGetTrustInfo(). from ff496ef autoconf: rename pdb_ldap module to pdb_ldapsam commit 62e6ea408a20197420eadb133df6ba233c7874b4 Author: Sumit Bose sb...@redhat.com Date: Mon Feb 4 13:15:18 2013 +0100 s3-rpc_server: Fix password encoding in _netr_ServerGetTrustInfo(). Reviewed-by: Günther Deschner g...@samba.org Reviewed-by: Andreas Schneider a...@samba.org commit 823a25f6a47c311ab33874be8a889ffbaf8db527 Author: Günther Deschner g...@samba.org Date: Tue Dec 11 09:29:37 2012 +0100 s3-rpc_server: Dont wipe out ref pointers in _netr_ServerGetTrustInfo(). Guenther Signed-off-by: Günther Deschner g...@samba.org Reviewed-by: Andreas Schneider a...@samba.org Do we need these in 3.6.x and 4.0.x ? Jeremy.
