![]() ![]() next until you are prompted to give it a name.ħ. The rest is all down hill, with nothing to really note press next.Next. make sure TCP is selected.įor reference, bcause i have four instances on my machine, i have four ports open:ġ433,12008,12012,12014 which is for my default instance, a SQL 2008R2, a SQL2012 and a SQL2014 i just mad esure those isntnaces listen to a static port instead of dynamic.Ħ. The right thing to do after that, is to add a specific exception for port 1433(assuming you are using the default port/only instance?)ġ.Go to the control panel and open windows firewall.Ģ.click on the Advanced Setttings Link you might get prompted with the UAC security prompt.ģ.Make sure the Inbound rules item is selected,a nd way over on the right, click new rule.Ĥ.Choose a rule type of Port and click next.ĥ.Put 1433 in the port box. You can prove it real quick by simply turning off windows firewall, and trying to connect from another machine. There's a dust layer at about that height and computers below the 2ft level (especially if you have carpet on the floor) will need to be cleaned internally (or filters changed if you have them) a whole lot more frequently. its a really bad idea to have any computer within two feet of the floor. Shifting gears a bit and speaking from experience way back when I was in PC support a million or so years ago. Just thought I'd add the newbie bit to check the protocol connections because locally it worked fine but network wise nothing. Dcomcnfg.exe fired up on our win7 platform and we made the recommended changes. Seems the Dcom has been tightened down too. Then we tried to log into SSIS, and failed for a odd error. Now we can see the server by it's machine name. Turned off the connections for the 2008 server then enabled the connections for the 2012 server processes and restarted the services. Yes, this is not good practice but kind of day-to-day real life. The 2008R2 had the TCP/IP and Named pipes enabled protocols. Jumped into the configuration manager, I realized what we did. Digging further we noticed there was 2 SqlServers running on this box. ![]() We can ping from a dos prompt but we can't connect via SSMS. I can now see the admins but no one can log in. ![]() ![]() We run SSIS packages from it for now and only until our new budget when we can buy a real server. My "server" is running under a desk and we just hammered it together quick. We attempted to add a new administrator to a 2012 box like we've done before with 2008R2 and previous. I did check that 'BUILTIN\Administrators' is a member of the sysadmin role.įirst let me say I'm a huge fan of Lowell. I can use them to login for other parts of the sql server, though. I have executed the mentioned xp_logininfo SP and it lists the users in the Administrators group but they don't work as logins for the Database Engine. I have the same issue but even after adding BUILTIN\Administrators, I am not able to log on with any account in the Administrators group (except for the user Administrator that has a separate login configured). Add/Restore Restore Builtin\AdministratorsĮXEC sp_grantlogin 'BUILTIN\Administrators'ĮXEC sp_addsrvrolemember 'BUILTIN\Administrators','sysadmin'Īfter you've done that, make sure you are really part of the Builtin\Administrators group:ĮXEC = 'members' - show group membersĭoes your windows login appear as part of that result set? Something like this is what you are after, i think: Adding the login is not enough.did you add them to the server role as well ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |