similar to: Domain server member cannot locate logon server.

I have a new CentOS 7 installation which I joined to my domain using 'realm join mydomain.com'. That worked great. I can get a ticket with 'kinit administrator at mydomain.com'. But my samba shares don't work. In fact, when I browse (from windows 7 domain member) to the host (lserver), it just times out. Similarly, when I try from another Linux server: smbclient

Hello, We had a strange thing happen today - we shut down our system (virtual machines) so that some work could be done in the server closet and everything was shut down gracefully but when everything was started back up I can no longer access my file server from windows. I get the following message in windows: \\fs1 is not accessible. You might not have permission to use this network

Hi, I'm having this authentication problem from a samba domain member; let's call this machine MEMBER. From MEMBER, if I do: wbinfo -a usr%pwd I receive: error code was NT_STATUS_NO_SUCH_USER (0xc0000064) error messsage was: No such user Could not authenticate user smediavilla%musica with plaintext password challenge/response password authentication failed error code was

Hi again, trying more tests, I give some more info: In MEMBER machine, when I run winbind in a terminal window (WINDOW1) not daemonized, that is, winbindd -FSi and call wbinfo -a in another terminal window (WINDOW2), in WINDOW1 I see two lines with this error: prs_mem_get: reading data of size 8650916 would overrun buffer by 8650420 bytes. Also, trying to capture the network packets out

We recently upgraded our PDC from Debian 4 to Debian 5. That entailed an upgrade of Samba from 3.0.24 to 3.2.5. Since the upgrade we've had a very specific problem connecting to shares on a commercial NAS running Samba 3.0.34. The problem happens when users try to connect to shares from standalone servers--e.g., Windows XP Pro boxes that we use for testing. From those boxes users should be

Hi, I'm trying to build a samba server that shall substitue one of our NT4 servers but I'm having some problems with setting up the local user account: The NT4 server was member of a ressource domain (R1) and also had a local user account named "bcd" which is needed for a boot-cd. Normal users authenticated through the master domains M1 and M2 which has all the necessary trusts

Hi, Formerly, I was successfully to use Samba 3.0.28a + FreeRADIUS 1.1.7 for Wi-Fi PEAP authentication against Windows 2003 AD. Now, I would like to replace Windows AD with Samba4. I build Samba4 successfully from source on Ubuntu 12.04.1 and the Samba4 domain controller seems function normally, e.g. able to work with the Samba4 domain with RSAT and edit the group policy. However, when I

Hi all, I'm running samba-3.0.25b w/Linux 2.6.16.27 (SUSE 10.1), newly compiled. I've joined the AD domain (which is a subdomain) whose PDC is Win2K3 server and which is running in native mode but allowing NT4 members. From the HOWTO, I followed the instructions - manually created the computer account, then did the "net rpc join ...." and successfully joined the AD

Hi folks, Can anyone shed light on this issue? I haven't heard from you guys. Is there anything else I could do to expedite resolution of this issue? I've read the WHATSNEW.txt and reviewed the release notes. I am not sure if I've fully grasped what needs to be done. Can someone point me in the right direction? ~Doug -----Original Message----- From: Doug Sampson

No takers thus far. These are the Samba 4.2 changes to which I previously referred (https://www.samba.org/samba/history/samba-4.2.0.html) : For the client side we have the following new options: "require strong key" (yes by default), "reject md5 servers" (no by default). E.g. for Samba 3.0.37 you need "require strong key = no" and for NT4 DCs

I should add that the samba.log file was logging NT_STATUS_NO_LOGON_SERVERS errors when authentication attempts were failing. Workstations in the domains were still able to authenticate, however, and I verified that the DNS records were still correct. The SRV records were all in place and the domain controllers' host names were resolving. On Wed, Jun 22, 2016 at 9:44 AM, Eric Shell

I have installed RedHat ES 3.0 It came with samba 3.0.0-14.3E.i386 I have no SWAT. Which one can I use? I downloaded samba-swat-3.0.0-1.test.rh90.i386.rpm and an rpm -i said it needs: samba 3.0.0-1.test.rh90 I downloaded samba-swat-2.2.7a-8.9.0.i386.rpm and an rpm -i said it needs: samba 2.2.7a Which SWAT do I need and where can I download it? thanks, in advance. Dean

I'm trying to install themes for KDE. In doing so, I came across the following web site which seems to have the themes I want as RPMs: http://rpm.pbone.net/index.php3/stat/17/dept/3/idg/User+Interface_Desktop The theme I want is called "Thinkeramik", and it has the following versions, for various Red Hat builds: thinkeramik-3.2.1-1.0.el3.kde.i386.rpm RedHat EL 3

I portupgraded my samba domain server and domain member to 3.0.23b from 3.0.23 and found that the domain member was not accessible from workstations. The error message: \\HOSTNAME is not accessible. There are currently no logon servers available to service the logon request. In the log.winbindd of the domain member, I found: [2006/08/23 22:52:00, 0] nsswitch/winbindd.c:request_len_recv(517)

Hi @all, this is an very old problem, posted the first time 2005 to samba-testers at samba.org: If I have a Domain client with WinXP, which is part of a domain and using this client, if the PDC is not available and want to remote shut down this client with the net tool from other servers, then this is not possible, because net tries to authenticate against the PDC: testeis # net -d3 -S

Hello everyone, Been trying hard to get my RH9 running as NT Domain member which keep failing at the authentication of another XP/2000 users. I have no problem if I create a unix account and samba account, but I = need winbindd. OS: RedHat 9.0 Samba: 2.2.8 smb.conf 1. set Security=3D domain 2. set password server=3D * / or netbios name of my PDC 3.separate domain and username with

I have my Samba 3.0.21c Linux Server as Domain member (security=ADS) so that domain users can use the Samba Server as shared file server. Everything works nice if the domain controller is present, e.g. wbinfo -a DOMAIN\\donald%donald plaintext password authentication succeeded challenge/response password authentication succeeded (this just simulates a Windows 2000 Client using the share which

I've configured a domain trust between Samba 3.5.6 and Windows 2003 Server Enterprise Edition SP2. It's a one way trust, Windows is the trusted and Samba the trusting. I want to give access to my resources in the Samba domain to the users in the Windows domain. The configuration of the trust was fine (I think). The validation on the window server says that it' s ok and the Windows

I am trying to upgrade our fully functional Samba domain from v3.0.2 to v3.0.7 or v3.0.8. My question is, do I have to upgrade every server in the domain in order for it to work or should I be able to upgrade one server at a time, test it, and move on to the next server? Or should I upgrade the domain controller first, then upgrade the member servers one at a time? I've tried to upgrade

I was able to resolve this issue. Just in case anyone is interested, I HAD to upgrade the PDC FIRST. Then I was able to upgrade the member servers without problems. ********************************************************* I am trying to upgrade our fully functional Samba domain from v3.0.2 to v3.0.7 or v3.0.8. My question is, do I have to upgrade every server in the domain in order for it to