Displaying 3 results from an estimated 3 matches for "dc2022".
Did you mean:
dc202
2024 Dec 20
1
Problem after join Windows Serwer 2022 DC to Samba AD
...new one. However, when I query using the command:
>> Get-ADDomainController -Filter * | Select-Object Name, HostName, I
>> don?t see the new controller.
> What does 'samba-tool computer show $DC_HOSTNAME
> --attributes=name,dNSHostName' display ?
# samba-tool computer show DC2022 --attributes=name,dNSHostName
dn: CN=DC2022,OU=Domain Controllers,DC=wenus,DC=local
name: DC2022
dNSHostName: dc2022.wenus.local
>
>> I also noticed that the SPN DNS/dc2022.wenus.local for the new DC
>> hasn?t been created.
> I wouldn't worry about that. none of my DCs have th...
2024 Dec 20
1
Problem after join Windows Serwer 2022 DC to Samba AD
...ew one. However, when I query using the command:
> Get-ADDomainController -Filter * | Select-Object Name, HostName, I
> don?t see the new controller.
What does 'samba-tool computer show $DC_HOSTNAME
--attributes=name,dNSHostName' display ?
>
> I also noticed that the SPN DNS/dc2022.wenus.local for the new DC
> hasn?t been created.
I wouldn't worry about that. none of my DCs have that SPN
Rowland
2024 Dec 20
1
Problem after join Windows Serwer 2022 DC to Samba AD
...orrectly. When I check with the
command: nslookup -type=SRV _ldap._tcp.wenus.local, it shows all DCs,
including the new one. However, when I query using the command:
Get-ADDomainController -Filter * | Select-Object Name, HostName, I don?t
see the new controller.
I also noticed that the SPN DNS/dc2022.wenus.local for the new DC hasn?t
been created.
I checked the replication, and it doesn?t show any errors.
Do you have any idea what might be the cause?