Re: Accessing OAB from domain other than the domain where Exchange
- From: CurlySafrican <CurlySafrican@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Sun, 7 Jan 2007 05:07:00 -0800
On the exchange 2003 resource mailboxes the tick for associated external
account needs to be selected for the NT account accessing it.
See http://support.microsoft.com/kb/278888
Cheers
Andreas
"CurlySafrican" wrote:
Please ignore the last statements gathered from the OABInteg test tool. The.
same results are produced when running the tool as one of the AD users.
"CurlySafrican" wrote:
I have this same problem; have you had any success in sorting this out ?
Before reading your post I used the OABInteg test to compare the access from
my AD users with that of the NT users.
When I ran the oabfldcheck test the NT users came back with one particular
error.
Property type not recognized for Property Tag = 0x6699000A,
PR_OVERALL_AGE_LIMIT
When running this same OABInteg test as one of the AD users this does not
appear at all.
Also I have come across a site where it seems that the PR_OVERALL_AGE_LIMIT
value should be 0x66990003
I don't know whether this is true, but I wouldn't mind trying to change it
if I knew where to.
Anyone else have any ideas about this?
Cheers
Andreas
"John Walker" wrote:
Yeah I initially thought that it might be a GC problem but the client
can get to the Global Address list, and they can also get a recent copy
of the global address book as an offline address book if I kill their
OST and rebuild it. It just seems to be the public folder where the OAB
lives that is giving the problem.
I did set up their DNS server so that my mail server hostname resolves
IP properly but with their domain name, as you are correct in the two
domain names are obviously different. That could certainly be confusing
the client.
However, you did give me an idea, in that I may need to add the true
domain name to the list of appendable domains on the NT domain clients.
A few of them have this already, so it may be working for them and I
don't realize it.
I will test by adding the host to a client computer directly and seeing
how it behaves.
I will post if that fixes or doesn't fix it. Thanks for the input!
JPW
On Nov 4, 5:26 pm, "-=-=-=-=-" <n...@xxxxxxxx> wrote:
Hello,
I noticed than when the clients are not in the same domain as the Exchange
domain you witness a lot of mecanism you will not see otherwise.
With Outlook 2003, you will see even more such things. And the cache mode
add a twist too...
For the technical background : when you says "Windows NT domain", do you
really mean NT 4 domain ?
My first guess is a name resolution problem.
For example, from my experience, when Outlook tries to contact a Global
Catalog, it will use unqualified name (not FQN).
As you belong to another domain, you usually don't have the DNS suffix for
the other domain. Therefore the DNS resolution will fail. Next Outlook will
try to perform a Netbios resolution and will fail as well...
You should try to investigate using a network monitor such as Packetyzer
from the client computer. Watch for DNS and traffic to the other domain.
It could show you as well a problem related to Kerberos.
--Richard.
<tsa...@xxxxxxxxx>
|I have a trusted domain from a company that we purchased. It is a
| Windows NT domain, but we have created users on our 2003 AD/Exchange
| domain for all of the NT domain users.
|
| After establishing the trust between the domains, I granted individual
| mailbox rights from each users old NT domain login to their new
| domain/Exchange mailbox so they would not have to enter their newer
| login each time they opened Outlook (also version 2003).
|
| These users are across a WAN connection from the Exchange server, so we
| set them up in cached Exchange mode.
|
| If Outlook is configured to use the NT domain login, not to prompt for
| a username, the users can access their e-mail correctly, but their
| offline address books are not being updated. If I force an OAB
| download, I receive a 8004010f error, object could not be found. The
| OAB is updated if I delete their local OST file and let all of the
| information be recreated.
|
| If I force the user to enter their new domain credentials, the OAB
| downloads correctly. If the user is not running in cached mode, they
| can see the Global Address List completely as well.
|
| I am therefore assuming that this is a permissions issue with the OAB,
| but I can't find the appropriate spot to apply permissions. I have
| expanded the public/system folder hierarchy in the Exchange manager
| tool and added my login from the old domain to be granted full rights
| to the Offline Address Book system folder and the two folders below it,
| as well as the OAB Version 2 and OAB Version 3a folders.
|
| This is temporary until i get the users migrated, but there are several
| users and it will still be a while before this project gets underway.
|
| Any help would be appreciated.
|
| JPW
|
- References:
- Re: Accessing OAB from domain other than the domain where Exchange
- From: CurlySafrican
- Re: Accessing OAB from domain other than the domain where Exchange
- From: CurlySafrican
- Re: Accessing OAB from domain other than the domain where Exchange
- Prev by Date: Hmtl Mail
- Next by Date: Re: Hmtl Mail
- Previous by thread: Re: Accessing OAB from domain other than the domain where Exchange
- Next by thread: Re: Attachment Size Limit in Exchange 2003
- Index(es):
Relevant Pages
|
