Re: [Samba] ADUC tool cannot creates users home directory
On Mar 27, 2013 8:08 PM, ?icro MEGAS microme...@mail333.com wrote: My smb.conf contains: [global] template homedir = /data1/homes/%ACCOUNTNAME [homes] browseable = no read only = no Remove template homedir from global and add following to your homes section: path = /data1/homes And while defining home directory for users in dsa.msc give following path: \\SRV4\homes\%USERAME% And it should work fine. Regards, Nishant -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] ADUC tool cannot creates users home directory
Well, In that case you could choose to hide the homes share by naming it homes$ and assigning a network drive say H: to users as their home drive. This is the way I have implemented it, may be there is some oversight from my side, but it works for me. And directories are created automagically by the windows tool. Regards, Nishant On Mar 27, 2013 8:41 PM, ?icro MEGAS microme...@mail333.com wrote: Hello Nishant, thanks for your feedback. Well, of course your proposed configuration would work, but have a caveats in my eyes: - a user accessing the share \\s4srv\homes would see all other users home directories. Although he cannot enter/access them, I don't like this behavior. - you would have two shares shown, one is \\s4srv\homes and the other cloned one (because of the homes special share) \\s4srv\johndoe. That's annoying, too. If I would use browseable = no at the [homes] section, than only the share \\s4srv\johndoe would be visible and when you open this share, you see again all other users home directories (which is not wanted at all). I would really appreciate to use the special share [homes] as it is intended to be used (as described in the manual of smb.conf). But I cannot find another option to have ADUC tool use somehow this syntax form of this special share which will clone [homes]--[username]. As I think exactly that is the problem, that's why ADUC cannot access this share to create a subdir there. Of course there would be an option to use logon scripts to create a non-existing home dir on-the-fly after the user logs in. I just wanted to ask here on the community, if I miss something and maybe there's a workaround to use [homes] as described initially on my post here *AND* to have ADUC tool creates a homedir for a user. However, thanks for your feedback. Cheers, Lucas. Срд 27 Мар 2013 18:50:02 +0400, Nishant Sharma codemarau...@gmail.com написал: On Mar 27, 2013 8:08 PM, ?icro MEGAS microme...@mail333.comhttp://compose/?adb_to=microme...@mail333.com wrote: My smb.conf contains: [global] template homedir = /data1/homes/%ACCOUNTNAME [homes] browseable = no read onlyXSSCleaned= no Remove template homedir from global and add following to your homes section: path = /data1/homes And while defining home directory for users in dsa.msc give following path: \\SRV4\homes\%USERAME% And it should work fine. Regards, Nishant -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Printer drivers
On Mar 23, 2013 11:37 PM, Fabian von Romberg fromberg...@hotmail.com wrote: Hi, is this a bug in Samba 4? I am also facing the same problem on samba 4.0.4. It was working fine on 4.0.1 and when moving to production, I decided to go with the latest version. Somehow, driver got uploaded on to the server, but clients are not able to find/install driver automatically. They get the driver installation wizard popped up and 'have disk' is required. I am running Samba 4.0.4 on AMD64 Debian Squeeze. Test system was running on i386 Debian and Samba 4.0.1. Regards, Nishant -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
[Samba] Strange corruption problem of Win7
Hello, I am running Samba 4.0.1 as AD DC. I have configured GPOs for redirecting folders (Application Data, Documents etc.). Yesterday, there was a strange problem. The network switch suddenly went kaput and all machines lost connection to the DC. Users logged off and when they are trying to start machine today, Windows 7 can not start. Few of the machines had restore points for day before yesterday and they could be restored. All others are in the need of re-installation. Has anyone faced such kind of problem earlier? Could it be related to redirecting the AppData(Roaming) folder? Let me know if more information is required. Thanks regards, Nishant -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Strange corruption problem with Win7
Hello All, On Thursday 31 January 2013 01:06 PM, Nishant Sharma wrote: I am running Samba 4.0.1 as AD DC. I have configured GPOs for redirecting folders (Application Data, Documents etc.). Yesterday, there was a strange problem. The network switch suddenly went kaput and all machines lost connection to the DC. Users logged off and when they are trying to start machine today, Windows 7 can not start. Few of the machines had restore points for day before yesterday and they could be restored. All others are in the need of re-installation. Here is an update. Freshly re-formatted machine with Win7 installed was joined domain and it again got corrupted. 2 of the machines which were running fine till yesterday after restoration have refused to start this morning. Although my suspicion is on AppData folder, I can not logically agree to it that user's profile data can cause this kind of an issue. Any guidance on this please. Thanks regards, Nishant -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
[Samba] Strange corruption problem with Win7
Hello, I am running Samba 4.0.1 as AD DC. I have configured GPOs for redirecting folders (Application Data, Documents etc.). Yesterday, there was a strange problem. The network switch suddenly went kaput and all machines lost connection to the DC. Users logged off and when they are trying to start machine today, Windows 7 can not start. Few of the machines had restore points for day before yesterday and they could be restored. All others are in the need of re-installation. Has anyone faced such kind of problem earlier? Could it be related to redirecting the AppData(Roaming) folder? Let me know if more information is required. Thanks regards, Nishant -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Samba4 AD Groups Problem
Hi Lukas, On Monday 14 January 2013 07:48 PM, Lukas Gradl wrote: there without any problem. But setting read only = yes and write list = @TEST\Domain Admins doesn't work - I get access denied on the windows host, despite I'm logged on as TEST\Administrator [testshare] Comment = Test share path = /space/testshare read only = Yes write list = @TEST\Domain Admins Change it to: write list = @Domain Admins,TEST\Administrators,administrator and try again. regards, Nishant -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Samba4 AD Groups Problem
Sorry for the top post, my mobile is old world's! What about public = yes guest = yes browseable = yes -Nishant On 1/14/13, Lukas Gradl samba@ssn.at wrote: Zitat von Nishant Sharma codemarau...@gmail.com: Hi Lukas, On Monday 14 January 2013 07:48 PM, Lukas Gradl wrote: there without any problem. But setting read only = yes and write list = @TEST\Domain Admins doesn't work - I get access denied on the windows host, despite I'm logged on as TEST\Administrator [testshare] Comment = Test share path = /space/testshare read only = Yes write list = @TEST\Domain Admins Change it to: write list = @Domain Admins,TEST\Administrators,administrator OK, little correction: I tried: write list = @Domain Admins,@TEST\Administrators (notice the additional @ before TEST\Administrators) This worked for users in the Administrators group. Added adminstrator then the administrator User itself can access the share. But @TEST\Domain Admins doesn't work... Additionaly I discovered that the Point and Print share works for the Administrator allone. Another User out of the Domain Admins Group is not allowed to add a printer driver. regards Lukas -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba -- Sent from my mobile device -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
[Samba] smb_panic with 4.0.0rc2 on Debian Squeeze
Hi, I have successfully compiled and installed Samba 4.0.0rc2 on Debian Squeeze as described in the Wiki. In order to support Win XP and Win 7 clients, I have created GPOs for folders redirection. The problem I am facing is with random PANIC messages in the logs and logon/logoff/file access process gets hung on the client. Here are the logs: Oct 18 13:42:32 pdc smbd[27384]: [2012/10/18 13:42:32.418846, 0] ../source3/smbd/open.c:1463(defer_open) Oct 18 13:42:32 pdc smbd[27384]: Trying to defer an already deferred request: mid=4, exiting Oct 18 13:42:32 pdc smbd[27384]: [2012/10/18 13:42:32.419608, 0] ../source3/smbd/oplock.c:115(release_file_oplock) Oct 18 13:42:32 pdc smbd[27384]: PANIC: assert failed at ../source3/smbd/oplock.c(115): sconn-oplocks.exclusive_open=0 Oct 18 13:42:32 pdc smbd[27384]: [2012/10/18 13:42:32.419714, 0] ../source3/lib/util.c:810(smb_panic_s3) Oct 18 13:42:32 pdc smbd[27384]: PANIC (pid 27384): assert failed: sconn-oplocks.exclusive_open=0 Oct 18 13:42:32 pdc smbd[27384]: [2012/10/18 13:42:32.421355, 0] ../source3/lib/util.c:921(log_stack_trace) Oct 18 13:42:32 pdc smbd[27384]: BACKTRACE: 46 stack frames: Oct 18 13:42:32 pdc smbd[27384]:#0 /usr/local/samba/lib/libsmbconf.so.0(log_stack_trace+0x2b) [0xb717b708] Oct 18 13:42:32 pdc smbd[27384]:#1 /usr/local/samba/lib/libsmbconf.so.0(smb_panic_s3+0x7f) [0xb717b566] Oct 18 13:42:32 pdc smbd[27384]:#2 /usr/local/samba/lib/libsamba-util.so.0(smb_panic+0x2a) [0xb76ffb1c] Oct 18 13:42:32 pdc smbd[27384]:#3 /usr/local/samba/lib/private/libsmbd_base.so(release_file_oplock+0x122) [0xb752fb4d] Oct 18 13:42:32 pdc smbd[27384]:#4 /usr/local/samba/lib/private/libsmbd_base.so(+0x10edd8) [0xb74cbdd8] Oct 18 13:42:32 pdc smbd[27384]:#5 /usr/local/samba/lib/private/libsmbd_base.so(close_file+0xa6) [0xb74cd3b3] Oct 18 13:42:32 pdc smbd[27384]:#6 /usr/local/samba/lib/private/libsmbd_base.so(file_close_conn+0x83) [0xb745c68a] Oct 18 13:42:32 pdc smbd[27384]:#7 /usr/local/samba/lib/private/libsmbd_base.so(close_cnum+0x2b) [0xb74f1249] Oct 18 13:42:32 pdc smbd[27384]:#8 /usr/local/samba/lib/private/libsmbd_base.so(smbXsrv_tcon_disconnect+0x573) [0xb75273e9] Oct 18 13:42:32 pdc smbd[27384]:#9 /usr/local/samba/lib/private/libsmbd_base.so(+0x16a6c2) [0xb75276c2] Oct 18 13:42:32 pdc smbd[27384]:#10 /usr/local/samba/lib/private/libdbwrap.so(+0x4efa) [0xb69bbefa] Oct 18 13:42:32 pdc smbd[27384]:#11 /usr/local/samba/lib/private/libdbwrap.so(+0x4fc9) [0xb69bbfc9] Oct 18 13:42:32 pdc smbd[27384]:#12 /usr/local/samba/lib/private/libdbwrap.so(dbwrap_traverse+0x26) [0xb69ba060] Oct 18 13:42:32 pdc smbd[27384]:#13 /usr/local/samba/lib/private/libsmbd_base.so(+0x16a494) [0xb7527494] Oct 18 13:42:32 pdc smbd[27384]:#14 /usr/local/samba/lib/private/libsmbd_base.so(smb2srv_tcon_disconnect_all+0x56) [0xb7527a18] Oct 18 13:42:32 pdc smbd[27384]:#15 /usr/local/samba/lib/private/libsmbd_base.so(smbXsrv_session_logoff+0x4a0) [0xb7524bba] Oct 18 13:42:32 pdc smbd[27384]:#16 /usr/local/samba/lib/private/libsmbd_base.so(+0x167f3f) [0xb7524f3f] Oct 18 13:42:32 pdc smbd[27384]:#17 /usr/local/samba/lib/private/libdbwrap.so(+0x4efa) [0xb69bbefa] Oct 18 13:42:32 pdc smbd[27384]:#18 /usr/local/samba/lib/private/libdbwrap.so(+0x4fc9) [0xb69bbfc9] Oct 18 13:42:32 pdc smbd[27384]:#19 /usr/local/samba/lib/private/libdbwrap.so(dbwrap_traverse+0x26) [0xb69ba060] Oct 18 13:42:32 pdc smbd[27384]:#20 /usr/local/samba/lib/private/libsmbd_base.so(smbXsrv_session_logoff_all+0xd1) [0xb7524d5d] Oct 18 13:42:32 pdc smbd[27384]:#21 /usr/local/samba/lib/private/libsmbd_base.so(+0x16dbe7) [0xb752abe7] Oct 18 13:42:32 pdc smbd[27384]:#22 /usr/local/samba/lib/private/libsmbd_base.so(exit_server_cleanly+0) [0xb752b049] Oct 18 13:42:32 pdc smbd[27384]:#23 /usr/local/samba/lib/private/libsmbd_base.so(+0x1065e3) [0xb74c35e3] Oct 18 13:42:32 pdc smbd[27384]:#24 /usr/local/samba/lib/private/libsmbd_base.so(+0x106d5e) [0xb74c3d5e] Oct 18 13:42:32 pdc smbd[27384]:#25 /usr/local/samba/lib/private/libsmbd_base.so(+0x1081de) [0xb74c51de] Oct 18 13:42:32 pdc smbd[27384]:#26 /usr/local/samba/lib/private/libsmbd_base.so(+0x10c0c0) [0xb74c90c0] Oct 18 13:42:32 pdc smbd[27384]:#27 /usr/local/samba/lib/private/libsmbd_base.so(create_file_default+0x335) [0xb74c9c78] Oct 18 13:42:32 pdc smbd[27384]:#28 /usr/local/samba/lib/private/libsmbd_base.so(+0x21e659) [0xb75db659] Oct 18 13:42:32 pdc smbd[27384]:#29 /usr/local/samba/lib/private/libsmbd_base.so(smb_vfs_call_create_file+0xbb) [0xb74d51eb] Oct 18 13:42:32 pdc smbd[27384]:#30 /usr/local/samba/lib/private/libsmbd_base.so(+0x154418) [0xb7511418] Oct 18 13:42:32 pdc smbd[27384]:#31 /usr/local/samba/lib/private/libsmbd_base.so(smbd_smb2_request_process_create+0x590) [0xb750f1ce] Oct 18 13:42:32 pdc smbd[27384]:#32 /usr/local/samba/lib/private/libsmbd_base.so(smbd_smb2_request_dispatch+0xd12) [0xb75081a0] Oct 18 13:42:32 pdc
[Samba] Printing problem with CUPS / Samba
Hello everyone! We're using samba-3.0.2rc2 with OpenLDAP-2.1.27, cupsys-1.1.20final-cvs200403 and a Samsung printer. Printing was working fine but yesterday all of a sudden it stopped working. The error message on the windows machine was: A StartDocPrinter call was not issued. On viewing samba logs for the machine, we got following error: tdb(/var/lib/samba/printing/Samsung.tdb): rec_free_read bad magic 0x42424242 at offset=63736 tdb(/var/lib/samba/printing/Samsung.tdb): rec_read bad magic 0xd9fee666 at offset=58844 tdb(/var/lib/samba/printing/Samsung.tdb): rec_read bad magic 0xd9fee666 at offset=58844 tdb(/var/lib/samba/printing/Samsung.tdb): rec_free_read bad magic 0x42424242 at offset=63736 We had a thought that Samsung.tdb file might have got corrupted, so we removed it and restarted smbd. The file was recreated and printing started fine. Could anyone please point out what was the main problem? We just did a trial and error process and got through. Any sort of help is welcome. Thanks in advance. regards, Nishant -- Nishant Sharma [EMAIL PROTECTED] Support - Enterprise Server Systems DeepRoot Linux, Bangalore India. Ph: +91-80-28565624 -- Why did the Roman Empire collapse? What is the Latin for office automation? -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] ldap replication
On Tue, 2004-05-11 at 15:58, Stefan Kania wrote: But now my problem started. It is no longer possible to log in to the system :-(. With login over ssh i got the message permission denied What are the entries in following files: nsswitch.conf ldap.conf libnssldap.conf libpamldap.conf when i login as root everything works, then i try su my-name i got the message no such user my-name. Also an ldapsearch -x -h localhost (cn=my-name) woun't bring up any results. This is because root exists in /etc/passwd file but my-name is in LDAP database. You need to add following line in your slapd.conf in permission section to be able to search anonymously: access to * by * read Also are you able to get the full user list by issuing this: # getent passwd regards, Nishant -- Nishant Sharma [EMAIL PROTECTED] Support - Enterprise Server Systems DeepRoot Linux, Bangalore India. Ph: +91-80-28565624 -- === ALL CSH USERS PLEASE NOTE Set the variable $LOSERS to all the people that you think are losers. This will cause all said losers to have the variable $PEOPLE-WHO-THINK-I-AM-A-LOSER updated in their .login file. Should you attempt to execute a job on a machine with poor response time and a machine on your local net is currently populated by losers, that machine will be freed up for your job through a cold boot process. -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Strange behaviour of samba-3.0.2rc2
Andrew Bartlett wrote: On Tue, 2004-02-10 at 02:42, Nishant Sharma wrote: On comparing the LDAP attributes of the users whose passwd I had reset and of those I didn't, I observed that when the value of the following three attributes are set to '0'(zero) for a user, he was not able to login: sambaPwdLastSet sambaPwdCanChange sambaPwdMustChange In Samba-3.0.0-2, if these values were set to 0, the user was prompted to change his password at the time of first logon saying that his password has expired. But with Samba-3.0.2rc2, login was not possible. Only on removing these three attributes or resetting their values, which is done by 'smbpasswd', logins were possible. Quite correct. If the password was last set in 1970, then we consider that it might be a bogus password (see the security annoucement about mksmbpasswd.sh for 3.0.2). Either do not set that attribute, or set it to a valid value. (The other values are unaffected). Hmm.. that means I've to set it right at the time off adding users :). Thanks a lot. But if i wish to force the users to change the password as soon as they login for first time, is there any way round for this? regards, Nishant -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Strange behaviour of samba-3.0.2rc2
Hi! I had installed samba-3.0.0-2 with openldap-2.1.25 on debian testing with kernel 2.4.23. All the Windows 98, ME, XP, NT, 2000 were able to join the domain as I was able to set the same SID as the previous version of Samba that was installed earlier. The only problem that arised was the Win-98, ME User list problem that was posted on this list at http://lists.samba.org/archive/samba/2003-December/076483.html So, I decided to upgrade the samba version. Now, I've Samba-3.0.2rc2 on the same machine acting as domain controller. Users were not able to login to the domain after the upgrade. The error being NT_STATUS_WRONG_PASSWORD. But when I reset the password using 'smbpasswd' command, they could. On comparing the LDAP attributes of the users whose passwd I had reset and of those I didn't, I observed that when the value of the following three attributes are set to '0'(zero) for a user, he was not able to login: sambaPwdLastSet sambaPwdCanChange sambaPwdMustChange In Samba-3.0.0-2, if these values were set to 0, the user was prompted to change his password at the time of first logon saying that his password has expired. But with Samba-3.0.2rc2, login was not possible. Only on removing these three attributes or resetting their values, which is done by 'smbpasswd', logins were possible. It would be helpful if someone could enlighten me on this issue. Thanks in advance. regards, Nishant -- Nishant Sharma, DeepRoot Linux, Bangalore, India +91(80)28565624, http://www.deeproot.co.in Server Appliances. Solutions. Migration. Community Projects. Getting Linux to work for you. Faster. Better. Today. Everyway -- The intensity of your desires determines the intensity of your success! -Anonymous -- -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
