similar to: Home directories not mounting under 3.0.2a

Dear Samba Team, I have recently upgraded from Samba 2.2.8a to Samba 3.0.2 where I first noticed the issue. I have also installed 3.0.2a to check if the problem I found may have already been fixed before submitting this issue. Here's the problem: After migrating and switching from passdb backend "smbpasswd" to the new "tdbsam" backend, I started having problems with

This could be quite simple but I don't know how to do it. Does anyone know how I can automatically mount a users home drive (which is located on a windows server) when they log in? Is there a pam module for that? Thanks very much, Sapan

Hi, I know this issue has already been handled several times, but I couldn?t find any clear description of the procedure. I have Samba 2.2.5 running as a PDC on a RedHat 7.3 box, which I?d like to migrate to 3.0.2a now. Both versions are compiled from source using different prefixes (/usr/local/samba and /usr/local/samba3), so I can still use the old version until I get the new one working.

Hello version samba-3.0.2a, OS redhat 9 I configure the samba-server to use pdbedit.... but my stations winXP can't change the passwords, always we receive message error (You not have permission to change password) but all users can change and permission is ok... I read in internet that version of the samba maybe have a problem with passwords on windows Xp, is this true? Anybody can help-me?

Firstly I apologise for the length of this query but I am hoping that if I document everything I did someone might respond / be able to help. My Configuration is Samba 3.0.2a as a PDC on Redhat 8. I cannot for the life of me get the "Domain Admins" functionality to work I am hoping that another set of eyes can shed some light on this problem as I have now spent 41 hrs googling /

Hey guys, Got an interesting problem for you all. I am currently running Samba 3.0212 on a Fedora Core 5 server. I am trying to set up the users' home directories and profile paths. This is how I want it to work. I have a share called "Home" to store all the home directories. So for example the home directory path would be \\server\home\user. I want to set the Profile path to

Hi all, I'm trying to create a domain user in USRMGR.EXE. The samba account will have its property "Password must change" set to 0. this results in the user not being able to access shares if he has been never logged in before. smbclient will return NT_STATUS_PASSWORD_MUST_CHANGE after logon. in USRMGR.EXE, it is impossible to uncheck the checkbox for "password must

Hello all, I progress slowly in my installation of Samba; but I'm confronted to two problems: 1) Is it possible to configure Samba (4.1.7) directly from GNU/Linux (CentOS 6.5) for automatically mount the user's home directory to "H:" when he connects to the domain ? 2) In addition, after that, I'll try to set up profiles' roaming. Here's my files:

Hello all, I progress slowly in my installation of Samba; but I'm confronted to two problems: 1) Is it possible to configure Samba (4.1.7) directly from GNU/Linux (CentOS 6.5) for automatically mount the user's home directory to "H:" when he connects to the domain ? 2) In addition, after that, I'll try to set up profiles' roaming. Here's my files:

I didn't get any answers so I try again: I am using tdbsam as passdb backand. I have added root user with pdbedit. The machine trust account was added on the fly. I have added the user with pdbedit. I have created the user in /etc/passwd. When the user logs in from a W2k and mounts the home-directory I noticed that Samba didn't take the home-directory information from tdbsam, it

Dear All, I run following code to estimate the blocks using cokriging ( my data set has more than 50,000 data points). All the things run finely but Once I run the predict.gstat function it gave the error message - "memory.c", line 58: can't allocate memory in function m_get(). I run this code on LINUX sever but result is same. Would any one please be able to give a solution for

Hello! Here is request to 2.2.8a: [dm@dm-amd64 /]$ nmblookup -R -U 192.168.6.10 center querying center on 192.168.6.10 192.168.22.224 center<00> And here is to 3.0.2a: [dm@dm-amd64 /]$ nmblookup -R -U 192.168.22.220 center querying center on 192.168.22.220 name_query failed to find name center Certanly, all is OK in DNS, I have in smb.conf dns proxy = yes Today I upgraded 2.2.8a

Hi guys/girls, How are you ? I'm looking at migrating my Samba-3.0.1 server which has the standard tdb backend to Samba-3.0.2a with an LDAP backend. I plan to use nss_ldap too. What would be the best way of doing this ? Any assistance would be greatly appreciated. Kindest regards David Wilson D c D a t a Tel +27 33 342 7003 Fax +27 33 345 4155 Cell +27 83 267 7500 http://www.dcdata.co.za

We just migrated a small network from a Win2K PDC to Samba, using "net rpc vampire" into a tdbsam backend on a Samba 3.0.2a Linux box. One of the users, let's call him Jon Harker, had the NT username "JHarker". When we ran "pdbedit -v jharker", we saw this: Unix username: JHarker NT username: JHarker Well, that looks wrong - the NT

Tried to upgrade our Samba 2.2.8a domain controller (Solaris 8) to Samba 3.0.2a. Compiled using gcc 3.3.2, linked to libiconv-1.8, popt-1.7 and cups-1.1.20. I shut down the Samba 2.2.8a. Removed everything in var/locks. Did a "make install" to install 3.0.2a, then restarted Samba. My smb.conf is basically the same as 2.2.8a with "domain admin group" removed. When I stared

Is there a way to differentiate between a SIP address which hasn't registered (but is within sip.conf) and one that's not there at all (i.e. not in sip.conf) using a straight dialplan. I'd like to differentiate actions depending the state of a SIP device and whether it's in my config or not (if that makes sense, basic automap of dial-in lines to sip phones, but if they've

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Flowers, Chocolate, a weekend at the beach, and Samba 3.0.2a. Samba 3.0.2a is a minor patch release for the 3.0.2 code base to address, in particular, a problem when using pdbedit to sanitize (--force-initialized-passwords) Samba's tdbsam backend. This is the latest stable release of Samba. This is the version that all production Samba servers

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Flowers, Chocolate, a weekend at the beach, and Samba 3.0.2a. Samba 3.0.2a is a minor patch release for the 3.0.2 code base to address, in particular, a problem when using pdbedit to sanitize (--force-initialized-passwords) Samba's tdbsam backend. This is the latest stable release of Samba. This is the version that all production Samba servers

Hi Moray, ? Thanks for your answer. It could help but only partially. ? The script name logon%u.cmd was a bad example. Actually, a user can log on from WinXP , or Win 7 workstations, and I'like to run different logon scripts depending on the OS . So having logon script = logon%a.cmd in the smb.conf generally works thanks to variable substitution. ? But for user accounts that have been

Hi folks :-) I've just downloaded Samba 3.0.2a, run ./configure , make and make install. All seemed to go OK but my system still appears to be running the previous 2.2.8a version. New installation seems to have placed smbd, nmbd and swat into /usr/local/samba/sbin (older ver was in /usr/sbin) so I changed the entries in /etc/rc.d/rc.samba to show correct path and now smbd/nmbd are not