have installed Exchange Server 2003 on a dedicated Windows 2003 server connected to the domain. I have run all the preperation for the forest etc and all was sucessful.can some one plese help me

How to open the LDAP port on the DC/GC That the exchange server will be able to connet to the dc/gb with ldap?
c_mottiAsked:
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.

isaman07Commented:
The Ldap poer is open by default, unless if you want to use SSL.
0
bnditCommented:
Hi c_motti,

Could you elaborate more on your question please? Are you trying to change service ports? Is your Exchange not working? Are your store databases mounted? I'm not quite sure as to what the problem is exactly. Isaman07 is correct, LDAP ports are open by default when you're done installing Exchange 2003. Here's a list of the LDAP ports used by Exchange:

LDAP
 TCP/UPD: 389
 Lightweight directory access protocol (LDAP) used by Microsoft Active Directory® directory service, Active Directory Connector, and the Microsoft Exchange Server 5.5 directory use this port.
 
LDAP/SSL
 TCP/UDP: 636
 LDAP over Secure Sockets Layer (SSL) uses this port.
 
LDAP
 TCP/UDP: 379
 The Site Replication Service (SRS) uses this port.
 
LDAP
 TCP/UDP: 390
 This is the recommended alternate port to configure the Exchange Server 5.5 LDAP protocol when Exchange Server 5.5 is running on an Active Directory domain controller.
 
LDAP
 TCP: 3268
 Global catalog. The Windows 2000 and Windows Server 2003 Active Directory global catalog (a domain controller "role") listens on TCP port 3268.
 
0
c_mottiAuthor Commented:
Hi All I fixed the problem by removing the ISP DNS Ip number from the secoundey DNS server on the exchange server that solve my problem for event "Event ID 8026"
thank you all
0
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

c_mottiAuthor Commented:
Hi All I fixed the problem by removing the ISP DNS Ip number from the secoundey DNS server on the exchange server that solve my problem for event "Event ID 8026"
thank you all.
0
c_mottiAuthor Commented:
Hi All I fixed the problem by removing the ISP DNS Ip number from the secoundey DNS server on the exchange server that solve my problem for event "Event ID 8026"
thank you all
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
Vee_ModCommented:
Closed, 500 points refunded.
Vee_Mod
Community Support Moderator
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.