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

Except that everything isn't fine, because I can't login to the samba domain as a PCNL/NT4 user or vice versa. -------- Forwarded Message -------- > From: Volker Lendecke <Volker.Lendecke@SerNet.DE> > Reply-To: Volker.Lendecke@SerNet.DE > To: Damian Lock (SSCI) <Damian.Lock@ssci.com> > Cc: samba@lists.samba.org > Subject: Re: [Samba] Samba 3.x and PCNetLink

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

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

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

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'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

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 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 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

On my test Samba PDC, I updated the krb5.conf file to add realm info for the Windows 2008. This seems to have resolved my "wbinfo" issue. "getent passwd" is still not working (I did update nsswitch.conf) but I suspect this is because of an idmap allocation issue. The syntax for idmap allocation in smb.conf seems to change between 3.0, 3.2, 3.3 and 3.4. I have also tried

I am having trouble upgrading my installation of Samba. My setup is: - Debian Woody x86 - Samba 3.0.0rc2 (upgrading from alpha22) - Samba acting as a PDC - Samba accounts and Posix accounts in an LDAP directory (OpenLDAP from Debian) I have successfully compiled and installed the new version. I have extracted all users from the LDAP tree and converted them to the new schema using the perl

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

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,

Is there any way to samdump a local SAM file using the net samdump tool? I have found other utilities for this purpose, but nothing yet that compiles on FreeBSD.

Hello! I've run into a strange problem with samba-2.2.7a. I compiled it with --with-ldapsam on a Debian/Woody box, set up openLDAP 2.0.23 with all users and machine trust accounts and configured samba to using LDAP and being a PDC. Works ok so far, users may authenticate and use their shares. But they can not *always* log into the domain from NT4.0 workstations. Sometimes yes, sometimes

I just did a clean install of Fedora 9 onto a Pentium 4 machine. It is actually running SELinux enforcing, but I haven't found any errors related to that so far. It is running Samba 3.2.3-0.20. I am trying to migrate a Windows NT 4.0 domain with about 30 users and 30 computers onto a pure Samba setup, using Samba as the PDC and tdbsam. I have read the HOWTO guide extensively, and

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

I'm trying to call from XLite phone to PSTN (I've tried this from internet and from local network the same) The Xlite doesn't write that it is connected but receives excelent audio. At the other end comes only noise. Some times only for a second you can here the caller voice , but this was only one time :) I saw with ethereal that UDP packets are coming and going to the asterisk