similar to: can Same SID but different domain name coexit

Hello, I have two Samba 3.0.22 PDCs and each trust each other. When I add an user of each domain to the permissions of a file on a windows machine (W2k, WXP), it shows for them DOMAIN\USERNAME. Everything is fine. But when i close the permission window and reopen it, then the user out of the trusted domain is only shown as SID. The one of the own domain is resolved fine. This happens on clients

Hi people: I've been using Samba for a long time with some "basic" features like Samba working as a PDC, integrated with OpenLDAP, being a print server, among others, for a small number of "almost controlled" users (no more than 30 or 50 users). But now I'm interested to implement a Windows domain using Samba for a University with 6000-8000 users distributed through

Hi all, We have a small network with WinXP Prof SP2 machines and a Linux (Debian) PDC using Samba 3.0.22. We encountered the following situation: One user was not able to lo into the domain any more some days ago. Using logging on samba side, I found out that samba correctly authenticates the machine and the workstation. Though, XP did not log in, giving a message that the password might not

Hi, Here is my scenario:- 1. I got 1 LDAP server with two domains (A & B) configured to it. 2. Both domain PDCs are fully trusted to one another. I did the "trustdom establish" both ways. 3. I have 1 XP client that has joined Dom A. The login bar can allow you to login to 2 domains. 4. I can managed to login to both domains. 5. I got all the sambaHomePath and home drive

I'm forwarding this to the vorbis list FYI. I'll also forward the reply. Marshall -------- Original Message -------- Subject: Re: File formats (RE: MP4 Player Available for Download) Date: Thu, 15 Mar 2001 10:29:20 -0500 From: Marshall Eubanks <tme@21rst-century.com> Reply-To: tme@21rst-century.com Organization: Multicast Technologies To: philippe.gentric@philips.com CC:

Hi Igor, I am no samba expert. Reading your email produce 2 thots. 1. If I have not read wrongly, you DID NOT managed to reproduce my scenario cos when you joined Domain A , login as user of DomB , you got the expected result, the Domain B's sambahomepath and drive gets map to the user B. Mine result was this: I joined Domain A, login as user of Dom B, I did NOT get Domain B's

Hi list, The task is to move an old samba installation (ubuntu with samba 3.0 brachch) to a new debian installation with samba 3.3.9. Both setups work as pdcs and have an ldap backend which I try to move from one setup to the next. In this new setup I tried to ldapsam:editposix = yes. Therefore I also installed winbind. I moved the domain SID and the local SID to the new pdc and filled the ldap

passdb appears a lot of times in smba logs, even if it uses LDAP as a backend, as in my config. Maybe the log message should be changed in the code for something easier to debug... But this error message you said, only appears if you try to add or delete the user twice from LDAP, so you should remove "-a" from the add user script and comment out the user delete script if you intend to

Dear All I'm having problem with some script which worked a few months ago (on a different computer that might well have had a different version of R installed, so perhaps it has to do with the old version of R?): library(reshape) Loading required package: plyr > tble.data <- melt.array(interp, varnames=c("tme","lon","lat")) > > allyrs.interp <-

When I migrated our Samba PDC from version 2.2.7 to 3.0, I was forced to have the 4 machines we are using rejoin our domain, because the SID had changed. Since then, users have been able to log on, but any attempt to start IE, or Outlook fails, apparently because something in the user's profile cannot be accessed due to the SID modification, and the icons in the WinXP start menu have

Greetings! It is premature for me to send out a "success procedure for migration" yesterday. I overlooked things and I appologize for to this group. Anyway, after migration, computers, users, groups are all created and filled up with the correct membership. However, I still have the same problem with machine password and user password. Further looking into the detail, it looks

Hi all, I got a new assignment today. My task is to install LDAP instead of NIS in our network, consisting of Solaris, Linux and W2k. Our actual setup is like this: Accounts are kept on a Solaris-server and served with samba and NFS. Two PCs serve as PDCs, running NOT samba on unix but a real W2k. Special MS-PAM-modules on the Solaris-server are used to synchronise accounts and passwords with

James: (Again someone correct me if I'm wrong) PAM allows local access to the Samba machine as well as authenticating Samba users. Winbind *only* allows for Samba access. This is why I chose *not* to use PAM in my setup. I don't want normal users to have local logon access to *MY* servers. <evil grin> With Winbind, you don't need PAM at all. If you're planning on

I recall reading that all MPEG AAC software has different and incompatible file formats , because this is a condition set by the MPEG AAC technology licensing authority. Some kind of yet-another-anti-piracy-measure, the idea probably being that users of different software can not swap their files. I picked up this a while ago when following AAC software development, but can't remember exactly

Hi Igor, Once again, thanks for keeping up with me. I have been migrating my master ldap server to 2.1 version so to keep it the same with the PDCs version of LDAP. Now they are the same. I have rectified such that "wbinfo -u" on both sides worked now. I am made "net rpc trustdom list" worked. It was not working before. I had to put "stuadmin = root" in the

The interesting part is that PAM nor the SMB auth plugin for Apache requires you to be a member of the domain. However, the caveat with pam_smb_auth is that you have to have a unix account for every windows user you want to authenticate. I guess the behavior I'm trying to achieve is the one achieved with the Apache plugin: 1) Doesn't require you to be a member of the domain 2)

Hello all, I''ve recently upgraded a Suse 9.1 box to Suse 9.2 (reinstall actually). This is mainly a test server that I use for testing our device with nat/snat etc. I just got around to reinstalling Shorewall 2.2.4, and I''m having an odd problem at startup I was hoping someone could perhaps shed some light on. I''ve created a very basic setup just to get Shorewall

Hi, I'm having some trouble connecting the SMB networks on two LANs that are connected over a "slow" (DSL) link: Network B: 172.16.0.0/24 Domain B: office Network A: 172.16.1.0/24 Domain A: home gate.office and gate.home are the respective networks' NAT gateways connecting to the internet over ADSL lines. The private IP spaces are connected to each other via an ipsec tunnel

Hey all, After setting up a migration server (a server which will act as a test for a Samba 3.x environment), so we can make sure our migration from Samba 2.2.x to 3.x goes as smoothly as possible, I've hit upon a problem, now I am not sure whether this is the fault of Samba (my configuration) or NT4 or whether this is infact designed behaviour for both/either servers. I'd like to

On 10/21/20 5:44 AM, Peter Boos via samba wrote: > So only for old NT4 style PDC - BDC environment one needs poledit. Even if you are running an NT4 domain and manage a recent Windows client to join it, poledit based policies never applied to them, IIRC since Windows Vista (or 7) even that NT4 domains still worked at launch, the policies were ignored. > > While AD's (with