similar to: 3.0.28a to 3.0.30 issues - pam_winbind_request: write to socket failed

Greetings, I have recently upgraded from 3.0.28a to 3.0.30 on a couple of FreeBSD 7.0 servers: one in a Windows 2000 Active Directory environment, and the other in a Windows 2003 Active Directory environment, as member servers. Everything works for a while and then winbindd goes into sulking mode. Re-starting fixes everythng for a little while. I'm guessing I've hit the winbindd bug

After upgrading to samba-3.0.30 on domain member servers using NT4 as PDC and running winbind users can no longer access the shares, they get prompted for passwords (which shouldn't happen) yet still cannot connect. Dropping back to 3.0.28a works (even after adding the recent security patch) fine. What can I provide to get this fixed? Thank you, -- Chris

Howdy folks, I'm having a weird issue here. I have winbind running on several other servers on our domain, and they are working fine. From what I can tell the configuration is identical, as I custom rolled my own RPM that set's all the config parameters. What's happening is when I try to ssh to this one specific server, it seems looking at the logs it's trying to continuously

Hi, I am trying to connect a FreeBSD server running 7.0 Release and Samba 3.0.28a to a Windows 2003 AD Domain Controller. Has anyone had success with this combo? I have joined the domain and I can enumerate users, groups, etc.. humpty# getent passwd|wc -l 105 humpty# wbinfo -u|wc -l 165 humpty# wbinfo -g|wc -l 59 humpty# wbinfo -t checking the trust secret via RPC calls

Hello, My name is Shane Drinkwater. If I use Samba 3.0.29/3.0.30 I cannot join to= my NT4 Domain. When running the net command to join I get the following er= ror. [root@testbackup bin]# ./net rpc join -Scsqdomainbackup -UAdministrator Password: [2008/06/05 16:40:35, 0] utils/net_rpc_join.c:net_rpc_join_newstyle(371) Error in domain join verification (credential setup failed): NT_STATUS_AC=

I've been running a samba 3.0.28a PDC with XP clients for a while now. The setup has been working flawlessly. I'm considering upgrading some of the clients to Vista. Are there any known issues to Vista using this version of Samba that I should know about. I all need to do is join the Samba domain and connect to a few network shares.

Everyone, We are currently seeing a very strange problem on our server. Everything will be running along smoothly and then all of a sudden, nobody will be able to login. Looking through the logs reveals the following messages... Apr 24 10:55:15 LINUX-1 httpd2-prefork: pam_winbind(httpd): pam_winbind_request: read from socket failed! Apr 24 10:55:15 LINUX-1 httpd2-prefork:

Dear friends, I failed to buld samba 3.0.30 for tru64unix 4.0F. I am curently locked to this os version due to other production software. We currently run Samba 2.2.8a but we were requested to upgrade by our network group. I downloaded 3.3.30 and did $ cd source $ ./configure no warnings or errors as far as I could see, except checking for replacing readdir using getdirentries()...

Greetings once again, I am still having trouble with the "print command" option in 3.0.30. In our computer lab, we force CUPS to print the jobs on hold, using: print command = lp -H hold -d %p %s This worked well with the Slackware packages of Samba 3.0.28 and CUPS 1.1.23. When I upgraded Samba to 3.0.30, the jobs were no longer queued on hold, but printed immediately. To

On Tue, Jun 24, 2008 at 12:08 PM, Aaron Browne <gopodge@gmail.com> wrote: > > Recently built 3.0.30 for testing and cannot establish a Trust Relationship > with our Windows 2003 domain controller. Joining > the domain seems to work but shares are unavailable. Working backwards, I > ended up identifying Samba 3.0.28a > as a working build. Any version after that does not

I'm trying to build and install Samba 3.0.30 on a Solaris 9 SPARC machine. When I do a "make test", the RW1 test is failing. If I go back and configure and build 3.0.28 with the same settings, and do a make test, everything passes. Here's what I'm seeing with 3.0.30: ---8<--- Testing RW1 (0) TEST OUTPUT: host=127.0.0.2 share=tmp user=root myname=cannes Running RW1

Hi. Tonight, I upgraded our Samba print server running Samba 3.0.30 to Samba 3.2.7. This netbios name of this server is 'EUPRYMNA' and the DNS-name 'euprymna.falw.vu.nl'. Since this is a difficult name to remember, we created a DNS-alias 'printserver.falw.vu.nl'. Connecting to printers by calling the server by it's DNS-alias worked in 3.0.30. After the upgrade

Jerry, The patch for 3.0.29 to 3.0.30 is broken; can you fix? James -- Patch Results -- Patch #10 (patch-3.0.29-3.0.30.diffs.gz): + /usr/bin/gzip -d + patch -p1 -s 146 out of 146 hunks FAILED -- saving rejects to file docs/Samba3-ByExample.pdf.rej 8 out of 8 hunks FAILED -- saving rejects to file docs/Samba3-Developers-Guide.pdf.rej 194 out of 194 hunks FAILED -- saving rejects to file

I have successfully joined a domain with Samba 3.0.30 But after approx. one or two hours, winbind looses connection to the domain controller and users are not allowed to connect shares. After a 'killall winbindd' and restarting of winbind, the users can connect to the shares again. How can I work around this bug? Configuration looks like this: [global] dos charset = ISO-8859-1

Hi, I've noticed a discrepancy between Samba Version 3.0.28a and Version 3.0.24 in relation to Winbind rid idmap and trusted domains behaviour. I have an environment with 2 domains linked via a trust, an Active Directory domain and an NT4 domain. On 3.0.24 the rid backend seems to work fine, but on 3.0.28a it shows OTHERDOMAIN\domain admins instead of the primary domain's domain

Hello folks, It seems that I am still having the trust issues I encountered with 3.0.28a with 3.0.30. My production servers are running 3.0.28 and that is working very well. Thanks in advance for any help or advice. - Franz Basic setup: Win NT4 PDC domain trusts an AD-mixed mode accounts domain Samba server member of NT4 domain and running winbind for auth When I call id <username> I

Listmates, I have a perplexing problem. I brought an old Toshiba laptop back from the lakehouse to update it, etc. I also brought the server back to. On out local network, I can see all the boxes in the network from the laptop (hostname: dcrlaptop), but I can only connect to it's normal server (hostname: lakehouse). dcrlaptop is running Win98 and the host I am trying to connect to is

An XP client is having an issue with my 3.0.28a server. They do not have this problem on a native w2003 file server with the same amount of data. [2008/08/20 13:25:14, 5] smbd/dir.c:OpenDir(1079) OpenDir: Can't open DowningShotgun/DowningTest/DowningTest.files/sample. Too many open files [2008/08/20 13:25:14, 3] smbd/filename.c:scan_directory(586) scan dir didn't open dir

greetings folks, i just upgraded to 3.0.28a on a secondary server (not live) and am now unable to connect to my trusted domain. here's the setup: NT4 PDC/BDC for my domain my domain trusts a central domain for the accounts the central domain is running AD in mixed mode my samba servers are members of my domain and use winbind after getting my daemons running, i check with winbind. -

Hi i compiled Samba 3.0.28a under Solaris 8 (sparc). Everything seems to be fine except the libnss_winbind.so. i copied it to /usr/lib and linked it to: libnss_winbind.so.1 libnss_winbind.so.2 nss_winbind.so.1 nss_winbind.so.1 now when i use: id user nothing happens. group user is the same wbinfo -t / -g / -u all work fine. So it must be something with the nss I guess?