similar to: Help: validating users with pdc

Hello, I want to implement a perl logon script which would map network shares depending on group membership. This way when I move a user to or from a group it automatically gets the new shares. The PDC is Samba 2.2.1 or 2.2.2 on BSD and clients are NT workstation and 2000 Pro. Perl is latest activestate for win32 and is intended to run on Win32 clients. The big trouble is getting user Group

Greeting- I have a mixed network of ms-windows, macintosh and freebsd systems. I am setting up a FreeBSD 9.0 system as a PDC using samba. I can from a FreeBSD box attach to the SMB server as a user that is defined on the Samba Server. [wynkoop at dt0 ~]$ smbclient -L hp1 Enter wynkoop's password: Domain=[HARAPARTNERS] OS=[Unix] Server=[Samba 3.6.4] Sharename Type

Hi everyone, System info: OS: Suse 9.1 samba: 3.0.2a-51 PDC: win2K My winbind was working well with the win2k PDC. I'm using it to control access to my samba shares and subversion repositories. Then they had to change the win2k's hardware. The hostname, domain name, settings, etc. were retained (so they say). And this broke my authentication. I rejoined the domain using net ads

Hi, I've configured samba with ldap support and all is going well with normal users. I wanted to know how to give special right/privileges to users using any windows tool. I tried to use w2k's support tool (Active Directory Users and Computers) and nt's srvtools(usermgr) but none of these worked. win2k says "can not connect to pre-windows 2000 domain" nt connects and

Hi, It seems a common problem that after successfully joining a domain (Samba 2.2.5/6pre PDC), the XP Pro client has a bizarre time trying to logon. The XP clients flatly refuse to even try and talk to the same PDC they just negotiated the domain membership with! I have read many postings (the signorseal registry hack is a must) but no solid answer as to how to get the client and PDC to talk.

Hi all, I'm trying to migrate NT PDC server to Samba PDC. and now i use samba 3.0.0beta2. I looks the migration steps from samba-howto-collection.pdf or in http://us2.samba.org/samba/ftp/cvs_current/docs/htmldocs/nt4migration.html, and it's not works well. The step is : ******** The approximate migration process is described below. " You will have an NT4 PDC that has the users,

Hello guys! I'm newbie in Linux and particularly in SAMBA. You can call me Microsoft centric but am veering away with MS and so my boss who wishes for me to establish a SAMBA PDC Server who will authenticate users, provide file and print services for WInXP and Mac users. I've read a good number of SAMBA-HOW-TOS but unfortunately i'm not going anywhere! thus this e-mail...I'm a

Hi @ll it works (now a small description, please note this was only test setup to bring me nearer to the desired function !!!) i just compiled the new pppd 2.4.3 in my suse 9.2 system. ( i build a suse rpm ) i ve configured a test smb pdc ------------------------------------------------ [global] encrypt passwords = yes unix charset = ISO8859-1 display charset = ISO8859-1

Hello guys! I'm newbie in Linux and particularly in SAMBA. You can call me Microsoft centric but am veering away with MS and so my boss who wishes for me to establish a SAMBA PDC Server who will authenticate users, provide file and print services for WInXP and Mac users. I've read a good number of SAMBA-HOW-TOS but unfortunately i'm not going anywhere! thus this e-mail...I'm a

Thanks Alex, your suggestion along with some additonal tweaks helped solve my problem. The balance has once again been restored in my little universe. >From: samba-request@lists.samba.org >Reply-To: samba@lists.samba.org >To: samba@lists.samba.org >Subject: samba Digest, Vol 27, Issue 39 >Date: Wed, 23 Mar 2005 00:23:28 +0000 (GMT) > >Send samba mailing list submissions to

I found what looks like a pretty good HOWTO type document at IBM on setting up Samba as a PDC. Samba is up and running using this config. The client Win2K Pro machine was in an office environment - but not sure if it was a NT 4.0 domain env or AD env. So I'm trying to put it into the Samba PDC domain which I've got called NONROUTABLE. I've followed the directions for setting up

Hi List, I installed Samba 3.0.0beta3 on RH 8. I'm trying to make a shared directory so I can access from M$ machines using NT users ( from my PDC ). I got to join the Domain and I can see the users from my domain (in the Linux), I can even login as one... I used the RTFM "Samba-HOWTO-Collection" to do this... But I can't open the shared directory, not from any M$ client (or

I have configured winbind on a Linux file server, connecting to a Samba PDC. When I run wbinfo -g, I can see the group "domain users". On the other hand, when I run getent group, I do not see this group. Apart from a few other groups, all groups are visibile in both wbinfo -g and getent group. When running for the first time wbinfo -u, getent passwd and wbinfo -g, I got the results

I've got a problem with roaming profiles. I've googled, trolled the mailing lists, and read the documentation. Problem details I'm running samba 3.0.7 as PDC with WinXP clients. When I log onto WinXP as a domain user the profile is downloaded (you can tell because it takes a while and hub is lit up) but the profile won't load properly. Specifically I notice that the desktop is

Good Morning to all, Sorry if this is spam to some of you, not sure if this is more technical or not... Considering i have been fighting for a week now on this trying all possible checks and configs out there on the net, i thought i better come to the experts. ;o) My last resort is to upgrade to latest samba ver which might help but i think the bug was not fixed in this version not sure.. :o\ I

Hi Samba wizards! Thanks in advance for your support! I am working on migrating an existing Samba 3.x PDC to new hardware, Samba 4.x and, eventually, LDAP. I'm finding out in the process that I don't understand it at all :-) Old configuration was 3.x as PDC, with tdbsam backend. Both NIS and winbind are running on the same server (as well as smb and nmb of course). Since I want the

Hi, we are testing a new AD domain that will replace our old NT4 one, and we are setting up a new cifs vserver of our Netapp filer (running Clustered Dataontap 9.2). The new AD domain was a clean deployment created using "samba-tool domain provision --server-role=dc --use-rfc2307 ...". All seems to work well and the Netapp filer joins the domain without errors and seems to run fine.

Hi all, The new NT migration chapter of Samba guide seems to indicate in the migration Log Validation (section 9.3.1.1) that users get added to all the same groups that they were in under the NT4 domain. However I am not seeing this despite having had a seemingly successful migration. All my users get added into the Domain User group but not into any other group. Is the text below now wrong or

This bounced back from "samba@lists.samba.org", I guess the posting addr is samba@samba.org(?)... Thierry ITTY a ?crit: > maybe > if you access a share on a server as user1 and want to access another share > on the same server as user2, windows complains that you can't use different > credentials at the same time (error 1236 ? I think) --- Yeah, something similar >

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