IP Library Granted Patent US 8,045,486
Granted Patent B2
US 8,045,486 · App. 12/153,273 · Granted Oct 25, 2011

Discovery and visualization of active directory domain controllers in topological network maps

View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 8,045,486
App. No.
12/153,273
Granted
Oct 25, 2011
Kind
B2
Abstract

Active directory (AD) Domain Controllers (DC) discovery includes determining the topology of the network, such as the nodes and connections in the network. For example, synthetic data may be transferred within the network and traced to determine the presence and relationships of the various network components. Alternatively, other mapping techniques are based upon mapping a known set of nodes to determine the relationship of the nodes. Next, Lightweight Directory Access Protocol (LDAP) commands are forwarded to the various nodes to identify the AD DC within a range of IP addresses discovered during the mapping of to the topology of the network.

Claims (64)

1. A method for discovering an active directory (AD) domain controllers (DC) comprising:

mapping a topology of a network;

creating a lightweight directory access protocol (LDAP) connection by binding to a LDAP endpoint;

using LDAP commands to perform a LDAP data search for the AD DC using the created LDAP connection, and returning at least one fully qualified domain name (FQDN) of a discovered AD DC; and

unbinding from the LDAP endpoint,

wherein the mapping the topology of the network comprises searching for nodes in a pre-defined number of internet protocol (ip) addresses and repeating the search for a predefined number of hops.

2. The method of claim 1 , wherein the mapping a topology of a network comprises:

transferring synthetic data within the network; and tracing the synthetic data.

3. The method of claim 1 , wherein the mapping the topology of the network further comprises:

determining layer 2 and layer 3 connectivity from any discovered nodes;

correlating the layer 2 and layer 3 address data; and

determining network connectivity of discovered ip addresses.

4. The method of claim 1 , wherein the mapping of the topology of the network comprises receiving and storing user preferences comprising the size of the block of ip addresses and the number of hops.

5. The method of claim 1 , wherein the binding of the LDAP endpoint comprises creating a LDAP connection to a current LDAP endpoint.

6. The method of claim 1 , wherein the binding of the LDAP endpoint comprises creating a LDAP binding to a node associated with user-specified domain credentials.

7. The method of claim 1 , wherein the using of the LDAP commands to perform a search for the AD DC comprises:

performing a reverse-domain name server (DNS) lookup for each discovered AD DC to establish an ip address for the AD DC;

inserting, into a list, a discovered AD DC that has an ip address within network address ranges discovered in the mapping.

8. The method of claim 1 , wherein the returning of at least one FQDN comprises:

searching the FQDN of domain controllers in an organization unit; and

searching the FQDN of domain controllers in a cited specific configuration.

9. An apparatus for discovering an active directory (AD) domain controllers (DC), the apparatus comprising:

a server comprising a processor and memory,

the server configured to

map a topology of a network;

create a lightweight directory access protocol (LDAP) connection by binding to a LDAP endpoint;

use LDAP commands to perform a LDAP data search for the AD DC using the created LDAP connection, and to return at least one fully qualified domain name (FQDN) of a discovered AD DC; and

unbind from the LDAP endpoint,

wherein, when mapping the topology of the network, the server is further configured to search for nodes in a pre-defined number of ip addresses and repeat the search for a predefined number of hops.

10. The apparatus of claim 9 , wherein, when mapping the topology of the network, the server is configured to transfer synthetic data within the network, and trace the synthetic data.

11. The apparatus of claim 9 , wherein, when mapping the topology of the network, the server is further configured to:

determine layer 2 and layer 3 connectivity from any discovered nodes;

correlate the layer 2 and layer 3 address data; and

determine network connectivity of discovered IP addresses.

12. The apparatus of claim 9 , wherein, when mapping the topology of the network, the server is further configured to:

receive and store user preferences comprising the size of the block of ip addresses and the number of hops.

13. The apparatus of claim 9 , wherein, when binding the LDAP endpoint, the server is further configured to create a LDAP connection to a current LDAP endpoint.

14. The apparatus of claim 9 , wherein, when binding the LDAP endpoint, the server is further configured to create a LDAP binding to a node associated with user-specified domain credentials.

15. The apparatus of claim 9 , wherein, when using the LDAP commands to perform a search for the AD DC, the server is further configured to:

perform a reverse-domain name server (DNS) lookup for each discovered AD DC to establish an ip address for the AD DC;

insert, into a list, a discovered AD DC that has an ip address within network address ranges discovered in the mapping.

16. The apparatus of claim 15 , wherein, when returning at least one FQDN, the server is further configured to:

search the FQDN of domain controllers in an organization unit; and

search the FQDN of domain controllers in a cited specific configuration.

17. A computer program for discovering an active directory (AD) domain controllers (DC), embodied on a non-transitory computer-readable medium, the computer program configured to control a processor to perform operations, comprising:

mapping a topology of a network;

creating a lightweight directory access protocol (LDAP) connection by binding to a LDAP endpoint;

using LDAP commands to perform a LDAP data search for the AD DC using the created LDAP connection, and returning at least one fully qualified domain name (FQDN) of a discovered AD DC; and

unbinding from the LDAP endpoint,

wherein the mapping the topology of the network comprises searching for nodes in a pre-defined number of ip addresses and repeating the search for a predefined number of hops.

18. The computer program of claim 17 , wherein the mapping a topology of a network comprises: transferring synthetic data within the network; and tracing the synthetic data.

19. The computer program of claim 17 , wherein the mapping the topology of the network further comprises:

determining layer 2 and layer 3 connectivity from any discovered nodes;

correlating the layer 2 and layer 3 address data; and

determining network connectivity of discovered ip addresses.

20. The computer program of claim 17 , wherein the mapping of the topology of the network comprises receiving and storing user preferences comprising the size of the block of ip addresses and the number of hops.

21. The computer program of claim 17 , wherein the binding of the LDAP endpoint comprises creating a LDAP connection to a current LDAP endpoint.

22. The computer program of claim 17 , wherein the binding of the LDAP endpoint comprises creating a LDAP binding to a node associated with user-specified domain credentials.

23. The computer program of claim 17 , wherein the using of the LDAP commands to search for the AD DC comprising:

performing a reverse-domain name server (DNS) lookup for each discovered AD DC to establish an ip address for the AD DC;

inserting, into a list, a discovered ad dc that has an ip address within a network address ranges discovered in the mapping.

24. The computer program of claim 23 , wherein the returning of at least one FQDN comprises:

searching the FQDN of domain controllers in an organization unit; and

searching the FQDN of domain controllers in a cited specific configuration.

Assignments (13)
RELEASE OF FIRST LIEN SECURITY INTEREST IN PATENT COLLATERAL AT REEL 066489/FRAME 0356 Recorded Apr 17, 2025
From: JPMORGAN CHASE BANK, N.A., AS COLLATERAL AGENT
To: SOLARWINDS WORLDWIDE, LLC; CONFIO CORPORATION; AJAX ILLINOIS CORP.
Reel/Frame 070884/0776 →
FIRST LIEN PATENT SECURITY AGREEMENT Recorded Apr 17, 2025
From: SOLARWINDS WORLDWIDE, LLC
To: JPMORGAN CHASE BANK, N.A., AS COLLATERAL AGENT
Reel/Frame 070884/0832 →
SECOND LIEN PATENT SECURITY AGREEMENT Recorded Apr 17, 2025
From: SOLARWINDS WORLDWIDE, LLC
To: ALTER DOMUS (US) LLC, AS COLLATERAL AGENT
Reel/Frame 070884/0846 →
ASSIGNMENT OF FIRST LIEN SECURITY INTEREST IN PATENT COLLATERAL Recorded Feb 5, 2024
From: CREDIT SUISSE AG, NEW YORK BRANCH
To: JPMORGAN CHASE BANK, N.A.
Reel/Frame 066489/0356 →
ASSIGNMENT OF FIRST LIEN SECURITY INTEREST IN PATENT COLLATERAL Recorded Dec 27, 2022
From: CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH
To: CREDIT SUISSE AG, NEW YORK BRANCH
Reel/Frame 062228/0972 →
RELEASE OF SECURITY INTEREST Recorded Nov 1, 2018
From: WILMINGTON TRUST, NATIONAL ASSOCIATION
To: AJAX ILLINOIS CORP.; SOLARWINDS WORLDWIDE, LLC
Reel/Frame 047383/0693 →
SECURITY INTEREST Recorded Mar 20, 2018
From: AJAX ILLINOIS CORP.; SOLARWINDS WORLDWIDE, LLC
To: WILMINGTON TRUST, NATIONAL ASSOCIATION, AS COLLATERAL AGENT
Reel/Frame 045284/0502 →
FIRST LIEN PATENT SECURITY AGREEMENT Recorded Feb 5, 2016
From: SOLARWINDS WORLDWIDE, LLC
To: CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH, AS COLLATERAL AGENT
Reel/Frame 037701/0639 →
RELEASE OF SECURITY INTEREST Recorded Oct 19, 2015
From: WELLS FARGO CAPITAL FINANCE, LLC
To: SOLARWINDS WORLDWIDE, LLC; SOLARWINDS, INC.
Reel/Frame 036887/0113 →
SECURITY AGREEMENT Recorded Oct 14, 2011
From: WELLS FARGO CAPITAL FINANCE, LLC
To: SOLARWINDS WORLDWIDE, LLC AND SOLARWINDS, INC.
Reel/Frame 027065/0476 →
AFTER-ACQUIRED INTELLECTUAL PROPERTY SECURITY AGREEMENT (FIRST SUPPLEMENTAL FILING) Recorded Feb 8, 2010
From: SOLARWINDS WORLDWIDE, LLC
To: WELLS FARGO CAPITAL FINANCE, LLC, FORMERLY KNOWN AS WELLS FARGO FOOTHILL, LLC, AS COLLATERAL AGENT
Reel/Frame 023919/0975 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Dec 9, 2008
From: SOLARWINDS, INC.
To: SOLARWINDS WORLDWIDE LLC
Reel/Frame 021953/0420 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jul 15, 2008
From: SWAN, MICHAEL JON
To: SOLARWINDS, INC.
Reel/Frame 021280/0682 →