First let me say I'm a huge fan of Lowell.

We attempted to add a new administrator to a 2012 box like we've done before with 2008R2 and previous. That's what brought me to this post. My "server" is running under a desk and we just hammered it together quick. We run SSIS packages from it for now and only until our new budget when we can buy a real server. It also happens to be my desktop.

Saw this post and ran the sql. I can now see the admins but no one can log in. We can ping from a dos prompt but we can't connect via SSMS. The connection just times out. Digging further we noticed there was 2 SqlServers running on this box. A 2008R2 scratch database and the 2012. Jumped into the configuration manager, I realized what we did. The 2008R2 had the TCP/IP and Named pipes enabled protocols. The 2012 it was not. Yes, this is not good practice but kind of day-to-day real life. Turned off the connections for the 2008 server then enabled the connections for the 2012 server processes and restarted the services.

Now we can see the server by it's machine name. Then we tried to log into SSIS, and failed for a odd error. Seems the Dcom has been tightened down too. Went here:

https://msdn.microsoft.com/en-us/library/hh213130(v=sql.110).aspx

That actually worked in a dos prompt. Dcomcnfg.exe fired up on our win7 platform and we made the recommended changes.

Just thought I'd add the newbie bit to check the protocol connections because locally it worked fine but network wise nothing. Thanks again everyone for posting this. It helped a lot.