similar to: Intermittent process crash serving files

First... Hi. Im new in the list and I want to say Hello Second. Apologies because my english writing is too bad. I haven't problem to read. But the verbs and syntaxis when I write is too bad. I will try to read the list without write. I write now because I have a big problem. In this right moment Im downloading the entire archive lists and I will try to ask less. I have a samba server and the

hello, samba. i have running samba 2.2.8a from the ports on the system: FreeBSD bingo.ru 4.7-STABLE FreeBSD 4.7-STABLE #2: Tue Mar 25 20:30:51 YEKT 2003 root@bingo.ru:/usr/obj/usr/src/sys/bingo i386 with config: === cut === [global] workgroup = bingo netbios name = emily server string = bingo samba daemon hosts allow = 192.168.2. 127. hosts deny = 192.168.1. interfaces = xl2 bind

Hey, i build my first Linux Server in Oktober 2001. Everything works fine. At the end of Februar 2002 i got a problem. Please see the logfile. [2002/02/25 09:02:15, 0] smbd/password.c:domain_client_validate(1563) domain_client_validate: could not fetch trust account password for domain NENN [2002/02/25 09:02:47, 0] smbd/oplock.c:request_oplock_break(997) request_oplock_break: no response

Trying to upgrade from 2.2.3a to 2.2.4 broke our Solaris 8 PDC. We see the following issues: - Compile flag -KPIC is not valid for gcc, does not seem to bread build - Now looks like directory /usr/spool/samba is needed, but not created by install - smbclient -L hemlock fails with login problem: [2001/10/16 10:43:28, 0] smbd/password.c:connect_to_domain_password_server(1295)

Good morning, I am posting msgs on the NON OPERATION of WINBIND. GOOD I should say that without I had made any change in the system it started to work in an of my facilities. INCREDIBLE but it worked. The problem now is that I tried log in the samba not previously using an user servant in the smbpasswd and him of autentication mistake. But should not WINBIND facilitate that? Do I need to have user

Hi ... When trying to migrate from samba3 to samba 4.2.2 I am facing a severe problem that bugs me for hours now. I cannot get a samba 4.2.2 fileserver to work with a samba 4.2.2 PDC as a domain member. My scenario: Samba 3 network. PDC and fileserver where Samba 3.6.25. LDAP backend. We can't move to AD right now so I wanted to move to the current 4.2.2 at least to do this step but to

I have a few RHEL7 boxes, all of them are members in MS Win domain using SSSD. All of these linuxes run Samba for file sharing with the same config. Usually it works nice, but from time to time users cannot map Samba folders, with the following message in the log: [2017/03/07 14:58:27.050493, 0] ../source3/auth/auth_domain.c:121(connect_to_domain_password_server)

I have been (unsuccessfully) trying to get this up and running for the past few days. I have successfully setup samba itself NUMEROUS times but this winbind stuff has me stumped. I have built a fresh box for this server using Turbo Linux server 6.5 and samba 2.2.2. I have followed all the docs and man pages that i could find. 1. I have samba compiled (using --with-winbind --with-pam) and

Hello everyone, I am trying to configure a Samba 2.2 server to allow users to mount their home directories (stored on a UNIX filesystem) from Windows after authenticating against a Windows 2000 Domain Controller. The Samba server is 2.2.3a compiled with acl support on Solaris 8. I think I am experiencing some (hopefully) basic configuration issues and can't seem to get it to work. I

All, we have a SAMBA server set up that has been working great for everyone in the corporate office, not to long ago I connected one of our foreigh offices to us through a VPN. All of our users authenticate to our PDC, our users in our foreign office, who is on the same domain but we have them on a different subnet, are not able to gain access to the SAMBA shares, here in the corporate office.

I'm running version 2.0 beta. During the initial installation, I configured Samba to authenticate with an NT server. It worked as expected. Now, I want to reconfigure Samba with security = user. I've set encryption = no (and insured that the NT client is sending plain text passwords), and I've removed the references in the smb.conf file to PASSWORD SERVER =. As I expected, the NT

All, We were running samba4-4.0.0-68.el6_7.rc4.x86_64 on our CentOS 6 box serving printers and joined to our domain. No issues whatsoever and quite happy. We upgraded to samba4-4.2.10-6.el6_7.x86_64 and have had ongoing issues since it was installed. Everything runs along just fine for a while (an hour or so) and then our logs start filling with [2016/04/13 17:51:21.635283, 0]

Hello, I'm having problems with user names containing a dot. For example "j.smith". In our network we have Win2K PDC and a Samba server. smb.conf contains this: [global] security = domain password server = MYSERVER username map = /etc/samba/smbusers [myshare] valid users = j.smith write list = j.smith etc... /etc/samba/smbusers file contains this: jsmith = j.smith And Linux box

So far we have been working well for a week now. We are using Samba 3.02a on suse 9. Authentication is against an win3k AD. Apart from a Kerberos ticket expiring, (a croned restart fixes this) we have one new problem We found we needed an additional AD server as the primary begun to fail on a regular basis. So we added one. Now this new server grabs the authentication requests before the old one

I have one server windows2000 mixed mode with active directory and samba 3.0 PDC. This is my smb.conf [global] workgroup = TESTIPLANET netbios name = TEST server string = DOMINIO TEST interfaces = 10.10.6.158 bind interfaces only = yes preferred master = Yes domain master = Yes wins support = Yes domain logons = yes

Hi all, Set-up: Local NT4-RESOURCE domain which the Samba server is a member off. One NT4-ADMIN domain with users accounts and one W2K domain with some other user accounts. A one way trust from NT4-ADMIN to NT4-RESOURCE and a one way trust from W2K to NT4-RESOURCE. Samba version 2.0.7 running on Solaris 2.6. According to the NT admins, the W2K domain is in native mode, but they still use

Hi Sambafriends ! I have done a migration from Novell to a Samba-PDC in a medium enterprise with nearly 50 workstations eight weeks ago. When i look at the /var/log/warn listing i still see some errors, and i like to ask you, if this messages are "normal" ? smbd[7809]: [2003/02/11 18:26:45, 0] smbd/password.c:domain_client_validate(1517) smbd[7809]: domain_client_validate: could

hi all, just finished upgrading to 2.2.8a and things went well and without any sign of a glitch. I was able to log in from windows to my FreeBSD box as root just like before the upgrade. but then, all of a sudden, the box was no longer available from windows no sign of anything going on with the FreeBSD computer I can putty into it and it seems fine nmbd and smbd show up in top what could

Hi there! I appear to be having problems with trusted domains using 3.0a21. Using Samba as a member server, as user "nirs" on domain "Exanet-il" I am unable to log on to a member server ("snow") who is a member of the "Exanet-qa" domain. The "exanet-qa" is supposed to trust "exanet-il", and it all worked with 2.2 . This is the relevant

I am having a hard time joining to the w2k domain controller. here are few steps that i am trying to do to join w2k domain controller. SMB.CONF file # Global parameters [global] workgroup = Examples realm = EXAMPLES.COM server string = Comment of the server security = DOMAIN password server = PDC server address log file = /var/log/samba/smbd.log