Unable to view Exchange Properties of users via ADUC

I support a global exchange platform everything was working fine until two weeks ago. We have servers in two location to service our global setup. one in North America and another in Europe.Suddenly within the past two weeks when I try to view exchange properties of users from the servers in Europe I get the following error.
"The Operation Failed.
ID no 80004005
Microsoft Active Directory- Exahange Extensions.
The properties will eventually display but all Exchange Tabs will be gone. I can view the same account from the North American Server without issues. I have queried from DNS to FIrewall with no luck.
Any assistance will be appreciated.

jenkibabaSystem AdministratorAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

gurdeep1302Commented:
Hi,

Try the following steps:-

1.Check AD replication in North America and Eroupe DC's
2.Check if the DC in Europe is able to find / PING the FSMO role holder in the domain
3.Check the Schema role holder is up and running and is available in the network
4.Check if you are able to bind Schema over LDAP

Further if above does not work,please provide the following information:-

1.How many DC's are there in the forest
2.How many Domains,Child Domains and Trees you have in the Forest
3.Run the following command repadmin /syncall /Aed on the DC
4.Run dcdiag /v and let me know the results
5.What is the version of the Exchange server

Hope this helps !!!!
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
jenkibabaSystem AdministratorAuthor Commented:
It turns out there was a firewall change that casued communication between the Exchange Server and the Global Catalog server.
0
jenkibabaSystem AdministratorAuthor Commented:
I've requested that this question be closed as follows:

Accepted answer: 0 points for jenkibaba's comment #a37482117

for the following reason:

Because it's the right solution if it was not for the change that was done within my network
0
jenkibabaSystem AdministratorAuthor Commented:
There was a change done within the network that was the cause of this problem
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Exchange

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.