similar to: Congratulations

Thanks, Unfortunately, I still got the same error. I may be wrong, but it is like it does the automatic lookup process of kdc instead of using the krb5.conf file. However, as per my note below, if I do add bad config info to the krb5.conf, it does complain. David David Shapiro Unix Team Lead 919-765-2011 >>> Dimitri Yioulos <dyioulos@firstbhph.com> 2/1/2006 10:15:49 AM

Folks, Sincere apologies for asking this again, but I'm just not getting this to work, and must be missing something here: My company's network is based around a Windows 2003 server AD, with several RHEL AS 3 boxes connected to it via samba (3.0.21c-1). ?This scheme works very well. ?I've set up, and have successfully been using a sendmail-based email system, too. My issue is

Ok I deleted the incorrect conf file and set it up using Yast again here is the amended file. I tried using the IP address of the server this time but I'm still getting the same errors as before. [libdefaults] default_realm = ELLISONSLEGAL.COM clockskew = 300 [domain_realm] .ELLNET = ELLISONSLEGAL.COM [realms] ELLISONSLEGAL.COM = { kdc = 10.0.0.31 default_domain = ELLNET

Hi, all. I'm working on a project to create a Samba PDC with LDAP authentication. I've been pretty successful in getting everything to work. However, I've run into a small snag: The PDC is built on an OpenSuse 11.2 box. Most of the member servers are also OpenSuse 11.2 boxes. However, a CentOS 5.5 server was just added to the mix. While users can lo into the CentOS box,

Having read a few posts recently I thought I would do some testing. Given XP's use of 445 and that I have a couple of networks where they only have XP clients, I thought I would try setting smb ports to 445 only rather than that suggested of just specifying 139. This has worked well for XP clients with SP2. However SP1, and presumably pre-SP1 clients, lose all sight of the NBT network.

Serious apologies if this has been discussed before, but my search didn't turn up much: I have samba (kept up-to-date with latest) running on several CentOS 3 and 4 boxes as part of a Win2k3 domain. On one particular box, winbind dies on a regular basis (all the other installations run flawlessly). A quick restart, and we're good again. However, as this is a very active server

I am having a hard time getting Samba to authentication correctly against a Windows Active Directory setup. Here is a snap of the smb.conf [global] passdb backend = ldapsam security = domain password server = server1.com server2.com prefered master = No local master = no hide unreadable = yes wins support = no winbind use default

okay, im far from a pam expert, but i don't see any mention of winbind there? It's my weekend at the moment so i can't get to my test box at work to show you my pam module using winbind, but maybe you should check out this page on my website, it's using ldap try and use this and replace any mention of ldap with winbind http://www.yourhowto.org/content/view/35/9/ or i have a

Good morning/evening to all. I hope I'm not taking up space here or wasting people's time but - I've had several samba machines joined to a Win2k3 AD for some time now. Of course, I'm using kerberos, but that's it. I've kinda rolled the bones up 'til now in that I've relied on the PDC without having a BDC. But, if the PDC were to experience any down time

All, Apologies if this is an impertinent question. I've been installing source RPMs from the "Experimental" branch at sernet. That has yet to change to samba-3.2.4. I understand it's a volunteer effort, but I was wondering if any work is being done to create the 3.2.4 source rpm? Dimitri -- This message has been scanned for viruses and dangerous content by MailScanner,

Hi, all. I have several boxes with CentOS versions 3.x, 4.x, and 5.x running in my shop, with Samba loaded on many. I've been able to stay on the current version of Samba in CentOS 4.x and 5.x using the source RPM from Sernet. However, I'm not able to upgrade Samba on the CentOS 3.x boxes. Here's the error I get when I run "rpmbuild --rebuild --clean

Hello to all. I want to use winbind to automatically create email accounts. I've added several linux boxes to our win2k3 AD and working pretty well (more in a new post about this). When I create a new user on the win2k3 box, users can access various shares on the linux boxes, as it should be. I also have a sendmail server sitting in a DMZ. I have to create the email user account on

Hello to all. With recent versions of Samba, it seems that I've built the Samba RPM from source RPM which, in turn. The single RPM that was created installs samba, winbind, smbclient, etc. With version 3.0.25, I can't find that source RPM. All I can find are source RPMs that create individual RPMs for Samba and each of its components. If I try to create the RPM from source

I am trying to connect to an ADS domain and it is failing all the time. I am running SuSE Linux 9.0 with Samba 3.0.13 and have configured Samba with ldap and heimdal kerberos Attached is my debug level 10 error log created when the join is attempted. I would appreciate any advice on solving this problem. Thanks in advance Penny Willisson DISCLAIMER: The information contained within or

Hi wxRuby gurus, I remember a while back, Zach Dennis was working on a mini Spreadsheet app using wxGrid when the issue of lack of wxGrid event handling was discussed. I think Kevin (or Assaph?) had suggested some workarounds until the Swig based version is out. Could not figure out from the archives exactly what the final resolution was, but I am stuck at the same spot and am desperately in need

hi all, yes the good old topic where most people have a problem with :) I have a Windows 2003 Active Directory Server und want that users on this directory are able to login on a Samba Share. The authentication with wbinfo -a user%password works and I already joined the domain with net ads join I am also able to authenticate as directory user with his directory password, BUT only if this

All, Yesterday morning, I updated samba from samba3-3.6.13-45 to samba3-3.6.14-45 (obtained from sernet) on a couple of CentOS 5.9 boxes. As soon as users started access these boxes, one of my sensors detected a winbind error, as in: Apr 30 08:19:36 norwell winbindd[13283]: ? INTERNAL ERROR: Signal 11 in pid 13283 (3.6.14) Here's what appears in syslog: Apr 30 08:19:36 norwell

Just want to offer my congratulations to the JGR developers as the recepient of the 2005 Chambers Award. Great job, guys!! http://stats.math.uni-augsburg.de/JGR/ [Now, could JGR be updated to work with 2.1.0 (or be made R version independent, please... 8-)] Best, Andy

All, I fear I''ve become a pita with this, but windbind periodically dying on one of my machines is really starting to cause grief, and I have no idea what might be causing it, especially as the same config is used on several similar boxes which do not exhibit the problem. While I've posted the problem previously, I thought that maybe this latest log entry after winbind dies

I just wanted to say Congratulations and thank you to the Centos Team for all of the work on Centos 6 - I know the last few months have not been easy - but the real benefit will be that Centos 6 will be as good and as stable as Centos 5 has been for me and everyone who has been using it for the past 4 years. It has never a matter of just getting it done - but getting it done right. Thank You