Re: user can't access mailbox

Tech-Archive recommends: Speed Up your PC by fixing your registry

ho ho ho, i read a lot more about ldap and found how to navigate directly to
the user object. as per now successfully completed instructions, i found
how to troubleshoot the Recipient Update Service:
http://support.microsoft.com/default.aspx?scid=kb;en-us;q288807

end solution, went into Active Directory Users and added the Exchange
Enterprise Servers group to the users Security tab, and set it to modify.
now the server can access the user and add the needed values to his active
directory object!

glory to the newsgroups for being the most helpful resource yet again.
-a

"anon" <not@xxxxxxxxx> wrote in message news:EdTNf.306$mw5.153@xxxxxxxxxxxxx
great article, i went through it several times and it taught me a lot. i
got ldp.exe and am able to connect and log into a domain server. however
in
section 4. it says that the showInAddressBook attribute should have a
Global
Address List variable, but there is none for any of my users (including
administrator, who is mail enabled.)

i then opened the value as a Tree (Base DN:

CN=Show-In-Address-Book,CN=Schema,CN=Configuration,DC=sub,DC=domain,DC=com)
but it showed no children (for any user). i then searched and found the
Global-Address-List value and viewed that as a tree, but there were no
children for that either.

then the article said to find the addressBookRoots attribute under
Domain,cn=Configuration,cn=Services. I tried
CN=Services,CN=Configuration,DC=sub,DC=domain,DC=com but it found nothing.
then i tried Schema instead of Services and found something, but viewing
it
taught me squat.

i'm not sure if i'm doing something wrong... but i think the user is just
not able to be added the global address list, because no one else can see
him from their Outlook list. i went into the Exchange Manager -> Default
Address List properties and added his user as full control over the
object,
but still nothing.

how could i go about manually adding him (i guess through ldp?) to the
global address list?
-a


"Nuevo" <imaneophyte@xxxxxxxxx> wrote in message
news:eExIG1UPGHA.312@xxxxxxxxxxxxxxxxxxxxxxx
Did you modify the default recipient policy and perhaps missed adding a
required value to this account?

Also, as for the check name error in Outlook, try this:

http://support.microsoft.com/kb/297801/en-us

Nue
"anon" <not@xxxxxxxxx> wrote in message
news:z5cNf.155$mw5.47@xxxxxxxxxxxxx
i'm running windows 2003 with exchange server 2003 (with sp2) on a
network
with two
clustered windows 2000 ADs. i've successfully set up mailboxes and
routing
for all the users in my active directory except for one. when i apply
the
default recipient policy, everyones mail address changes however i set
it,
except for his. in the AD snap-in, i added his mailbox and email
addresses
by hand, and i can log into his mailbox through the Web Access
website,
but
when i try to make his outlook 2000 connect to his mailbox it can't
even
find his user name in the global catalog. other users in the network
don't
see him on the public global catalog to send email to.

i tried previewing the global catalog on the exchange server and he's
on
that list. also, his mailbox was definately created (by sending him
email,
and also by accessing his web interface). i tried deleting the active
directory user object and making a new one from scratch with the same
values, but exchange still won't automatically set up his SMTP and
x400
email addresses.

i tried to force replicating AD, rebuilding recipient update service,
making
new recipient and system policies... i don't know what to try anymore.
any
help would be much appreciated.

-a








.

Relevant Pages

  • Re: Connection to a SAMBA Active Directory
    ... Keep in mind that you're trying to setup a NT4 style trust ... if you setup the Exchange as a resource forest model, ... domain and the Exchange server in another domain will work. ... I am able to define a 2 way Realm trust using the Active Directory ...
    (microsoft.public.exchange.connectivity)
  • Re: Connection to a SAMBA Active Directory
    ... domain and the Exchange server in another domain will work. ... I am able to define a 2 way Realm trust using the Active Directory ... There is a bit of confusing on the SAMBA side. ...
    (microsoft.public.exchange.connectivity)
  • Re: Home Network Dilemma
    ... You must understand Active Directory first, in order to implement Exchange. ... Matter of fact, Exchange must alter Active Directory prior to installation, to accomodate the changes. ... On top of that, an understanding of DNS is required, because AD will not work if DNS is not implemented properly for its internal use only, and on top of that, an understanding of DNS on the internet is required in order to manipulate public records so others in the world can 'find' your mail server on your network. ...
    (microsoft.public.windows.server.networking)
  • Re: Exchange 2003 Disaster Recovery 1.mal / Wiederherstellung
    ... und habe dem Exchange Server im ADS einen neuen Namen gegeben. ... Und im ADS bei einem Exchange user bekomme ich die Meldung (Exchange ... > an Active Directory operating system installation that was saved in the past ...
    (microsoft.public.de.exchange)
  • Re: Connection to a SAMBA Active Directory
    ... I built a new Windows 2003 Server in a brand new domain. ... I am able to define a 2 way Realm trust using the Active Directory ... There is a bit of confusing on the SAMBA side. ... Active Directory components but not enough to deploy Exchange. ...
    (microsoft.public.exchange.connectivity)