192.168.253.1
192.168.179.1
My domain controller disappears. Can not ping the electrical device. It resolves to one of the two ip address above. After removing adjectives reference, I regard as, and any reboot or hang around, the dns entries translate. I do not know why or what will rationale this to take place.
Answers:
Did you purely installed VMWare or Virtual PC? They will donate virtual NICs to the device.
Make sure surrounded by Network connections, after Advanced, Advanced Settings, the definite NIC is the first one within sequence within the chronicle from top to bottom, that determines the priority the NICs are getting.
Several factor to consider.
Are you routing correctly? How several domain controllers do you enjoy? If you cannot ping the piece of equipment, whats the error? If the DNS entries correct, what are the varying to? Is the other domain controller remote or local?
Need a LOT more info to troubleshoot this...
Is the DC pointing to itself beneath DNS??
Are you ever competent to ping the electrical device? If not, I suspect the problem may fib contained by your TCP/IP set up.
The combination of the IP address and subnet shroud determine how lots hosts and servers may exist on a framework and determines what selection may exist for valid TCP/IP address.
If the apparatus you are trying to ping is out of this allowed span, afterwards the two computers will not know how to see respectively other lacking the use of a router.
Without the subnet camouflage, I can not do the sums to determine the allowed TCP/IP address for the net. Without knowing the subnet mask involved, we can't investigate the TCP/IP address schematics to determine if this is the problem.
run the command prompt and type ipconfig /all and post the output spinal column here, this will report what NIC's are installed and furnish their complete IP information.
You own your DC set to acquire its IP using DHCP and the REGISTER CONNECTIONS ADDRESSES IN DNS checkbox is checked in the IP Protocol configuration for the connection(s) in quiz. This scheme that whenever the servers IP change, so do the DNS archives.automagically.
Consider that all domain controllers should enjoy statically assigned IP address to work properly, additionally, the dc should be pointing to itself for label resolution. This ability your dc's IP will also be your dc's primary DNS server. You should not specify a subsidiary DNS server unless the subsidiary DNS server is another dc running DNS.