Additional AD Issue
-
@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 ?
-
-
@Ghani said in Additional AD 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
what kind of switch is in use? are both servers plugged into the same switch?
-
Is the first AD server a VM? is this new desired AD server a VM? you might have posted already, but I'm tired, and not back reading
-
Yes . new AD is a virtual machine running on VMware hypervisor.
-
@Ghani said in Additional AD Issue:
Yes . new AD is a virtual machine running on VMware hypervisor.
What version? Is there a firewall inside ESXi? and network level blocking going on?
-
Existing AD running on physical server. New Additional domain controller machine running on virtual machine.
-
how to check any firewall or network level block on VMware hypervison ?
-
VMware Hypervisor version 6.0 update 2
-
can you ping the original AD from the VM by FQDN? (fully qualified domain name)
-
I facing error screen shot attached here
kindly provide any solution for creating Additional domain controller.
-
Yes i could pinging the FQDN name.
-
did you do as it said and remove this server from the domain, reboot, and readd it?
-
yaa i checked
-
I got event error from new Additional DC
-
Please show pictures of your IP settings on both the original AD and the new VM.
-
This error is sounding like you have DNS installed on the new AD server already, but that it's misconfigured. Open the DNS applet and do what this error says, check to see if DNS is running on the IP address that is currently assigned to the server. Perhaps the server came online and got a DHCP address, they you installed DNS, so it tied to that IP, then you set IP to a manual setting which is different from the selected one in DNS. This does seem weird that this would happen, but hey, stranger things, eh?
https://i.imgur.com/0JX0bcT.png
Check your DNS manager settings on both servers
https://i.imgur.com/KlphvDp.pngAlso, This error message leads me to think that this new AD box might be pointing to itself for DNS, instead of pointing to the other AD server for DNS.
Please post pictures of the IP settings on both servers.
-
OK , i will check it
