"Interesting" calendar problem Ex5.5/Ex2003

I have rather a strange problem that I would like some comments on if at all
possible.

We have a reasonably large Exchange 5.5 organisation which has started
migration towards Exchange 2003. So far, two servers in a site have been
converted to Exchange 2003 and SRS and ADC connectors seem to be running
correctly. We have full visibility of all users in the GAL on both sides and
email flows correctly between both sides.

We do have a problem with accessing other users calendars though. Users on
the 2003 side can access all calendars (default permissions on calendars are
set to Reviewer) but users on the 5.5 side can only access 5.5 calendars.
Any attempts from a 5.5 user to access a 2003 calendar results in a message
from Outlook saying it can not open the folder.

We have traced the problem through diagnostic logging and network tracing
and are convinced it is not a lookup issue, Outlook correctly identifies the
server that holds the calendar and attempts to connect but seems to get an
access denied message.

The only way we can access a 2003 calendar from the 5.5 side is to give full
mailbox access through ADU&C, login in as a Domain Admin on the NT4.0 side
(normal users do not work) and then configure Outlook to access the 2003
mailbox as the only mailbox being used. The entire mailbox then opens
normally.

Initially Calendars did work and then stopped. We corrected some ADC issues
to get replication running again but calendars still do not work.

Currently SP2 is not installed on the Exchange 2003 servers but will be
applied in the next maintenance window.

Nuevo
Wed Jan 18 07:28:52 CST 2006

Karl

As you found this should work (and did for you) without too many problems.
Can you clarify what you mean by "corrected some ADC issues" as this would
appear to be the source of the problem?

Nue
"Karl Foley" <karl@thefoleyhouse.co.uk> wrote in message
news:ubEwWgCHGHA.3728@tk2msftngp13.phx.gbl...
>I have rather a strange problem that I would like some comments on if at
>all possible.
>
> We have a reasonably large Exchange 5.5 organisation which has started
> migration towards Exchange 2003. So far, two servers in a site have been
> converted to Exchange 2003 and SRS and ADC connectors seem to be running
> correctly. We have full visibility of all users in the GAL on both sides
> and email flows correctly between both sides.
>
> We do have a problem with accessing other users calendars though. Users on
> the 2003 side can access all calendars (default permissions on calendars
> are set to Reviewer) but users on the 5.5 side can only access 5.5
> calendars. Any attempts from a 5.5 user to access a 2003 calendar results
> in a message from Outlook saying it can not open the folder.
>
> We have traced the problem through diagnostic logging and network tracing
> and are convinced it is not a lookup issue, Outlook correctly identifies
> the server that holds the calendar and attempts to connect but seems to
> get an access denied message.
>
> The only way we can access a 2003 calendar from the 5.5 side is to give
> full mailbox access through ADU&C, login in as a Domain Admin on the NT4.0
> side (normal users do not work) and then configure Outlook to access the
> 2003 mailbox as the only mailbox being used. The entire mailbox then opens
> normally.
>
> Initially Calendars did work and then stopped. We corrected some ADC
> issues to get replication running again but calendars still do not work.
>
> Currently SP2 is not installed on the Exchange 2003 servers but will be
> applied in the next maintenance window.
>
>

Karl
Wed Jan 18 08:00:36 CST 2006

> As you found this should work (and did for you) without too many problems.
> Can you clarify what you mean by "corrected some ADC issues" as this would
> appear to be the source of the problem?

Firstly, thanks for the reply.

In answer to your question the problem with the ADC connectors were minor -
Someone had changed the account password for the account used to connect to
Windows\Exchange to synch the 5.5 and 2003 directories. Once the password
was corrected the ADC began synchronising again correctly.

As part of the troubleshooting for this process we did delete a 2003 ou's
worth of disabled user accounts and had to clear a 5.5 attribute
(ADC-Global-Names? ISTR) using 5.5 Admin in raw mode before we could get
them to reappear in 2003.