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 machines on the network and I can't even manually map a share manually on the XP client using the full UNC path. Am I missing something in the smb.conf file or the XP registry settings to make it work?
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 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 machines on the network and I can't > even manually map a share manually on the XP client > using the full UNC path. > > Am I missing something in the smb.conf fileNo idea, you haven't posted your smb.conf ;-)> or the XP registry settings to make it work?This is probably where the problem lies, but this is just a guess. Your XP machines are probably expecting/sending NTLMv1 and your AD domain has this turned off, see here for how to make XP use NTLMv2: https://support.symantec.com/en_US/article.HOWTO54187.html Rowland
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 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 machines on the network and I can't >> even manually map a share manually on the XP client >> using the full UNC path. >> >> Am I missing something in the smb.conf file > >No idea, you haven't posted your smb.conf ;-) > >> or the XP registry settings to make it work? > >This is probably where the problem lies, but this is just a guess. Your >XP machines are probably expecting/sending NTLMv1 and your AD domain >has this turned off, see here for how to make XP use NTLMv2: > >https://support.symantec.com/en_US/article.HOWTO54187.html > >Rowland > > > >-- >To unsubscribe from this list go to the following URL and read the >instructions: https://lists.samba.org/mailman/options/samba