similar to: Samba 4.17 AD Cannot connect to shares as administrator

Hi Davor, thanks for the answer. They were actually part of a NT4 domain called mayweg.net (the new realm name). But I did join workgroup "WORKGROUP" before I tried to join the new domain. If it's possible that they're sending the information the wrong way because they were part of a workgroup named after the new realm, is there any way to clear the old data (apart from a new

Hi Davor, most of the domain accounts were part of an old NT4 domain. I did a classicupgrade. Your theory with the NTUSER.DAT-files seemed so promising, unfortunately that was not it. I created new accounts on an XP machine and a Win7 machine and tried to join with them, but still receive the same error. One of the machines I'm not able to join with, wasn't even part of the domain

Hi Davor, I finally found it! After going through https://wiki.samba.org/index.php/Joining_a_Windows_Client_to_a_Domain , I checked the time settings on said clients and they differed from the AD DC too much. This also explains why some clients could join after a while...they synchronised with a NTP server after a day or so and then I was able to join. After that, joining the rest of clients was

Timo Altun skrev den 2015-05-19 08:12: > Hi Davor, > > thanks for the answer. They were actually part of a NT4 domain called > mayweg.net <http://mayweg.net> (the new realm name). But I did join > workgroup "WORKGROUP" before I tried to join the new domain. > If it's possible that they're sending the information the wrong way > because they were part

On 2015-05-20 09:21, Timo Altun wrote: > Hi Davor, > > most of the domain accounts were part of an old NT4 domain. I did a > classicupgrade. > > Your theory with the NTUSER.DAT-files seemed so promising, > unfortunately that was not it. I created new accounts on an XP machine > and a Win7 machine and tried to join with them, but still receive the > same error. One of

So you use images!? Are you shure you used different host names for each client. We found using install images will do this confusion some times because windows announced with the image name not with the new one. EDV Daniel M?ller Leitung EDV Tropenklinik Paul-Lechler-Krankenhaus Paul-Lechler-Str. 24 72076 T?bingen Tel.: 07071/206-463, Fax: 07071/206-499 eMail: mueller at tropenklinik.de

Hello, I have a strange problem with Samba AD member: It is accessible via \\server or \\server.domain.local But when I try to access it with its IP address, ex. \\10.15.10.1 I get access denied error and prompt for user and pass. Entering username and password with or without DOMAIN\ has no effect. The server is FreeBSD 10.1. It behaves the same way with Samba 4.1.18 and now with Samba 4.2.2

Good morning Rowland and samba list ... Rowland Penny wrote on 03.07.2015 18:36:32: > From: Rowland Penny <rowlandpenny241155 at gmail.com> > To: samba at lists.samba.org, > Date: 03.07.2015 18:40 > Subject: Re: [Samba] Migration Samba3 -> Samba4: Accessing domain > member server is not working > Sent by: samba-bounces at lists.samba.org > > On 03/07/15

Greetings, All! I'm trying final steps of my long upgrade process, but I've got hit by the unexpected. When everything seemingly run fine in the end, I'm unable to browse the local shares of the DC. # smbclient -L localhost -U% Domain=[CCENTER] OS=[Unix] Server=[Samba 4.1.11-Ubuntu] Sharename Type Comment --------- ---- ------- Error returning

Hello to the Samba Mailing List, This is my first post, so please, should I commit any faux pas, nudge me in the right direction and I will adjust accordingly. I'm experiencing a complete failure of the PDC in a Samba 4 AD Domain I've deployed for a client. Samba failed a few days ago and I've been unable to resolve the issue on my own. Google searches are leading me in circles,

Hello, I have installed Samba4 on Debian8. RSAT from windows 7 works fine(all) and before a few days I have tried create a new domain user via RSAT on Windows 8, but something block to finish this step with popUp 'An error occured. Contact your system administrator' on samba server from log: [2015/06/15 12:04:23.431150, 2] ../source3/smbd/server.c:419(remove_child_pid) Could not

Hi, I have a samba 4.5.8 AD DC (debian 9.1 package) which is having problems with RPC requests. This DC has been updated from the wheezy-backports package (4.1.17) via the jessie package (4.2.14) but I'm not sure if RPC worked immediately before the upgrade either since most of the time it only serves LDAP and krb5. Connecting using RSAT from windows gives "RPC Server

Hello, I am attempting to debug an issue with my Samba configuration. It has been working fine, but we recently updated Samba from 4.6.x to 4.8.3 and are now seeing some issues authenticating. Most of our servers are still working fine after the upgrade, but one server is giving us issues. A little more environment info: The server is running Centos 7.1. Windows clients can connect OK. We are

Greetings, Rowland Penny! Got some logs. But... they do not make much sense. It seems to fail to chdir to /tmp. But I can do it with sudo just fine under the same credentials. What's going on? [2015/03/30 01:05:38.027147, 3, effective(0, 0), real(0, 0)] ../source3/lib/access.c:338(allow_access) Allowed connection from 127.0.0.1 (127.0.0.1) [2015/03/30 01:05:38.027425, 3, effective(0, 0),

I have a small home network with server and 5 clients all on an internal LAN with private IPs. Samba, Version 4.7.6-Ubuntu, file sharing is not working on the server for any of the 5 clients. I have tried both mount.cifs and smbclient. The same errors are thrown in the server's samba logs for all connection attempts, regardless of how the client tries to connect: getpwuid(1000) failed,

Mandi! Rowland penny via samba In chel di` si favelave... > Even though your users may have the same username in AD as in the NT4-style > domain, they are different users, so a few thoughts. You have 'map to guest > = bad user', so I take it you must have 'guest ok = yes' set in the shares > (you haven't shown us the shares), so try changing 'bad user' to

Hi, Just a moments ago i've sent a message to other user saying that I've a working server with CUPS authentication using AD groups. Well, that authentication is not working anymore and i've not changed anything... The thursday I was configuring the server to allow the management of cups with AD groups and was working perfect. After that i've added some printer alias to samba

Hi Ivo, I think I've a very similar issue on 4.1.16 and it seem that hosts allow = 10.15. 127.0.0.1 interfaces = localhost, re0 is to blame. please try to comment them and see if that work. On Mon, Aug 3, 2015 at 4:54 AM, Ivo Karabojkov <karabojkov at kit.bg> wrote: > Hello, > > I have a strange problem with Samba AD member: > It is accessible via \\server or

On 30/12/15 03:36, IT Admin wrote: > Hello to the Samba Mailing List, > > This is my first post, so please, should I commit any faux pas, nudge me in > the right direction and I will adjust accordingly. > > I'm experiencing a complete failure of the PDC in a Samba 4 AD Domain I've > deployed for a client. Samba failed a few days ago and I've been unable to >

Hai, Can be incorrect rights, of corrupted db. Can you give the output of ls -al /var/lib/samba/ ls -al /var/lib/samba/private ls -al /var/lib/samba/private/dns Greetz, Louis > -----Oorspronkelijk bericht----- > Van: samba [mailto:samba-bounces at lists.samba.org] Namens IT Admin > Verzonden: woensdag 30 december 2015 4:37 > Aan: samba at lists.samba.org > Onderwerp: