-
Title
Exchange Information Stores fails to obtain Legacy DN. Attribute -
Description
During the Default Gathering Task you will see the following error in the Task logs:
Binding to the LDAP object to get the legacy DN attribute from a Mailbox.
Failed to get Legacy DN Attribute.
-
Cause
Firewall between MessageStats server and Domain Controller (Usually when there are multiple domains) -
Resolution
The way native Microsoft technologies (i.e. Explorer, Exchange System Manager, etc.) traverse Firewalls, would be similar to the way MessageStats would communicate.
Also confirm that the Firewall is allowing multiple ports to be open at a given time. Sometimes there are limits on firewalls to only allow a couple ports to be open at one time.
The following ports need to be opened to allow for dynamic RPC communication:
- Windows 2003 Ephemal Ports - TCP/UDP Ports 1024-5000
- Windows 2008 Ephemal Ports - TCP/UPD Ports 49152 - 65535
To access file shares to read and copy Message tracking logs the following Ports are required for SMB:
- Microsoft file sharing SMB: TCP/UDP 135-139
- Direct-hosted SMB traffic: TCP/UDP 445
Further Communication from MessageStats to retrieve Active Directory Information, and for name resolution the following ports will need to be open to the appropriate Servers:
- LDAP - AD Lookups: TCP/389
- Kerberos: TCP/UDP 88
- LDAP Global Catalog: TCP/3268
- DNS: TCP/UDP 53
- WINS: TCP/UDP 137
Ports required for Remote Powershell:
- Remote Powershell for Exchange - TCP Port 80 and access to the IIS /powershell virtual directory on your Exchange 2010 servers
- Remote Powershell for Lync - TCP Port 443 and access to the IIS /OcsPowershell virtual directory on your Lync Servers
Note: Host Headers defined in IIS can restrict access to IIS and any virtual directories.