similar to: %a variable and Windows 7

Hi, I encountered a strange problem...some of my windows machines cannot be joined to an Samba 4.17 AD domain (8 of ~90 clients). These are 7 Win7 clients and one WinXP client. The message I receive in windows is: "Logon failure: unknown user name or bad password". All other Win7 and XP machines could be joined...the same OS image has been used to install both the machines that could be

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

We installed the Samba 3.5.1 rpms for OpenSuSE 10.2 from ftp.sernet.de. The VFS modules seem to be broken. Is this an error in the packaging or do I need to be looking else where. A snippet from the log file follows: <extracted from log> [2010/03/12 19:58:59, 0, pid=28792, effective(0, 0), real(0, 0)] smbd/vfs.c:66(smb_register_vfs) Failed to register vfs module. The module

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

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

Hello Sambaers, i can not access my samba shares after upgrade my centos to 7.4,samba version was upgraded to 4.6.2 i joined centos to windows domain by realm command,domain user(format as username at doaminname) could login to centos could get kerberos ticket by kinit with domain user execute net view command at domain windows server get access denied C:\>net view

> On 25 Jul 2016, at 19:49, Rowland penny <rpenny at samba.org> wrote: > > On 25/07/16 19:32, Kevin Davidson wrote: >>> On 25 Jul 2016, at 16:39, Rowland penny <rpenny at samba.org> wrote: >>> >>> On 25/07/16 16:02, Kevin Davidson wrote: >>>> Having problems with rfc2307 user ids. This was working briefly and now it’s not.

> On 25 Jul 2016, at 16:39, Rowland penny <rpenny at samba.org> wrote: > > On 25/07/16 16:02, Kevin Davidson wrote: >> Having problems with rfc2307 user ids. This was working briefly and now it’s not. >> >> samba and winbind v 2.4.2.10+dfs >> >> […] >> What have I done wrong? >> > > You haven't done anything wrong. > >

I'm running 3.4.6 (was running 3.0.28a but upgraded in hopes to fix this issue). Clients running Windows 7 that are NOT joined to the AD domain (samba authenticates against it via "security = server") cannot authenticate to access the server. Clients running Windows 7 that are on the domain as well as Windows XP, Windows 2003 on and off the domain work as expected. Any help would

I am trying to get Samba 3.4.0 (on an Ubuntu 9.10 box) set up as a file server for my home. The router is 10.1.10.1; the Ubuntu box ("chronicles") is 10.1.10.2; the OS X box I'm using for testing purposes ("job") is 10.1.10.3. From job, I can see ports 139 and 445 on chronicles are open. Neither box has 'chronicles' or 'job' listed in its /etc/hosts file.

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

This is a new Samba config that has not yet worked. I have installed sernet-samba 4.1.14. [root at sltltfsee samba]# rpm -qa | grep sernet sernet-samba-libsmbclient0-4.1.14-10.el6.x86_64 sernet-samba-common-4.1.14-10.el6.x86_64 sernet-samba-4.1.14-10.el6.x86_64 sernet-samba-libs-4.1.14-10.el6.x86_64 sernet-samba-winbind-4.1.14-10.el6.x86_64 sernet-samba-client-4.1.14-10.el6.x86_64 I have been

*testparm -v | grep "client min protocol"* client min protocol = CORE On Tue, Apr 19, 2016 at 2:50 PM, lingpanda101 at gmail.com < lingpanda101 at gmail.com> wrote: > On 4/19/2016 2:43 PM, Bill Baird wrote: > > I am accessing the new member server. All my other servers are still on > 3.6.x. > > Both settings are set to "default". > > Will look at

We are currently using samba and openLDAP to enable our users to have roaming profiles on our domain network. We have one primary domain controller and 7 "home servers" at the various locations that serve the profiles and such. The problem is that randomly various users are unable to load their profile and windows just gives them a temporary profile. This mostly happens on vista

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

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

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

Dear Rowland , Just keep in mind that the Debian RPI maintated by rasperry.org PI fellows and _not_ mainly by the Mainsteam debian pkg maintainers, and ways behind the main distro - allmost. > > Even though there is no mention of dlopen, samba_dlz works. > yes/no ->> its not displaying the DLZ file open <<- and that happen even on my now +1J old samba4.0 RPI samba4 ad.