Solved

Active Directory problem on running data collection

Posted on 2004-09-20
8
311 Views
Last Modified: 2010-08-05
I am installing a Exchange 2003 server and trying to connected it to an existing 5.5 server. In the Active directory connector screen, when trying to run STEP 2 data collection I get the following error

Server <MAILSERVER> :389 is not an Exchange 5.5 server or an SRS service.
Data Collection stopped. Check the ADCTools.log file for the cause. Then repeat Step 2.
0
Comment
Question by:bateman2413
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
8 Comments
 

Author Comment

by:bateman2413
ID: 12103289
When I look at the ADCTOOLS.LOG  I see the following

Pass 1 of 4: Resource Mailbox Scan 09/20/2004 11:39:31
      Server mailserver name :389 is not an Exchange 5.5 server or an SRS service.
0
 
LVL 2

Expert Comment

by:fitcher
ID: 12103359
Maybe a dumb question but,

Is LDAP enabled on the 5.5 server is it set to use port 389? Have you run the domain prep and forest prep?
0
 

Author Comment

by:bateman2413
ID: 12103604
I ran forest prep and domain prep. How would someone enable LDAP on a exchange 5.5 site running Windows 2000 server?
0
Does Powershell have you tied up in knots?

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

 

Expert Comment

by:g_2000
ID: 12105509
Hi,
Is there a program on your computer that  behaving a virus like activity........mey be run anti-virus sofwares..........Thanks
0
 

Author Comment

by:bateman2413
ID: 12105533
well I believe that I had to choose create new organization when installing instead of join existing...  trying that now...
0
 

Author Comment

by:bateman2413
ID: 12237329
I had to resort to calling MicroSoft to walk me through the full Installation of Exchange 2003. The problem was I need to change the port to another port cause something else was using port 389.
0
 

Accepted Solution

by:
ee_ai_construct earned 0 total points
ID: 12526955
Question answered by asker or dialog valuable.
Closed, 500 points refunded.
ee_ai_construct (replacement part #xm34)
Community Support Admin
0

Featured Post

Free NetCrunch network monitor licenses!

Only on Experts-Exchange: Sign-up for a free-trial and we'll send you your permanent license!

Here is what you get: 30 Nodes | Unlimited Sensors | No Time Restrictions | Absolutely FREE!

Act now. This offer ends July 14, 2017.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Recently, Microsoft released a best-practice guide for securing Active Directory. It's a whopping 300+ pages long. Those of us tasked with securing our company’s databases and systems would, ideally, have time to devote to learning the ins and outs…
This article is a collection of issues that people face from time to time and possible solutions to those issues. I hope you enjoy reading it.
This Micro Tutorial hows how you can integrate  Mac OSX to a Windows Active Directory Domain. Apple has made it easy to allow users to bind their macs to a windows domain with relative ease. The following video show how to bind OSX Mavericks to …
Monitoring a network: why having a policy is the best policy? Michael Kulchisky, MCSE, MCSA, MCP, VTSP, VSP, CCSP outlines the enormous benefits of having a policy-based approach when monitoring medium and large networks. Software utilized in this v…

690 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question