Autodiscover service not working

The following solution might not be Microsoft recommended or supported. 

Please read the rest of the thread below before tying this fix.  There are many other more common fixes to the problem that should be tried before the fix presented here.

I found this solution on a third party web site.  The site claimed that it only affected exchange 2007- and prior to SP2.  It should not affect Exchange 2010, but in my case it worked. I’m guessing in my case, the in-place upgrade had something to do with it, and I think the problem didn’t appear until the DC was changed to 2008.

In IIS, I changed the ‘Windows Authentication’ to run ‘kernel-mode authentication’

On the client, I was no longer prompted starting outlook.  Using the test auto-configuration showed it found via SCP and http status 200.  Viewing the Outlook diagnostic logs (olkdisc.log) also showed successful authentication negotiation.  Accessing Out-Of-Office failed, as did Free/busy.

I then turned on kernel-authentication on EWS and OAB (OAB inherits the setting from the Default Web site level).

Problems with OOF, Free/Busy, downloading OAB all went away for both Outlook 2007 and 2010.  Viewing the Outlook diagnostic logs confirms they are successfully running.  And I no longer get any authentication prompts.

Thanks for all those who help in troubleshooting the problem and I hope others will find this information useful.

EULA every time you open Outlook

Run Outlook.exe as Administrator

problem solved.

SQL Server does not exist or access denied

Situation:

New SQL Express 2012 on Server 2008 r2 (specifics shouldn't matter)

Trying to connect to the DB from another server (local subnet).

Was getting error "SQL Server does not exist or access denied."

Couldn't telnet to port 1433. Could to other ports.

TCP/IP and named pipes enabled.

Services properly authenticated and started/restarted.

Firewall exceptions given to 1433 on SQL server's inbound (even tried disabling firewall)

What tripped me up was that I was working with a non-default instance (original one was disabled). Apparently, the non-default instance gets a random port generated for it. Also, the port doesn't seem to show itself anywhere in the SQL mgmt tools.

The port was found here:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL11.SQLEXPRESS\MSSQLServer\SuperSocketNetLib\Tcp\IPAll

I put it in the firewall inbound exceptions, success.

Windows 7 can't join domain, DNS issues resolved

You need flush your DNS cache in client side first.

Then, let’s create the following registry value for a try:

HKLM\System\CurrentControlSet\Services\LanManWorkstation\Parameters

 - Created a DWORD DomainCompatibilityMode = 1

 - Created a DWORD DNSNameResolutionRequired = 0

Reboot the machine and check the result again.