Link to home
Start Free TrialLog in
Avatar of Ohmit
OhmitFlag for Denmark

asked on

Outlook 2011 for Mac will not connect to Exchange

I have a SBS2008 with 5 clients, 3 Windows7 and 2 MacBook Pro's.
Both MacBooks is running OSX 10.6.6 and Outlook 2011.
For some reason the one of the Macbooks will periodically not connect to Exchange.
This is outside LAN as well as inside.
Thawte has issued a valid certificate.

I have placed the two Macbook's side by side and can confirm that settings is matching!
What is wrong here???

Settings in Outlook are as follows:

Exchange Account

Validation: Username and password

Username : DOMAINNAME\LOGIN

Microsoft Exchange:
Server: mail.DOMAIN.dk    : 443
v USE SSL
ASKER CERTIFIED SOLUTION
Avatar of Philip Elder
Philip Elder
Flag of Canada image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of Ohmit

ASKER

Please notice, that the are several clients connected to this SBS so I don't belive the server is the issue.
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of Ohmit

ASKER

:-) you asked for SP levels of Exchange?
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of Ohmit

ASKER

Hi Philip :-)

The 443 is default settings.
I have two similar MacBooks both with OSX 10.6.6 and Office 2011.
If I compare the settings they match 100%.
Difference is that one of them works the other don't!

I will check SP level of Exchange and get back ASAP

BONUS INFO :-)
If I configure the "good" MacB with the "bad" mac's user credentials it works perfect.
This should indicate without any doubt that the problem is located to the MacBook!