AIX 5.3 Active Directory Synchronisation using Winbind

I have been trying to get AIX 5.3 ML-11 integrated with MS AD (MS-2003 with SP2 and SFU 3.5). It has given me a
few y hairs. I have not been able to get it to function correctly.

I have followed various tech articles and installation notes that I have found on the web.  They are all
basically the same in that they suggest to either compile the required components from scratch or to use
the precompiled packages from the pware.hvcc.edu site.

I originally tried compiling from scratch/source which I have always done in the past when using samba as a
NT4 domain member.  This is the first time I have tried integrating into MS AD.

My latest attempt is with using the pre compiled packages from the hvcc site.

I run into the same issues with both types of setup (i.e.: compiling samba from scratch or using the pware53 packages).

When I have samba installed and joined to the AD the following commands work as expected.
wbinfo -u
wbinfo -g
wbinfo -a username

However if I try and telnet to the AIX server or connect to a share the AD is not using for authenticating the
password.   When trying a telnet login I get back “3004-007 You entered an invalid login name or password.”

Following is a list of what I have installed etc.

AIX:  5.3 ML-11-03-1013

  pware53.base.rte           5.3.0.0  COMMITTED  pWare base for 5.3
  pware53.bdb.rte           4.6.21.4  COMMITTED  Berkeley DB 4.6.21
  pware53.cyrus-sasl.rte    2.1.22.2  COMMITTED  cyrus-sasl 2.1.22
  pware53.gettext.rte       0.17.0.0  COMMITTED  GNU gettext 0.17

Re: Performance issues: have eliminated disk and network as cause

Just been told the config file didn't appear in the email as it went out
(even though it certainly appears in the copy I've got), so I'm attaching
inline this time.

Oh, BTW:  it's version 3.4.7 on Debian Lenny, installed from backports.

[global]
        workgroup = U4EATECH
        netbios name = tiamat
        enable privileges = yes
        server string = Primary Domain Controller %v
        security = user
        local master = no
        os level = 33
        domain master = no
        preferred master = no
        encrypt passwords = true
        null passwords = no
        hide unreadable = yes
        hide dot files = yes
        obey pam restrictions = Yes
        unix password sync = Yes
        remote browse sync = 172.30.20.109 172.30.20.130 172.27.0.6
        enhanced browsing = yes
        passwd program = /usr/sbin/smbldap-passwd %u
 passwd chat = "Changing UNIX and samba passwords for*\nNew password*" %n\n
"*Retype new password*" %n\n"
        ldap passwd sync = Yes
        log level = 0
        syslog = 1

Failure to transfer files to Win2008 Server Clusters

Hi, list: 

Our printers are using samba-3.0.37, and we hit a problem recently when doing file transfer to Windows 2008
Server Clusters.

The error occurs when the printer attempts to locate the file path and uses the server IP address rather than
the hostname:
======================================================
18	21.335677	13.121.8.162	13.121.8.3	SMB	Session Setup AndX Request, NTLMSSP_NEGOTIATE
19	21.337175	13.121.8.3	13.121.8.162	SMB	Session Setup AndX Response, NTLMSSP_CHALLENGE, Error: STATUS_MORE_PROCESSING_REQUIRED
20	21.349010	13.121.8.162	13.121.8.3	SMB	Session Setup AndX Request, NTLMSSP_AUTH, User: rasta-man\earl
21	21.354123	13.121.8.3	13.121.8.162	SMB	Session Setup AndX Response
22	21.360548	13.121.8.162	13.121.8.3	SMB	Tree Connect AndX Request, Path: \\13.121.8.3\SCANFOLDER
23	21.361288	13.121.8.3	13.121.8.162	SMB	Tree Connect AndX Response, Error: STATUS_BAD_NETWORK_NAME
======================================================
I believe the problem is related to how Microsoft scopes the file shares when using a cluster
configuration. The transfer is smooth when the destination is a stand-alone Win2008 server. 

Still, from the client side, is there any way to walk around the problem? I mean, since the problem doesn't
occure when the hostname is used to locate the file path, where in the code can I disable the resolving of the
server's hostname to ip address in samba client?

Looking forward to help,
Xu Qiang
--

-- 
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/options/samba

Re: Failure to transfer files to Win2008 Server Clusters

On Thu, Apr 01, 2010 at 04:17:42PM +0800, Xu, Qiang (FXSGSC) wrote:
> Our printers are using samba-3.0.37, and we hit a problem
> recently when doing file transfer to Windows 2008 Server
> Clusters.
> 
> The error occurs when the printer attempts to locate the
> file path and uses the server IP address rather than the
> hostname:
> ======================================================
> 18	21.335677	13.121.8.162	13.121.8.3	SMB	Session Setup AndX Request, NTLMSSP_NEGOTIATE
> 19	21.337175	13.121.8.3	13.121.8.162	SMB	Session Setup AndX Response, NTLMSSP_CHALLENGE,
Error: STATUS_MORE_PROCESSING_REQUIRED
> 20	21.349010	13.121.8.162	13.121.8.3	SMB	Session Setup AndX Request, NTLMSSP_AUTH, User: rasta-man\earl
> 21	21.354123	13.121.8.3	13.121.8.162	SMB	Session Setup AndX Response
> 22	21.360548	13.121.8.162	13.121.8.3	SMB	Tree Connect AndX Request, Path: \\13.121.8.3\SCANFOLDER
> 23	21.361288	13.121.8.3	13.121.8.162	SMB	Tree Connect AndX Response, Error: STATUS_BAD_NETWORK_NAME
> ======================================================

Probably there's not much you can do about this. You
probably have to use the file server name in the
//server/share piece of the smbclient (are you using that?)
command line. What you can do if you have problems with your
name resolution is to use the -I switch to smbclient to give
it the server's ip address.

Volker

--

-- 
To unsubscribe from this list go to the following URL and read the

Re: What are the main differences of the Samba releases?

2010/3/31 John Drescher <drescherjm <at> gmail.com>:
>> today I noticed that red hat el 5.5 includes samba 3.3.x while the
>> former updates of RH EL are based on samba 3.0.x.
>>
>> So my question is, is there some overview of the main differences? I
>> found the Samba Histories at http://samba.org/samba/history, but there
>> may be some chunky list? 
>
> You need 3.3.X or greater to work with windows7, windows2008 and
> possibly vista when samba is a pdc.
>
> If you want more information, check the release notes at the main
> samba page. There is a lot of info there.

There was also a similar question on this list a week or two ago, so
checking the archives might help too.

I believe Karolin answered.

Found it:
http://lists.samba.org/archive/samba/2010-March/154416.html

-- 
Michael Wood <esiotrot <at> gmail.com>
--

-- 
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/options/samba

Samba 3.0.22 - slow performance - Really urgent help

Hi Samba world,

Have been struggling with this for the past 10 days, we are running Samba 
3.0.22 on VCS zone, we have end users saving files
onto Samba mapped drive, and complained that it 5mins to save 300 files, 
now it takes 30 mins.  There is recently a change in the
topology.

Before

        Enduser ----------- samba mapped -------------- server (local 
attached storage)
                                                      physical
                                                      Solaris 8
Now

        Enduser-------------samba mapped ------------  server 
------------------------------ SFCFS/HA
                                                     virtual VCS NFS 
cluster
                                                     Solaris 10 

        We have reverted the NFS from version 4 to 3

        Fine tune Samba, wb and rb are at 64k

        Is there in samba log somewhere to tell me why is the bottleneck ?

        If I move the Samba server which is less loaded in Memory 
consumption , will it help.

Re: help installing samba 3.0.37 on solairs 9 server

On 30 March 2010 23:24,  <Gregory.Jones <at> exeloncorp.com> wrote:
> I am getting these errors running:
> sh makepkg.sh
>
> can anyone help?
>
> ===============================================
> root#  sh makepkg.sh
> Distribution base:  /var/tmp/samba-3.0.37
> Temp install dir:   /tmp/samba-3.0.37-build
> Install directory:  /opt/samba
> mkdir: Failed to make directory "/tmp/samba-3.0.37-build"; File exists

Try: mv /tmp/samba-3.0.37-build{,.old}

before running sh makepkg.sh again.

Not sure if that will fix the other issues, but the first thing it's
complaining about is that it can't create the directory because
there's already a file/directory called that.

> make: Fatal error: Don't know how to make target `install'
> makepkg.sh: bin/smbd: not found
> .
> .
> . (truncated for easy reading)
> cp: cannot access nsswitch/libnss_wins.so
> cp: cannot access nsswitch/libnss_winbind.so
> makepkg.sh: /tmp/samba-3.0.37-build//smbd: not found
> makepkg.sh: man: does not exist

Re: Failed to join domain: failed to precreate account in ou (null): Out of memory

Hi Andrew,

On Wed, Mar 31, 2010 at 09:14:10AM -0400, Andrew Tranquada wrote:
> Anyone else have this problem? We are kind of stuck as 3.4.x seems to hang
> when any of our multiple AD servers are rebooted, and 3.5 seems to not have
> that problem. Right now we are installing 3.4.5 then upgrading to 3.5.1, we
> would much rather install just 3.5.1
> 
> On Fri, Mar 26, 2010 at 1:09 PM, Andrew Tranquada <
> andrew.tranquada <at> gmail.com> wrote:
> 
> >
> >
> > with samba 3.5.1 if I were to join a server to the domain and specify an OU
> > to create the computer object in, i getFailed to join domain: failed to
> > precreate account in ou (null): Out of memory
> >
> >
> > However, if I run the same command with samba 3.4.5 it works.
> >  Did the syntax change? I cannot see anything about it
> >
> > net ads join createcomputer="Linux_Servers" -U <user>%<pass> -n core278468

I think you hit bug https://bugzilla.samba.org/show_bug.cgi?id=7204.
The patch will be included in Samba 3.5.2 (scheduled for April 7).
Maybe you would like to test the patch...

Cheers,
Karolin

Re: Samba 3.0.22 - slow performance - Really urgent help

On Thu, Apr 01, 2010 at 05:24:26PM +0800, Alan Pek wrote:
> Have been struggling with this for the past 10 days, we are running Samba 
> 3.0.22 on VCS zone, we have end users saving files
> onto Samba mapped drive, and complained that it 5mins to save 300 files, 
> now it takes 30 mins.  There is recently a change in the
> topology.
> 
> Before
> 
>         Enduser ----------- samba mapped -------------- server (local 
> attached storage)
>                                                       physical
>                                                       Solaris 8
> Now
>  
>         Enduser-------------samba mapped ------------  server 
> ------------------------------ SFCFS/HA
>                                                      virtual VCS NFS 
> cluster
>                                                      Solaris 10 
>  
> 
>         We have reverted the NFS from version 4 to 3
> 
>         Fine tune Samba, wb and rb are at 64k
> 
>         Is there in samba log somewhere to tell me why is the bottleneck ?
>  
>         If I move the Samba server which is less loaded in Memory 
> consumption , will it help.

Re: Printing Slow-down with Samba 3.5.1

Hu John,

On Wed, Mar 31, 2010 at 02:27:54PM -0400, John Welch wrote:
> We have a Windows 2003 Active Directory environment with a mixture of Windows 2000/2003 and Linux (CentOS
4/5) / Samba servers.  The Samba versions on some of the Linux machines are getting a little old (3.0 and 3.2)
and we are starting to introduce Windows 7 in our environment, so I thought now might be a good time to
upgrade.  On a fully patched CentOS 5 test machine I upgraded to Samba 3.5.1 using the packages from the
sernet repos.  For the most part things seem OK, except that I've noticed a great deal of latency when trying
to print (CUPS) to a printer shared on the test Samba 3.5.1 machine.  Any type of task involving this printer
(viewing properties, selecting the printer, actually printing a document) takes at least a few seconds
longer than it used to.  
> 
> In investigating this problem I didn't really see anything relevant in the Samba logs, but for each
printing task I do I see messages like the following repeated several times in the CUPS logs:
> 
> I [31/Mar/2010:12:38:12 -0400] cupsdCloseClient: SSL shutdown successful!
> 
> I'm guessing this might have something to do with the new Samba "cups encrypt" parameter.  However, the
default is supposed to be "no", so I'm not sure why I'm seeing these "SSL" messages.  I even tried explicitly
setting the parameter to "no" in my smb.conf file, but this had no effect.  All the printing tasks do
eventually work (or at least from what I've found so far), but the extra time involved to complete the tasks
is an annoyance.
> 
> Backing off to 3.4 series (3.4.7) fixes the problem, so it definitely seems to be a 3.5 thing.  I have no
problem upgrading to 3.4.x instead of the 3.5 series, at least for now.  But just wondering if I've maybe
missed a configuration change that needs to be made either to Samba or CUPS to fix this issue.
> 
> Any help would be appreciated.

this might be related to bug https://bugzilla.samba.org/show_bug.cgi?id=6727