Did you ever create a Recovery Storage Group in Exchange?  It's possible
that the new mailboxes are getting created there, instead of in the regular
mailbox store.  Deleting the recovery storage group is the fix.

I've never done this personally, but I think that I would delete the
mailboxes from the users in AD first.  Then delete the recovery storage
group, then go back in and recreate the mailboxes.

Hello,

Thanks for posting in our newsgroup.

From your description, I know that the new user account cannot access
Outlook and get message: "The name could not be matched to a name in the
address list.". If I am off-base, please don't hesitate to let me know.

Based on my research on this issue, I'd like to give you the following
suggestions:

Step 1: The Problem may be caused by corrupt Recipient Update Services.
Please recreate it and try again.

1. Open ESM.
2. Expand Recipients->Recipient Update Services
3. Right-click each entry of Recipient Update Service in the right pane,
and then click Rebuild.

Step 2: The permissions on the exchange server may be modified. Please
ensure the correct permissions to the authenticated users in the exchange
server. Please follow the following steps in KB 322832 to have a check:

"The Name Could Not Be Resolved" Error Message When You Add Additional
Mailboxes to Your Outlook Profile
http://support.microsoft.com/kb/322832

Step 3: Please follow article 297801 to verify that the user account has
been stamped by the Recipient Update Service after you mailbox-enable the
user account. And then verify that the following attributes have been
populated to the account:

showInAddressBook ()
textEncodedORAddress
msExchUserAccountControl
msExchALObjectVersion
msExchUserAccountControl
msExchPoliciesIncluded

More info:

Troubleshooting Check Name errors
http://support.microsoft.com/kb/297801

Step 4: Please install the latest Exchange hotfix and Service Packs.

Users do not appear in the Global Address List, users cannot connect to
their Exchange mailboxes, event ID 8331 is logged, and e-mail names cannot
be resolved in Exchange Server 2003
http://support.microsoft.com/kb/837444

How to obtain the latest service packs for Exchange Server 2003
http://support.microsoft.com/kb/836993/

If the problem persists, please help me collect the following information
for further research:

MPS Report on SBS server

1.Visit
http://download.microsoft.com/download/b/b/1/bb139fcb-4aac-4fe5-a579-30b0bd9
15706/MPSRPT_Exchange.EXE to download the file.

2. Run the MPSRPT_Exchange.EXE on the server box.

3. Wait for 10~15 minutes.

4. Open Windows explorer, navigate to %SYSTEMROOT%\MPSReports\Exchange\cab\

5. Send the .cab file directly to  v-robeli@microsoft.com with subject:
40037315-Created a new mailbox but can't access it via Outlook or OWA.

I am looking forward to hear from you.

If you need further assistance, please don't hesitate to let me know.

Best regards,

Robert Li(MSFT)

Microsoft CSS Online Newsgroup Support

Get Secure! - www.microsoft.com/security

=====================================================

This newsgroup only focuses on SBS technical issues. If you have issues
regarding other Microsoft products, you'd better post in the corresponding
newsgroups so that they can be resolved in an efficient and timely manner.
You can locate the newsgroup here:
http://www.microsoft.com/communities/newsgroups/en-us/default.aspx

When opening a new thread via the web interface, we recommend you check the
"Notify me of replies" box to receive e-mail notifications when there are
any updates in your thread. When responding to posts via your newsreader,
please "Reply to Group" so that others may learn and benefit from your
issue.

Microsoft engineers can only focus on one issue per thread. Although we
provide other information for your reference, we recommend you post
different incidents in different threads to keep the thread clean. In doing
so, it will ensure your issues are resolved in a timely manner.

For urgent issues, you may want to contact Microsoft CSS directly. Please
check http://support.microsoft.com for regional support phone numbers.

Any input or comments in this thread are highly appreciated.

=====================================================

This posting is provided "AS IS" with no warranties, and confers no rights.

--------------------
<From:  eggedd2k <chrisnrach17@aol.com>
<Newsgroups: microsoft.public.windows.server.sbs
<Subject: Created a new mailbox but can't access it via Outlook or OWA
<Date: Mon, 30 Jul 2007 10:53:00 -0700
<Organization: http://groups.google.com
<Lines: 24
<Message-ID: <1185817980.899799.5640@q75g2000hsh.googlegroups.com>
<NNTP-Posting-Host: 172.207.202.169
<Mime-Version: 1.0
<Content-Type: text/plain; charset="iso-8859-1"
<X-Trace: posting.google.com 1185817981 2782 127.0.0.1 (30 Jul 2007
17:53:01 GMT)
<X-Complaints-To: groups-abuse@google.com
<NNTP-Posting-Date: Mon, 30 Jul 2007 17:53:01 +0000 (UTC)
<User-Agent: G2/1.0
<X-HTTP-UserAgent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1;
.NET CLR 1.1.4322),gzip(gfe),gzip(gfe)
<Complaints-To: groups-abuse@google.com
<Injection-Info: q75g2000hsh.googlegroups.com; posting-host=172.207.202.169;
<   posting-account=ps2QrAMAAAA6_jCuRt2JEIpn5Otqf_w0
<Bytes: 1730
<Path:
TK2MSFTNGHUB02.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTFEEDS01.phx.gbl!news-out.
cwix.com!newsfeed.cwix.com!newscon02.news.prodigy.net!prodigy.net!border1.nn
tp.dca.giganews.com!nntp.giganews.com!postnews.google.com!q75g2000hsh.google
groups.com!not-for-mail
<Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.windows.server.sbs:53366
<X-Tomcat-NG: microsoft.public.windows.server.sbs
<
<For some reason any new user account I set up in AD and create the
<associated exchange mailbox the user subsequently cannot access their
<mailbox in either Outlook 2003 or via OWA.
<
<In Outlook 2003 I receive a message saying "The name could not be
<matched to a name in the address list."
<
<
<In Outlook web access I just get the username/password box
<repeatedly.
<
<
<This happens for all new users that I create.I havent installed any
<updates recently nor have any permission changes been implemented.
<
<
<It seems like a permission issue somewhere but I'm not sure what to
<try next.
<
<We're using SBS 2003
<
<
<any ideas??
<
<