Additional AD Issue
-
-
Is your DNS setup correctly on that new server? DNS has to point to an AD DNS server so it can find the needed records. If you're using something like 8.8.8.8 or your ISPs DNS then it will fail.
-
Almost certainly DNS. Can you ping the server(s)?
-
@scottalanmiller said in Additional AD Issue:
Almost certainly DNS. Can you ping the server(s)?
Pinging isn't 100% reliable way to know DNS is setup correctly - Windows will use other methods to find each other, then move over to IP to complete the ping.
-
@Dashrender said in Additional AD Issue:
@scottalanmiller said in Additional AD Issue:
Almost certainly DNS. Can you ping the server(s)?
Pinging isn't 100% reliable way to know DNS is setup correctly - Windows will use other methods to find each other, then move over to IP to complete the ping.
No, but we need to know if it is pingable at all.
-
NO issue with dns, but if we join in domain the dns record is not created in forward lookup we are creating manually.
pinging was successful no problem with that @scottalanmiller @Dashrender
-
Oh. It is joining okay just not making a record? There is a checkbox for that.
-
@scottalanmiller said in Additional AD Issue:
Oh. It is joining okay just not making a record? There is a checkbox for that.
what kind of checkbox you are asking for
-
unable to telnet port like 88, 389, 3268, 3269, 464 (from ad old to adc new)
unable to telnet port like 88 (from adc new to ad old )
-
@RoopanKumar said in Additional AD Issue:
unable to telnet port like 88, 389, 3268, 3269, 464 (from ad old to adc new)
unable to telnet port like 88 (from adc new to ad old )
Why are you trying to telnet?
-
What is the IP address of your current AD server?
What is the IP address of your DNS server? Do you have more than one DNS server?
What is the IP address of the server you are trying to install AD onto? -
@Dashrender this is for my team mate ask this boy @Ghani
-
Yes, we are using telnet to establish session from new windows server OS to existing Domain controller. The ports [ 389,3268,3269,464,53] are establised session, except port 88. And then , we using telnet to establish session from
existing domain controller to new windows server OS that time , the ports [ 389,3268,3269,464,88] are not established session in between existing DC and windows server. Only 53 and 445 ports are establish the session. But i am using netstat -n commands on existing DC. 389,3268,3269,464,53,88 ports are open.Thanks
Ghani -
@Dashrender said in Additional AD Issue:
What is the IP address of your current AD server?
What is the IP address of your DNS server? Do you have more than one DNS server?
What is the IP address of the server you are trying to install AD onto?@Ghani what are the answers to these questions?
-
@Dashrender said in Additional AD Issue:
@RoopanKumar said in Additional AD Issue:
unable to telnet port like 88, 389, 3268, 3269, 464 (from ad old to adc new)
unable to telnet port like 88 (from adc new to ad old )
Why are you trying to telnet?
That's how you test ports
-
@scottalanmiller yeah is there any other option to check ports
-
@scottalanmiller said in Additional AD Issue:
@Dashrender said in Additional AD Issue:
@RoopanKumar said in Additional AD Issue:
unable to telnet port like 88, 389, 3268, 3269, 464 (from ad old to adc new)
unable to telnet port like 88 (from adc new to ad old )
Why are you trying to telnet?
That's how you test ports
Yeah OK.. what do these ports have to do with the OP issue?
-
192.168.1.124 of AD server
192.168.1.124 of DNS server [ Note : Only on DNS server ].
192.168.1.125 { it is ip address of new AD server ]Thanks
-
OP means ?
-
