Scalix 11-GA: Unable to open delegated mailbox

[tuxtattoo]

Hi,

I'm having trouble opening up a mailbox that has been delegated to me in Office 2002 after upgrading to Scalix 11-GA. I even tried uninstalling and reinstalling from scratch again.

I've tried two different computers and two different version of your Outlook connector (v10 and v11GA) and both yield the same results. I have tried with and without the SmartCache but no joy.

SWA has no problem with the folder, it works as it should.

The error that I get is:

"Unable to expand the folder. The set of folders could not be opened. The information store could not be opened."

I am trying this on the Community edition, but since it's not going well, I am scared to try it on my Enterprise edition. Anyone have any ideas?

[BoomerangIT]

I to am having a similar problem, but when trying to open a shared Calendar after delegation.

I get the error message "Unable to display the folder. The information store could not be opened."

This is a fresh install of Scalix11-GA, with the Scalix 11-GA Outlook Connector.

Has anyone else had this problem, and more importantly is there a fix for this.

Kind Regards

Matt

[kanderson]

on the server, type

omshowmnmp

this will return a server name.

On the desktop, you need to be able to reach that server by name. Delegation works by referring you to a server and a user. (so that it works in multi-server installations). Almost always, a delegation problem will be an issue with DNS.

This is assuming delegation is set up correctly. You need to allow access to the user's mailbox, as well as the specific folder they should have access to.

[tuxtattoo]

on the server, type

omshowmnmp

this will return a server name.

On the desktop, you need to be able to reach that server by name. Delegation works by referring you to a server and a user. (so that it works in multi-server installations). Almost always, a delegation problem will be an issue with DNS.

This is assuming delegation is set up correctly. You need to allow access to the user's mailbox, as well as the specific folder they should have access to.

I fixed it by adding a new zone to my internal DNS server and it fixed the issue. Previously, I tried using the IP address and that didn't work. Tthen I added an entry to the lmhosts file, which also didn't work. I guess the Outlook connector doesn't use the lmhosts file?

Thanks for the help.

[kanderson]

lmhosts is only for SMB networking. If you added it to hosts, rather than lmhosts (LanMan hosts), it would have worked. But the reality is, you should correct the DNS problem rather than using work arounds. Eventually, they will catch up with you as shown here.

Kev.

[blentini]

I cannot use outlook connector at all. I have my firewall opened to allow connections form TCP/5729 and TCP/5757

I believe my issus that the 5757 is listening on localhost and not the ip for the nic. If my assumption is right, how can I change this. If not, what could it be?

I have already tested DNS and that is working correctly for my server.

Regards,

Bob

[kanderson]

Please start a new thread. Your issue is unrelated to the delegation issues these people were encountering.

Thanks
Kev.

[dresdn]

Hi.

I just wanted to point out something that might be of use in case anyone else stumbles across this thread.

In a new install, I had the exact same problem, and it was driving me nuts because everything was reachable by DNS. The problem was that the mail.domain.com was resolving to the external IP which was port forwarding to the server, not the internal IP of the server itself. When I did an "ommodnmp mail mail.internal.lan" the problem was resolved.

-Mike

[kanderson]

The command dresdn mentions had a typo. It should be ommodmnmp

He's correct, this can be an issue. In addition to this, you may also need to change entries for the webclient, and other areas too.

If possible, you add an alias so that resolution works for internal and external?