Quantcast
Channel: Exchange Server 2010 forum
Viewing all articles
Browse latest Browse all 19214

Communication servers with Exchange 2010 ExBPA DC with FSMO alert

$
0
0
Higood morning, I have anExchange 2010infrastructurePS2RU5v2onWindowsServer 2008R2 SP1,

Myenvironmentis 2AD Sites,themainSite, where are theDCswithall FSMO rolesdomainandthe remote site, where all themail serversand twoDCsthatareGConly.

TheExchangeserver hosthave nocommunication withDCsthat have the FSMO,but if they havecommunication withGCsthat are onyoursite.

When I passtheExBPA, I getthese errors:


DomainNamingMasterfailed to respond
Can notcontacttheserver actingasthe DomainNamingMasteron port389.Check ThatActive Directoryserver
xxxxxxxxxxxxisFunctioningCorrectly.Error code: 389Not Available.

PDCEmulatorfailed to respondDomain:yyyyyyyy
Can notcontacttheserver actingasthePDCEmulatorfor domainyyyyon port389. Check ThatActive
FunctioningCorrectlyxxxxxxxxxxxis Directoryserver.Error code: 389Not Available.


RIDMasterfailed to respondDomain:yyyy
Can notcontacttheserver actingastheRIDMasterfor domainyyyyyon port389.Check ThatActiveDirectory
xxxxxxxxxxxxisFunctioningCorrectlyserver.Error code: 389 Not Available.


SchemaMasterfailed to respond
Can notcontacttheserver actingastheSchemaMasteron port389.Check ThatActive Directoryserver
xxxxxxxxxxxxxisFunctioningCorrectly.Error code: 389Not Available.


InfrastructureMasterfailed to respond Domain:yyyyy
Can notcontacttheserver actingastheInfrastructure Masterfor domain'yyyyy' onport389.Check ThatActive
DirectoryserverisFunctioningCorrectlyxxxxxxxxxxxxxx.Error code: 389Not Available


Everythingseems to work fine,but my question isifIignorethis error andI have tomake theexchange serversto communicatedirectly withDCsthathaveFSMO roles


Thank you very muchfor your help

Microsoft Certified IT Professional Server Administrator



Viewing all articles
Browse latest Browse all 19214

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>