Active directory Problem

Support
,
13

Blue_Diamond, note this is just an example. In your setup 192.168.1.1 might be already taken by your router, which it is most probably also serving addresses through DHCP.

14

I tried but it gives me another problem

IMG_20191207_190515_775
IMG_20191207_190515_775.jpg1280×690 81.7 KB

15

How can I fix?

16

Can Nethserver reach the Internet (ping external IP and external domain name)?

17

Yes ping works

18

run:

yum clean all

and retry.

19

Tried, Same error

20

Is the server able to resolve mirror.nethserver.org

21

It can’t resolve it. What I need to do?

22

Can it resolve other public domains?

23

Others yes

24

You can try changing NethServer DNS settings.
Is NethServer behind a proxy/firewall?

25

Maybe related? Failed connection to mirrorlist.nethserver.org from Russia

26

No, it’s not behind a proxy/firewall.
I have set dns 8.8.8.8

27

Yes, also this

28

Try to join your AD with older Gui ipnethserver:980 with an free ip again…

29

I join from the older Gui… Each time I didn’t try to join AD on gui 9090

30

Hi Vitor,

I you tried an IP and it failed, then you have to change for another IP because I think the installation remembers the previous IP.

The best way is to have a virtual machine to try things, then you can go back to a previous state if something fails.

Not sure, but I think the DHCP always tests if the IP is taken before issuing it to a client?

Michel-André

31

Hello Marc, Until now I didn’t had problems at all with this config… Awkward behavior, but as robb has said, the best pratice is to maybe assign out of dhcp scope reducing dchp scope itself

Happy New Year 2020

Best Regards

32

@Vitor_Hugo_Barbosa @michelandre
Maybe I am ‘old school’. My first encounters with DHCP are from Windows NT3.5 and NT4 era. And back then it was considered ‘best practice’ to have you fixed addresses not inside the scope of your DHCP range. Maybe it’s not necessary anymore because DHCPd is a bit ‘smarter’ nowadays, but I still think it would be good practice to have your DHCP scope not overlap fixed addresses, just for your own administration. I think it is good practice to even decide what kind of devices get what ip addresses.
For instance:
gateway: always x.x.x.1
DC: always x.x.x.2
DHCP: if not on the same as DC, always x.x.x.3
servers with local services: x.x.x.10 -x.x.x.19 (better put them in a seperate VLAN with a gateway at x.x.x.10)
printers: x.x.x.20 - x.x.x.49
DHCP scope: x.x.x.50 - x.x.x.250