When launching Lync (same goes for the old OSX Communicator), I get a message stating that:

"Sign in to Microsoft Lync failed because the service is not available or you may not be connected to the Internet."

Needless to say, I am connected to the Internet.

In fact, I am ABLE to connect to our Lync server if I change the DNS settings on my machine to point to an outside DNS service (i.e. Google DNS = 8.8.8.8). Of course that then prevents me from accessing other critical internal services, QA environments, etc. When I switch back to my corporate DNS, Lync maintains its connection so I'm able to IM, see presence, etc. but, its an awful workaround and something that's been broken for years based on various message boards around the internets.

Any plans on fixing it? Or can you provide guidance on proper AD config issues (if that's the problem)?

Impacted systems:
- Lync v14.0.1
- Communicator v13.1.3
e use Microsoft Lync in my company, and the outside contacts that I had for hotmail or MSN are no longer showing their presence?.
Shortly after installing Office 2011 for Mac, everything went pretty sour (I'm on Lion 10.7.4). Here's a roundup of the situation.

1) Lync starts, but then promptly crashes with a EXC_BAD_ACCESS. Crash log is below:

Error Signature:
Exception: EXC_BAD_ACCESS
Date/Time: 2012-06-11 00:52:18 +0000
Application Name: Microsoft Lync
Application Bundle ID: com.microsoft.Lync
Application Signature: UCCP
Application Version: 14.0.0.110823
Crashed Module Name: Microsoft Lync
Crashed Module Version: 14.0.0.110823
Crashed Module Offset: 0x00011a1b
Blame Module Name: Microsoft Lync
Blame Module Version: 14.0.0.110823
Blame Module Offset: 0x00011a1b
Application LCID: 1033
Extra app info: Reg=English Loc=0x0409
Crashed thread: 38

Already tried a re-install, deleting certificates, re-installing again.

2) Outlook then decided to bite the dust too. It worked twice, and then it just won't launch. The menu bar is up at the top, but no UI displays at all. Oddly enough, it works on other user accounts but I get the feeling that's a temporary thing too.

Now of course you're saying 'Well, just go use the Microsoft Database Utility and rebuild! Duh!" I could if I would, so that brings us to problem #3. (Oh, tried a re-install here too).

3) Microsoft Database Utility crashes faster than anything else I've ever seen. Quite remarkable really. Here's its crash log:

Error Signature:
Exception: EXC_CRASH (SIGTRAP)
Date/Time: 2012-06-11 00:55:41 +0000
Application Name: Microsoft Database Utility
Application Bundle ID: com.microsoft.outlook.database_utility
Application Signature: DUlr
Application Version: 14.2.0.120402
Crashed Module Name: merp
Crashed Module Version: 2.2.4.120402
Crashed Module Offset: 0x00003aa2
Blame Module Name: Microsoft Database Utility
Blame Module Version: 14.2.0.120402
Blame Module Offset: 0x00005ea8
Application LCID: 0
Extra app info: Reg=en Loc=0x0000
Crashed thread: 0

I am in need of serious help. I've ready several dozen forum posts on way too many forums, and I feel like a headless chicken.

Thank you to anyone who can help me out!

~J