similar to: Samba 3.x and PCNetLink domain trusts]

It looks as if 2-way trusts are working between Samba and PCNL and between Samba/NT4. The one exception seems to be logging in as Samba/myname on the ENT4 PDC. I had created a ENT4/myname account. I had forgotten to add SAMBA/myname to the local users group on the ENT4 PDC before trying to the ENT4 PDC as SAMBA/myname. If I log in as SAMBA/anothername it is OK. This isn't real show

I am trying to establish a domain trust between a Samba 3.024 domain and a PC Netlink 2.0 domain. Currently, we are using PC Netlink as our primary Windows file server and "NT4" domain controller. (Lets say that the domain is called LEGACY and the domain controller LX1) Windows 2003 servers are unable to join a PC Netlink domain (even with the SignOrSeal option disabled.) For

I found part of the prob may have been that I didn't join the samba PDC to its own domain. # net join samba -U root Joined domain SAMBA Now, commands like "wbinfo -t" and "wbinfo -m" indicate that the domains are trusted. Also, I can run "net rpc samdump" to dump the NT4 domain info (but not the PCNL domain.) If I try to log in to the NT4 server as a

Thanks for the advice. I had played with NT4 a little bit to see if I could use it for setting up a resource domain for windows 2003 machines- since it looks like you can join Windows 2003 machines to an NT4 domain (so why PCNL can't I don't know), and then establish trusts between NT4 and PCNL. I didn't really want to have NT4 machines in my enviroment any longer than necessary so

Sun PCNetlink is a NT4.0 PDC emulator. I'm running samba-3.0.13, joined to an ADS server that has a trust with a PCNetlink domain. My samba can authenticate fine against ADS accounts, but refuses to authenticate against the PCNetlink domain. I can do getent passwd "ADSDOM\user" and get an ADS user printed out, but if I use getent passwd "NT4DOM\user" nothing

Some additional info: The solaris server is Solaris 10 (sparc.) According to man smb.conf, "enable asu support = yes" creates an IPC only "ADMIN$" share. Using the computer management tool from a Windows machine I could verify this was the case. However, the "ADMIN$" share on the PC Netlink server is actually a data share. I did try "enable asu support =

Some additional info: The solaris server is Solaris 10 (sparc.) According to man smb.conf, "enable asu support = yes" creates an IPC only "ADMIN$" share. Using the computer management tool from a Windows machine I could verify this was the case. However, the "ADMIN$" share on the PC Netlink server is actually a data share. I did try "enable asu support =

I have setup a Samba 3.024 server on Solaris. I have successfully enabled two-way trusts between my samba domain and my legacy PC Netlink domain. (PC Netlink is the solaris port of NT4 aka Advanced Server for Unix.) My Samba domain includes 2 Windows 2003 Servers (One is Windows 2003 SP1, the other is Windows 2003 R2 SP2.) The PCNL server supports Windows 2000 Servers and XP Pro clients.

I now have one PDC (Samba 3.026a on Solaris 10) and several member servers (including Samba 3.026a on Solaris 9 and 10, and Samba 3.024 on Fedora core 6.) Each machine uses NIS for unix accounts. If I start smbd and nmbd on a member server, I can connect to a share from a windows 2000 or XP client. If I look at the permissions on a folder, if shows "Unix Account/someuser" or

I am running samba 3.0.4 using ldap and I am having a wierd problem. I am trying to setup a one way trust with an NT4 PDC. The NT4 PDC is the trusted domain and the samba pdc is the trusting. I setup the password on the nt4 machine in the trusting field. When I go to the samba pdc and type in "net rpc trustdom establish NT4PDC" it prompts for the password. After I type it in it

I have a Sun Clutster running on two Sun Fire 4800s, OS is Solaris 9. The environment was set up with PC Netlink prior to my arrival. On Nov 24 after work I shutdown PC Netlink on both systems and started Samba. However from the windows side we can only see one Sun box and the one sun development box that I tested on prior to this weekend. The other production system can't be seen from

I've been reading some documentation and can't find an answer to my question... I work in an environment where we have a bunch of Solaris 2.8 servers and a bunch of developers using Windows 2000 and XP desktops. We support a client using a Windows 2000 Server ADS PDC, and they need to map some of the NFS drives on our Solaris 2.8 servers. Currently we run a PCNetLink PDC (don't worry

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,

I dowloaded from samba.org samba-3.0alpha24.. I refered http://samba.org/~jht/NT4migration/Samba-HOWTO-Collection.pdf chapter 31 it also mentioned in the how chapter 31 that it is a rough explanation but i decided to follow this and started doing things as i explaned below i looked google and samba mailing lists i did'nt see anything related to my problem anywhere Trying to Migrate from

I would like to move my Samba file server (Samba 4.4.14 on Solaris 11) from a classic domain into an Active Directory domain. The active directory domain has one Win 2008 directory server / domain controller, and one Win 2012 R2 DS. E-mail, among other things, depends on a Microsoft AD backend. A few months ago I was able to join a test server to the AD domain. Today I tried joining a

As per earlier post, I was having problems getting trusts setup between my Samba domain (3.0.x PDC, 3.4.x BDC on Solaris 10) and two Active Directory domains (each in a separate forest.) One domain is a test Win 2003 PDC in native Win 2003 mode, the other is a Win 2008 system also in native Win 2003 mode. To summarize some of the progess- things work better if the Samba 3.4 is the PDC,

Hello I am running a net work with a NT4PDC a NT4 BDC and attent to add samba BDC. I am following the brief section 28 of the Samba-Howto collection for samba head/3.0. * Adding the samba server as a BDC from NT server manager seems OK * Getting, recording domain sid is ok (see below) > rpcclient NT4PDC -U Administrator password: > lsaquery domain IMAGERIE has sid blablabla > net

Hello all, I've got a weird problem with a fresh install of Samba from the FreeBSD ports collection (btw. the BSD-box is also a fresh 4.7 Stable install). Configured Samba 2.2.7a - without cups - with winbind - with winbind-auth - with audit so far, the installation seemed to work fine... Then I copied the libnss_winbind.so to /usr/lib and softlinked it to /usr/local/lib as well as to the

Hi, I am trying a test of migrating a NT4 Domain to Samba 3 Beta 3 configured to use LDAP on Redhat 8. Is this possible? Details ------- I previously had Beta 2 on LDAP running as it's own domain controller without problem and could create users (in LDAP) with smbpasswd -a. XP clients could join and login OK. Now I have flushed that setup and have loaded Beta 3 configured to use LDAP,

I have setup a test PDC with samba 3.4.7 on a fedora core 12 linux machine. I have setup two way interdomain trusts with a Windows 2008 domain. The domain and forest functional levels are Windows 2003. Since the samba machine is not emulating an Active Domain Controller, the Windows 2008 machine should think it is talking to an NT4 server. And since NT4-based domains don't use