VirtualBox

Opened 10 years ago

Closed 10 years ago

#14016 closed defect (invalid)

Windows Active Directory access not working with active NAT

Reported by: Resu Owned by:
Component: other Version: VirtualBox 4.3.26
Keywords: Cc:
Guest type: Windows Host type: Windows

Description

When I have two network connections (internal network for active directory access and registered DNS and a NAT card) I'm not able to access the active directory.

The domain controller is running on a separate machine and my windows client machine, that has joined the domain network, can access the domain only when i deactivate the NAT network card.

Running a ping with active NAT it can resolve the domain controller, but pings the internal IP like 127.0.0.X. When a deactivate the NAT network card, the ping returns the correct IP from the internal network like 192.168.0.X.

Attachments (5)

networkConfigDomainController.png (67.4 KB ) - added by Resu 10 years ago.
networkConfigClient.png (74.4 KB ) - added by Resu 10 years ago.
hostOnlyNetworkDetails.png (18.6 KB ) - added by Resu 10 years ago.
(not relevant in my eyes)
pingComparison.png (12.7 KB ) - added by Resu 10 years ago.
clientInternalNetworkTCPIPconfig.png (14.8 KB ) - added by Resu 10 years ago.

Download all attachments as: .zip

Change History (8)

comment:1 by Valery Ushakov, 10 years ago

Please, can you provide exact network configuration/topology, exact commands, their output etc. Unfortunately it's not clear from your description what is that you are trying to do.

by Resu, 10 years ago

Attachment: networkConfigClient.png added

by Resu, 10 years ago

Attachment: hostOnlyNetworkDetails.png added

(not relevant in my eyes)

by Resu, 10 years ago

Attachment: pingComparison.png added

comment:2 by Resu, 10 years ago

I've attached some files with my network configuration. The pingComparison file shows the difference when accessing the domain controller from the client. Before release v4.3.20 everything worked fine, but till this release i have the problem (currently installed version: 4.3.26).

comment:3 by Valery Ushakov, 10 years ago

Resolution: invalid
Status: newclosed

There's a name collision that is indicated to you by 127.0.53.53. When client has NAT network up, it probably has access to another resolver or something. Anyway, the problems is with your network configuration, not with VirtualBox.

Note: See TracTickets for help on using tickets.

© 2025 Oracle Support Privacy / Do Not Sell My Info Terms of Use Trademark Policy Automated Access Etiquette