similar to: Win XP Client with Samba AD - Mapping Shares

On 2/27/2019 3:01 PM, Rowland Penny via samba wrote: > On Wed, 27 Feb 2019 14:50:34 -0500 > Marco Shmerykowsky PE via samba <samba at lists.samba.org> wrote: > >> I'm having issues having WinXP client access shares >> on my Samba domain. >> >> The user account can authenticate to the network using a >> Win10 client. The win10 client maps the users

In the process of upgrading my whole samba setup. I've setup a server as an active directory controller, I created a stand alone member server, I've gotten win10 to join the domain and drive mapping via group policies seems to work with win 10 clients. I still have a few winXP clients that have usefullness. They seem to connect to the domain ok, but they can't see any of the

Thanks. Will check. I should have added that everything was working fine on the old winNT style samba domain setup. Its something related to the new samba AD setup On February 17, 2019 8:17:03 AM EST, Rowland Penny via samba <samba at lists.samba.org> wrote: >On Sun, 17 Feb 2019 07:51:24 -0500 >Marco Shmerykowsky via samba <samba at lists.samba.org> wrote: > >> In

On Sun, 17 Feb 2019 07:51:24 -0500 Marco Shmerykowsky via samba <samba at lists.samba.org> wrote: > In the process of upgrading my whole samba setup. > > I've setup a server as an active directory controller, I > created a stand alone member server, I've gotten win10 > to join the domain and drive mapping via group policies > seems to work with win 10 clients.

I tried the NTLM setting. No change. When I try to browse the network, I get the following error: "internal is not accessible. You might not have permission to use this network resource. The list of servers for this workgroup is not currently available." Here is the smb.conf from the AD machine. [global] netbios name = MACHINE251 realm = INTERNAL.DOMAIN.COM

On Wed, December 5, 2018 9:52 am, Rowland Penny via samba wrote: > On Wed, 5 Dec 2018 09:41:13 -0500 > Marco Shmerykowsky via samba <samba at lists.samba.org> wrote: > >> I'm trying to setup a Samba4 Active Directory server. >> >> I've gotten the server running, the IP addresses resolve >> properly. The Windows10 client can join the domain. >>

Hi, I'm not able to join a windows XP machine in samba AD DC. This XP machine is a VM. No problems when joining Windows 10 machines to this DC. On XP machine, after inserting the Administrator username\password to join the domain, the error message is - error while attempting to join the domain "VIDROESTE.IND": Internal error. I can see that the XP machine account was created in AD

On Tue, 16 Jun 2020, Rowland penny via samba wrote: > On 16/06/2020 12:41, Harald Hannelius via samba wrote: >> I have Samba AD-domain with two fileservers and two Samba DS-servers. Most >> people can authenticate OK, but one user always gets "wrong password". > What versions of Samba ? All servers are 4.9.5-Debian. >> Auth: [SMB2,(null)] user [SAD]\[username]

On Wed, 5 Dec 2018 10:56:48 -0500 Marco Shmerykowsky PE via samba <samba at lists.samba.org> wrote: > > On 12/5/2018 10:37 AM, Marco Shmerykowsky via samba wrote: > > On Wed, December 5, 2018 9:52 am, Rowland Penny via samba wrote: > >> On Wed, 5 Dec 2018 09:41:13 -0500 > >> Marco Shmerykowsky via samba <samba at lists.samba.org> wrote: > >>

On 2019-02-17 10:54 am, Rowland Penny via samba wrote: > On Sun, 17 Feb 2019 10:37:48 -0500 > Marco Shmerykowsky <marco at sce-engineers.com> wrote: > > >> >> Seems I can map a drive from the command line. (Didn't check that >> - it was 2:00am and I was tired with fighting this stuff) > > Time you went to bed ;-) > > its 15:45 Sun here. >

Is there a recommendation for good books covering the setup/deployment of Samba 4 using an Active Directory structure? Something on the order of "The Official Samba-3 HOWTO and Reference Guide"? I've setup a Samba4 server and I've gotten a Win10 machine to join the domain, but i can't seem to move past that to get a user to login or to create a share. Sort of blindly

I'm trying to setup a Samba4 Active Directory server. I've gotten the server running, the IP addresses resolve properly. The Windows10 client can join the domain. I've run the basic checks that seem to be listed on the samba wiki and get the expected results. I've modified nsswitch.conf to include winbind on the passwd and group lines. I've made sure all machines are

Am 14.11.2019 um 16:23 schrieb Christopher Wensink: > We have the same setup and have had no problems with clients mapping shares. > > Some simple tips: > > double check spelling of all usernames and that passwords on the clients > match that of the samba shares > > try setting up a user that can connect on their pc with a login on one > that cannot, see if the

I have Samba AD-domain with two fileservers and two Samba DS-servers. Most people can authenticate OK, but one user always gets "wrong password". I tried changing this user's password, and was able to connect by using smbclient, and I was also able to map this drive using the user's username and password on my own windows 10 workstation. Also; # wbinfo -a username Enter

I have a win10 VM in virtualbox on my Linux (C7) desktop. I CAN connect to it with rdesktop 1.8.3 (now rather old, but it's the latest release), but cannot connect with remmina or krdc. Both of them just hang for a while then say they can't connect. Curiously, they all will connect to the win10 box in my office. They don't show any other useful information, and I don't know where

Hopefully this is a simple problem for a guru to solve. I have been installing Centos / Samba servers for my clients since 2004. However, in almost every instance, the linux machine has been the only server on site. To begin with I set up the server as a domain server but as most of my customers have less than a dozen PCs on a single site, the domain seemed to be an overkill so I now tend to use

I've been running Samba 4 in NT4 Domain mode for a few years, and it's been working fine with Windows 7 PCs. I now need to join a new Windows 10 PC to the domain, but I'm not having any success! When I try to join the domain, the Windows 10 PC says "An Active Directory Domain Controller could not be contacted...." I've tried a few things, including:- Setting

On 2019-02-17 10:17 am, Rowland Penny via samba wrote: > On Sun, 17 Feb 2019 09:53:56 -0500 > Marco Shmerykowsky <marco at sce-engineers.com> wrote: > >> I tried the NTLM setting. No change. >> >> When I try to browse the network, I get the following error: >> >> "internal is not accessible. You might not have permission to >> use this

Hallo, We are using centos 7 and samba in combination with Win10 1903. The problem: Some systems are able to map a share and some can t. Any ideas and hints? Thanks Ralf

I have an old setup that serves my purposes, but which I'll move over to a more modern Samba4 setup at some point. I know it's old, deprecated etc. In any case, at the moment I'm having a problem with two Windows 10 machines connecting to the domain I set up. The network is a mix of XP, Windows 7 and Windows 10 machines. Four (4) windows 10 machines connect to the domain after the