Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Exchange 2003 new install problem

Status
Not open for further replies.

RoamZone

IS-IT--Management
Dec 2, 2003
18
US
I've got a brand new machine that I have put a fresh install of Windows 2003
Server with all the updates. It has 1Gig of Ram, RAID drives, and 1.6GHz
processor. I have no special or advanced settings. I've gone through the
"Manage Your Server" steps of setting up and activating the "File Server,
Application Server, Mail Server, VPN Server, Domain Controller, and DNS
Server". Again no special or advanced settings. So far I've tested what I
can and all the aspects of the OS and features work as they should. I had
an issue adding users to Active Directory but it was a user password
permissions issue that needed set. Now it works.

I then installed Exchange 2003 Standard as instructed by the CD's on screen
checkbox steps. I've done the DNS configuring, ForestPrep, DomainPrep, and
then the actual Setup, all without errors or speed bumps. I'm logged is as
Administrator with all permissions and rights that the instructions specify.

The Problem: When I open the "Exchange 5.5 Administrator" program that it
installed it can't find an Exchange Server. Specifically, I click the
Browse button in the "Connect to Server" window and it gives me the
following message. "The list of Microsoft Exchange Server computers is not
available because no Microsoft Exchange Server computer could be located.
Microsoft Exchange Administrator, ID no: c10312c8". If I type in the name
of the server (which is Exchange) in the field and click OK it gives me the
following message. "A connection could not be made to the Microsoft
Exchange Server computer 'EXCHANGE'. The Microsoft Exchange Server computer
does not respond. Microsoft Exchange Directory, ID no:
DS_E_COMMUNICATIONS_PROBLEM"

When I open the "Active Directory Users and Computers" list the server shows
up under the "Domain Controllers" folder. When I open the "Exchange System
Manager" there is NO server or machine listed anywhere. The only folders
listed are "Global Settings, Recipients, Administrative Groups, and Tools".

Please help. I've got a seperate Exchange Server on a seperate domain that
I wish to keep totally seperate from this new one. My point is that I'm
somewhat familiar with what is supposed to happen here, it's just not
happening.
 
Did you ever find out what is causing this? I've scoured the web and can't find much about this particular problem. Any help would be greatly appreciated.

TIA - Rob
 
First, let's look at how the 5.5 admin tool locates an exchange server. When you click "Browse", EA retrieves the browse list from the master browser. If the PDCE is on the same subnet, then this would be the PDC Emulator [I'm omitting WINS to simplify]. EA is looking for the netbios suffix of 24, which identifies the Exchange 5.5 Directory service. If it can't retrieve the browse list, or there are no entries in the list with a netbios suffix of 24, then the list is empty. In that there are no 5.5 servers in the org or domain, this is expected.

Next, you typed in the name of the E2K server. EA attempts to connect to the 5.5 directory service, which does not exist on the E2k server. This results in the DS_E_COMMUNICATIONS_PROBLEM error. E2K does not have a 5.5 directory service to connect to, unless it is running the SRS. You only get the SRS if you installed the E2K server into a 5.5 org. In that this is a new org only containging a single E2K server, this is expected.

In Exchange System Manager, all you see is "Global Settings, Recipients, Administrative Groups, and Tools". If you expand Administrative Groups, you should see the name of your administrative group. Expand that, and you should see "servers". Expand servers, and you should see your E2K server.



 
Yes I resolved it. I ended up calling the Microsoft Tech Support at $250 per incedent and found out that the DNS Server setup of the OS wasn't setup the way that Exchange requires.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top