similar to: System error 64 occurred

Dear all, I am using Samba 3.0.20b on REdHat 7.2 and + OpenLDAP 2.2.X on another RedHat 7.3 When I try to connect to Samba from XP, it always returns "System error 64 occurred. The specified network name is no longer available." But I were using IP to connect to the samba so there should'n have network name issue. After I restart smbd, then everything fine. Is there any problem

Hi Timo, On 01.03.2016 22:51, Timo Sirainen wrote: > On 29 Feb 2016, at 17:18, Gordon Grubert <gordon.grubert+lists at uni-greifswald.de> wrote: >> >> Hi, >> >> we are using a round robin dns record for connections to our ldap >> system. This works fine for almost all cases. In particular, for >> dovecot does this mean, when an ldap server is stopped,

Hi Guys I have recently migrated an existing courier install to dovecot + openldap and think dovecot is wonderfull. Great work! However, I am seeing that dovecot-ldap doesnt reconnect if openldap restarts. Is there an options I am missing or is this a know problem?As I am using dovecot for sasl with postfix and pop/imap this basically completely stops my mail sytem... Thanks in Advance --

Hi, i've migrated a debian box into ads, most people can work as they should, some users eg which are not part of the domain can not authenticate themself, the log says NT_STATUS_INVALID_COMPUTER_NAME . After reading all the howtos i noticed that wbinfo -t doesn work, the output is: #wbinfo -t checking the trust secret via RPC calls failed error code was NT_STATUS_INVALID_COMPUTER_NAME

I am re-posting this with a subject line in line (hopefully) with your guidelines. Apologise if this causes any confusion. I'm fairly new to samba but I've spent too long on this - can anyone help? This system was previously working on another domain. Now I have tried to register it on the production domain (it has been removed from the test domain and I've deleted the secrets file

the output is below: C:\>net view \\grumpy System error 53 has occurred. The network path was not found. i tried the suggestions in DIAGNOSIS to no avail. can someone please help me troubleshoot this? tia if (duane.douglas) { technologies = asp && php && cgi_perl && cold fusion && xml && xsl && xsd && sql server && mysql

Hi all, I can't succeed to compil samba-3.0.20b on a solaris 10 box with ldapsam parameter. The configure is ok: ./configure --prefix=/export/zoe/samba-3.0.20b --with-pam --with-ldap=/usr/local/openldap-2.2.26 --with-ldapsam --with-krb5=/usr/local/krb5-1.4.3 but when I try to do the make I have the following error: [zoe.root:56] make Using FLAGS = -I/usr/local/krb5-1.4.3/include -O

Hi gurus, Am using Win XP professional and SUSE 9.3 professional and samba version is 3.0.13-1.1 am able to access my XP machine from samba server using smbclient \\<xp<file://\\<xp>machine name>\<share drive> but when i give net view \\<samba <file://\\<samba> server> it gives following error "System error 53 has occurred. The network path was not

Hi, When I am logging from the windows NT /2000/XP clients, I am getting this error message while running the Login script. the message which i am getting is 'system error 85 has occurred' .I am generating the login script on the fly when user is loggin in. How can I solve this error. Pl any one help me. with warm regards, Rajesh Rajesh Prakasan Sr. Data Centre Executive DIREM

Hello Andreas, Am 02.02.2015 um 13:00 schrieb Andreas Hauffe: > I set up a new AD with the Sernet Samba 4.1 packages. I did the provisioning > with "samba-tool domain provision --use-rfc2307 --interactive". I checked the > dc, ldap, kerberos and dns services under linux. Everything seems to work > fine. > > Then I join a Windows 8.1 Enterprise running in as VM to

W dniu 2019-09-16 o?19:43, Rowland penny via samba pisze: > On 16/09/2019 17:26, Bart?omiej Solarz-Nies?uchowski wrote: >> So how can I drop DC "oceanic" and reconnect whole network to DC >> "themes"? >> >> (when I do it DC will be on server which has no shares (only netlogon >> + sysvol?)) > > If 'oceanic' was the first AD DC

One more obvious line from the log: dovecot[26621]: auth: Error: LDAP: Connection lost to LDAP server, reconnecting Where it claims to reconnect, but after that there is no LDAP authentication. And the same configuration has worked fine since at least 10 years ago up to some recent update of dovecot or openldap. Best Dag

Greetings: I'm on section 3.2 (page 7) of the SAMBA-LDAP PDC HowTo and am getting errors. This is on a brand-new install on RedHat 7.2, using openldap-2.0.23-4.i386.rpm, openldap-clients-2.0.23-4.i386.rpm, and openldap-servers-2.0.23-4.i386.rpm from the 7.3 tree from a RedHat mirror (Rawhide wouldn't let me in at that point) and samba-2.2.4-2.src.rpm from RedHat's Rawhide tree. My

Hi everybody! In my company, we want to migrate from Windows NT to a Linux PDC. I am responsible for the change so I am searching for the best solution. After some time surfnig in google, I decide to use a LDAP server for users maintenance and SAMBA as a file server. and PDC controller The first step was configure LDAP for autenticating linux users, which works fine. Then I configure SAMBA

Hello all, I am using Samba on a Debian GNU/Linux box. I am trying to create a netlogon.bat file that will execute whenever a user logs in to the domain. However, I am getting a strange error message on the client workstations. The following is the netlogon.bat: echo Setting Current Time... net time \\xavier /set /yes echo Mapping Network Drives to Samba Server Xavier... net use Z:

Dear Sir, I have been getting this error on the PC site when I tried to connect to the Samba server. I have Red Hat 8.0 installed and I am using Windows 2000 Server as client. I have tried all the steps listed in the 'DIAGNOSIS.txt' and here are the results. Test 1, 2,3,4 passed. Test 5: I can only use IP but not PC Name. Test 6, 7 passed. Test 8: I got "System error 53 has

Hello, I've upgraded a Linux box from Debian 2.0 to Debian 2.2 (potato), before the upgrade I had Samba 1.9.18 which worked without any problem. Upgrading to Samba 2.0.6 (debian version), now every connection fails with this error: [2000/01/31 12:07:36, 0] lib/util_sec.c:assert_gid(72) Failed to set gid privileges to (-1,65534) now set to (0,0) uid=(0,0) [2000/01/31 12:07:36, 0]

Hello, I set up a new AD with the Sernet Samba 4.1 packages. I did the provisioning with "samba-tool domain provision --use-rfc2307 --interactive". I checked the dc, ldap, kerberos and dns services under linux. Everything seems to work fine. Then I join a Windows 8.1 Enterprise running in as VM to the domain and login as administrator of the domain. When I install the RSAT and try

Am Montag, 2. Februar 2015, 17:44:53 schrieb Marc Muehlfeld: > Hello Andreas, > > Am 02.02.2015 um 13:00 schrieb Andreas Hauffe: > > I set up a new AD with the Sernet Samba 4.1 packages. I did the > > provisioning with "samba-tool domain provision --use-rfc2307 > > --interactive". I checked the dc, ldap, kerberos and dns services under > > linux.

Hi all, ?I'm new to sssd configs and debugging. Recently we have encountered some problems with sssd. Basically 6 out of 50 servers has 'getent passwd' lost all userIDs from LDAP backend, while others are OK.? My sssd is at version 1.8.0-32. the related error messages are attached below. The sssd_nss seems got killed by temporarily network connection problems to backend openLDAP