I
I
ITF2019-07-04 07:00:44
Computer networks
ITF, 2019-07-04 07:00:44

Why does the virtual machine not see AD?

There is a physical server (Server-AD) with 2 interfaces, DHCP, DNS, AD are deployed on it.
I registered with statics:
192.168.1.2
225.255.255.0
Gate 192.168.1.1
DNS 127.0.0.1
The Hyper-V (Server-N) virtual machine was also raised on it.
The virtual machine receives static:
192.168.1.3
255.255.255.0
Gate 192.168.1.1
DNS 192.169.1.2 The
second interface is used, and I issue static to the Hyper-V virtual switch:
192.168.1.4
225.255.255.0
Gate
192.168.1.1
As a result, ping 192.168.1.1 the virtual machine of the AD-server by name (Server-AD) went on IP 192.168.1.4
Turned off the switch, ping went to 192.168.1.2. Those. I see the car.
But I don’t understand how to see now exactly the domain server by the NetBIOS name in order to bring the virtual machine into the domain.
Because by the given name (AD) and by the full domain name (AD.companyname.ru) pings do not pass at all

Answer the question

In order to leave comments, you need to log in

3 answer(s)
I
ITF, 2019-07-04
@ITF

Honestly, I don't know what happened.
The only changes I made after installing the DNS server and AD were changing the IP address. Certainly in a direct zone all records with IP changed. The server just rebooted.
I was tormented, poked, looked at the settings, ran diagnostics ...
I turned off the virtual switch.
Nothing actually helped.
Now I go to the virtual machine - I ping AD over NetBios again - and it all worked.

A
Armenian Radio, 2019-07-04
@gbg

You have two interfaces stuck in the same network 192.168.1.0/24. Fix it.

V
Vladimir Kuzin, 2019-07-04
@Bobson8

What address is your DNS listening to?
Try changing the dns from 127.0.0.1 to 192.168.1.2 in the AD server settings

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question