Ping gives the wrong IPv4 address

Filippo 21 Reputation points
2022-02-01T15:43:30.267+00:00

Hi. I am studying Active directory. I created a virtual lab to experiment for the couse I am studying.
I am using Oracle VM 6.1 and I created 2 virtual machine. One where I installed Windows server 2019 and one wher eI installed Windows7 (my laptop cannot run anything bigger than that).
In each VM I created 2 network adapters, the first is attached to "internal network" on and the second to a "bridged adapter"
I then set the ip of the win2019 VM to 192.168.100.10 and the one for the Win7 machine to 192.168.100.50, both from the network configuration of the OSs.
I then activated the DNS service on the Win2019 and used 192.168.100.10 as DNS in the Win7 network configuration.
When I ping -4 server1 ( the anme I gave o the Win2019VM) from cmd in Windows7 I get as ip 192.168.100.31.
If I deactivate the bridged network adapters in both machines, I get the expected one, 192.168.100.10
If I reactivate the adapters, I get 192.168.100.31 again.
Seems WIN2019 gets the internal network adapter as second ethernet adapter.

From what I see on the course I am studing it is expected to have 192.168.100.10 as result of ping -4 server1 with both networks adapters active.

Am I doing something wrong? Happy to provide more details if needed.
I am almost new to networking so please be patient if it is a stupid question. I checked the forum, but seems none posted this question here

Windows for business | Windows Server | User experience | Other
0 comments No comments
{count} votes

Accepted answer
  1. Anonymous
    2022-02-01T16:56:41.357+00:00

    The domain controller should have only a single network adapter. Some general info. Domain controller and all members must use domain DNS only so members can find and logon to domain. Internet queries are passed on to the default 13 root hint servers in a top-level down fashion or optionally to forwarders.

    --please don't forget to upvote and Accept as answer if the reply is helpful--

    170282-image.png

    170150-image.png

    1 person found this answer helpful.
    0 comments No comments

3 additional answers

Sort by: Most helpful
  1. Anonymous
    2022-02-01T16:09:44.077+00:00

    Multi-homing a domain controller will always cause no end to grief for active directory DNS.

    --please don't forget to upvote and Accept as answer if the reply is helpful--


  2. Anonymous
    2022-02-01T16:39:15.633+00:00

    In other words?

    Do not multi-home a domain controller.

    --please don't forget to upvote and Accept as answer if the reply is helpful--


  3. Filippo 21 Reputation points
    2022-02-01T16:52:58.76+00:00

    DSPatrick, I appreciate you may not have much time for newbies questions, but his way I am not learning anything and it is what I would like to do. If you have time, cna you be more specific?
    For what I undestood, having two network interfaces in the VM that runs win2019 creates a lot of issues and I should remove one. In case, since the win2019 machine should also work as DNS server, would be better to remove the bridged connection or the internal one?
    IS there any thing I can do to fix it in some other way?
    Any detalis or information you could give me would be really appreciated,as it will teach me something. My networking skills ar quite low and I never worked specifically with servers .
    Thanks!

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.