Comment savoir si je me trouve sur un contrôleur de domaine Active Directory (DC)

Différente façon de savoir si on se trouve sur une machine qui est Contrôleur de Domaine  (DC) Active Directory:

En ligne de commande:

#systeminfo |findstr /i "domain"
Configuration du système d'exploitation:Contrôleur principal de domain
Domaine:                                domain.com
#dsquery server
"CN=ROOTDC1,CN=Servers,CN=SiteTest1,CN=Sites,CN=Configuration,DC=...
"CN=ROOTDC2,CN=Servers,CN=SiteTest2,CN=Sites,CN=Configuration,DC=...
#netdom query dc
List of domain controllers with accounts in the domain:
ROOTDC1
ROOTDC2
#netstat -an | findstr /i "écoute" ou "listening"
et vérifier les ports 389, 636, (3268, 3269) ces deux derniers
sont pour les GC (Catalogue global)

regardez sur le site pour les ports réseaux utilisés  http://support.microsoft.com/kb/832017

#net share |find "sysvol"
NETLOGON     C:\WINDOWS\SYSVOL\sysvol\domain.com\SCRIPTS
SYSVOL       C:\WINDOWS\SYSVOL\sysvol     Partage de serveur d'accès

Liste des ports utilisés par Microsoft

Port Microsoft

When you look at an installation of Windows (especially server-versions of Windows), you will find a number of ports open. Several of these are well-known ports, while others are dynamically assigned.The dynamically assigned ports start at port 1024 and usually range up through roughly port 1100. The exact meaning of these can be obtained through the « endpoint mapper » at port135.

Basic Windows ports

135 The « end-point mapper ». RPC services are assigned other ports dynamically. When trying to connect to a service, you go throug this mapper to discover where it is located. The process works the same as on the UNIX RPC portmapper. A big difference is that a lot of services run on top of named pipes, which don’t have a specific port.
137 NetBIOS name service. This is how NetBIOS-based services find each other. On a NetBIOS network, these names uniquely identify the machine and services running on the machine (and the IP address doesn’t matter). Machines find each other either using broadcasts or looking them up in a centralized NetBIOS naming server (called a WINS server).
138 NetBIOS datagram service. This is primarily used for broadcasting information. It is primarily used by the SMB browser service that fills the information within the « Network Neighborhood » icon.

Basic Services

This section describes the ports that you would encounter when installing the basic services on WinNT Server. Note that virtually all Microsoft services require port 135 for remote administration.

42 For WINS replication. Remember that normal access to the WINS service is through port 137; this port is used for database replication.
1723 PPTP (Microsoft’s VPN solution). Note that this will also use IP protocol 47.
138 NetBIOS datagram service. This is primarily used for broadcasting information. It is primarily used by the SMB browser service that fills the information within the « Network Neighborhood » icon.

Exchange Server

This section describes the type of ports you might see in Micorosft’s Exchange server. This is a huge e-mail server package.

Again note the heavy reliance upon port 135 for remote administration and RPC communication between server components.

102 X.400 MTA
110 POP3
119 NNTP
143 IMAP4
389 LDAP
563 POP3 over SSL.
636 LDAP over SSL.
993 IMAP4 over SSL.
995 POP3 over SSL.

NetMeeting

Microsoft’s NetMeeting is video-conferencing style software.

389 Internet Locator Server (ILS) using LDAP.
522 ULP (User Location Server), obsoleted by LDAP. ULP is only used by older version of NetMeeting.
636 Secure LDAP over SSL
1503 T.120 teleconferencing protocol
1720 H.323 call setup
1731 Audio call control protocol
Dynamically assigned ports for call control and RTP transport of the data.

Windows Media

The Windows Media Server streams content over the web. This was formerly known as « NetShow » and uses the .asf file extension.

80 Can stream content over HTTP.
1755 Uses a TCP control connection on this port, as well as some UDP traffic.
7007 Encoder-to-server traffic. This allows an encoder (such as a system encoding live radio) to stream content to the server, which then streams it out to clients.

Note that the UDP traffic may be carried over IP multicast.

Terminal Server

Microsoft’s Terminal Server is a special version of WinNT Server that allows remote GUI access. It is essentially Microsoft’s version of X Windows, but since the Win32 API isn’t geared toward remote viewing, its bandwith requirements are higher. Clients are available for WinCE devices allow NC-style access.

3389 RDP client
1494 Citrix (ICA) client
636 Secure LDAP over SSL
1503 T.120 teleconferencing protocol
1720 H.323 call setup
1731 Audio call control
Dynamically assigned ports for call control and RTP transport of the data.

Cluster Server

Clustering is where multiple servers coordindate themselves into providing the same service so that if any server goes down, clients get uninterupted operation.

1717 Convoy
2504 WLBS

Other

 

593 Encapsulates the RPC ‘end-point mapping’ services within HTTP.
1477 MS SNA server
1478 MS SNA server

Source : http://www.iss.net/security_center/advice/Exploits/Ports/groups/Microsoft/default.htm

 

A voir aussi -> http://support.microsoft.com/kb/832017