new users can't access email

  • Thread starter Thread starter Andy
  • Start date Start date
A

Andy

I'm running Exchange 2K in a Win2K server environment.
One exchange server one domain everything in native mode.
If I create a new user with an exchange account in AD,
everything appears to be OK, except the user can't open
Outlook to see email. The user gets the error
message "Unable to open your default email folders. The
MSFT Exchange server computer is not available ...." When
I look at the Exchange props in AD everything looks good.
The email addresses are created using the policy that's in
place. One test I tried was copying my user account to
create a new account and then the user was able to open
their email. Also, when I'm configuring Outlook and I'm
logged into Windows with the new user account, Outlook
resolves the name in the props when you click "check name"
yet it still gives the error message "Unable to open your
default email folders...." Any ideas?
 
Andy,

I bet that it works now! Sometimes it can take up to two hours for the
newly created users to be able to access their 'mailbox'. And that is
assuming that you have only one Site. Throw in multiple Sites and that time
can increase.

If it is working now - about 24 hours later - I would check everything
anyway just to make sure that we are not overlooking / ignoring a problem.
I would suggest that you install the Support Tools ( which can be found on
the WIN2000 Server CD as well as on the WIN2000 Service Pack CD in the
Support | Tools folder ) on all of your WIN2000 Servers ( yes, all of them -
Domain Controller, member Server, whatever! ) and run a dcdiag /c /v on the
Domain Controllers and a netdiag /v on all of the WIN2000 Servers. This
will give you an excellent overview of what is going on.

Furthermore, I would use a couple of the tools found in the Support Tool -
namely repadmin, replmon and netdom - to make sure that all of the FSMO
Roles are known, available and bindable ( did I just make up a word? ).

Specific to your problem - if it still is a problem - I would check to make
sure that the Global Catalog(s) is(are) available.

HTH,

Cary
 
Sorry...left off something.

Using repadmin and replmon to make sure that all is good with the AD
replication is what I meant. You can use both replmon and netdom to make
sure that all of the FSMO Roles are 'findable' and 'bindable'.

Cary
 
Back
Top