join linux server to windows AD
am getting this error in windows
(Password propagation is not done. Either default encryption key is configured or no UNIX hosts configured to propagate password.)
then computer will join to windows AD but dns update fail.
(Password propagation is not done. Either default encryption key is configured or no UNIX hosts configured to propagate password.)
then computer will join to windows AD but dns update fail.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
1- i have windows AD + Dhcp
2-do u mean that i have to reserve ip address from dhcp scop or what
not that i have already joined 4 redhat server to windows AD but after that am facing this issue
i can the redhat server in windows AD comuputer but it is not automatically registering the dns records.
2-do u mean that i have to reserve ip address from dhcp scop or what
not that i have already joined 4 redhat server to windows AD but after that am facing this issue
i can the redhat server in windows AD comuputer but it is not automatically registering the dns records.
Do you have any of the RedHat systems configured with OpenLDAP?
That is the only possible destination to which password would propagate.
Which DNS update fails, the reverse host registration? Check the /etc/smb.conf to see to which interface it is bound/sending the DNS registration events?
You have to have DNS on your AD, do you have non AD based Name server listed on the server/clients?
I.e. are you pushing external DNS servers to the client systems via DHCP?
Make sure on your DNS server to add the private network reverse zones to avoid having those registration attempts from being forwarded/sent out.
10.0.0.0/8 255.0.0.0
172.16.0.0/10 255.192.0.0
192.168.0.0/16 255.255.0.0
That is the only possible destination to which password would propagate.
Which DNS update fails, the reverse host registration? Check the /etc/smb.conf to see to which interface it is bound/sending the DNS registration events?
You have to have DNS on your AD, do you have non AD based Name server listed on the server/clients?
I.e. are you pushing external DNS servers to the client systems via DHCP?
Make sure on your DNS server to add the private network reverse zones to avoid having those registration attempts from being forwarded/sent out.
10.0.0.0/8 255.0.0.0
172.16.0.0/10 255.192.0.0
192.168.0.0/16 255.255.0.0
ASKER
Already ihv prod envi with winAD and redhat serv register to it so am planning to do another staging envi ans am facing thia issue now before this i hv join 4 redhat swrvwra and it was joined smoothly
ASKER
any update
Do you manually create a computer account for the redhat systems you will belonging within the AD?
Are you using the GUI system-config-authenticati
Are you using the GUI system-config-authenticati
ASKER
no man am running script that include many thing required for linux to be joined to windows AD
Are you using system-config-authententic
Your response does not include which guide you are following and what your issues are.
Searching for "redhat 6 ad integration" returns guides to complete the process.
Are you trying to setup/configure a kickstart setup that will auto join a system into the ad upon install?
Your response does not include which guide you are following and what your issues are.
Searching for "redhat 6 ad integration" returns guides to complete the process.
Are you trying to setup/configure a kickstart setup that will auto join a system into the ad upon install?
ASKER
2-i hv already production windows AD and 12 redhat server joined to it but the issue with new ad created even i have joined 4 redhat server after 2two i faced this issue
3- am using both samba winbind and nswtich
so any clue for this issue.