I tried 'domain\username' in adexplorer as you say.But it doesn't work, too. It's the same warning. Do you remember I've ever mentioned that when I try to join the domain it succeed but still warned 'change the primary domain dns name of this computer to "" failed. the rpc server is unavailable.' I tried this in windows 7 and windows8.1, bath gave this warning. Do you get any clue from this for my problem? Thanks.>On Fri, 20 Apr 2018 17:14:03 +0800 >"ryanyang51 at 163.com" <ryanyang51 at 163.com> wrote: > >> But the program works well with samba4.5.x. In fact I think it's the >> compile progress or the rpm has something wrong. So I want to know if >> my configure option or build option is not right. Although they are >> right for 4.5.x. >> > >I downloaded adexplorer to a win10 machine and ran it. > >Entered the following info: > > Connect to --> dc4.samdom.example.com > User --> Adminisrator > Password --> xxxxxxxxxx > >Clicked on OK and I got a warning 'The directory service is unavailable' > >I Changed the User to 'samdom\Adminisrator' > >Clicked OK again and it now works. > >So it looks like something has changed and you need to update your C# >program. > >Rowland > >-- >To unsubscribe from this list go to the following URL and read the >instructions: https://lists.samba.org/mailman/options/samba
On Sat, 21 Apr 2018 10:08:46 +0800 (CST) Ryan <ryanyang51 at 163.com> wrote:> I tried 'domain\username' in adexplorer as you say.But it doesn't > work, too. It's the same warning. Do you remember I've ever mentioned > that when I try to join the domain it succeed but still warned > 'change the primary domain dns name of this computer to "" failed. > the rpc server is unavailable.' I tried this in windows 7 and > windows8.1, bath gave this warning. Do you get any clue from this for > my problem? Thanks. > >OK, I found that the Win10 machines I was using were not '1709', one was '1511', the other '1607' [RANT] Why is windows update so c**p ??? I tried to update the '1511' machine to 1709, but, what ever I tried, it failed, so I moved to the '1607' machine. this failed to update several times until, for no reason what so ever, it decided to work. [/RANT OFF] I can connect using to Ad using adexplorer on the 1709 machine just as before i.e. I have to specify the DOMAIN with the username. All I can suggest is, leave the domain on the windows machine, check that it is a member of the same dns domain as the AD DC and then re-join the domain. What ever the problem is, it doesn't seem to be a Samba problem. Rowland
Er..Actrually I don't use any windows as DC. Windows computer just the domain member for me. I've seen a similar thread https://lists.samba.org/archive/samba/2017-July/209728.html. I want to build a domain only using samba in linux as the DC. It's a new domain and my first DC. I'd like to believe it is not a samba problem. After all, it occurs in 4.7.x and 4.8.x, a such large range. Situation is that, I can get rpms and install them successfully. But function not well. My thought is, firstly confrim my config options during build process are right for a AD DC. Secondly, see if there is any wrong about the configuration after install. But all my configuration is the same as it for 4.5.x. Have no idea to figure it out...>On Sat, 21 Apr 2018 10:08:46 +0800 (CST) >Ryan <ryanyang51 at 163.com> wrote: > >> I tried 'domain\username' in adexplorer as you say.But it doesn't >> work, too. It's the same warning. Do you remember I've ever mentioned >> that when I try to join the domain it succeed but still warned >> 'change the primary domain dns name of this computer to "" failed. >> the rpc server is unavailable.' I tried this in windows 7 and >> windows8.1, bath gave this warning. Do you get any clue from this for >> my problem? Thanks. >> >> > >OK, I found that the Win10 machines I was using were not '1709', one >was '1511', the other '1607' > >[RANT] >Why is windows update so c**p ??? >I tried to update the '1511' machine to 1709, but, what ever I tried, it >failed, so I moved to the '1607' machine. this failed to update several >times until, for no reason what so ever, it decided to work. >[/RANT OFF] > >I can connect using to Ad using adexplorer on the 1709 machine just as >before i.e. I have to specify the DOMAIN with the username. > >All I can suggest is, leave the domain on the windows machine, check >that it is a member of the same dns domain as the AD DC and then >re-join the domain. What ever the problem is, it doesn't seem to be a >Samba problem. > >Rowland > >-- >To unsubscribe from this list go to the following URL and read the >instructions: https://lists.samba.org/mailman/options/samba