July 26, 2006 at 1:29 pm
I am developing in one dedicated server and a workstation and was working without any problems till I had to reinstall the OS on the workstation. When I was up and running again I could not logon to SQL Server anymore from this machine; neither with my regular Windows logon from «Power Users group» nor with the Administrator. I still can logon from the server. Obviously the server kept the SIDs from my prior workstation installation so I went to management studio to add a new login from my new workstation but the problem is management studio is not detecting my new computer (location) on the add new login property window; it only displays the server name on which is running. Needless to say that the workstation is listed properly (along the server name) on Windows Explorer network places | MicroSoft Windows network | «MyGroup» and that I can access resources on both machines from both of them, so the network setup is not an issue, it's working flawlessly. Question is: I am missing something important here ? Should I «register» my workstation (or whatever) in management studio or sql server in order to lookup objects on another machine ? Please advise. Thanks.
July 26, 2006 at 3:07 pm
Are you in a Domain? If you can login to SQL Server using your Domain Windows account, there is not a problem with your login. But if you've already deleted your Windows login in an attempt to re-create it, add your Domain login as the new login. You do not want to add your Workstation's local logins. When you say that you cannot login anymore, are you getting an error message? What tool/method are you using to login?
July 27, 2006 at 2:18 am
Nope, I'm not in a domain. Both machines are running Windows Server 2003 EE R2. The server is configured with app and file server roles only, it's not running a domain controller nor Active Directory though I probably add this role to unify logons and the like (it wasn't done yet because I'd like to learn a little bit about it and didn't have the time to do so). SQL Server database engine is installed on the server and Management Studio on both machines (on the server for troubleshooting purposes like this one) and on the workstation as my primary dev tool along Visual Studio. I usually login to SQL Server from Management Studio on the workstation. The server is running with an ASP app accessing SQL Server (ASP.Net granted access on many databases) and is fully working both from the server and the workstation. The only problem seems to be with the new workstation OS installation users; both the Administrator and my ID. Do you suggest I add a domain controller role to avoid problems like this in the future ? If so, SQL Server will use the users/group defined in Active Directory instead of the stand-alone ones on both machines ? I'm not very much involved in Active Directory and domain controllers issues so I'm a little bit new to these issues but I think adding it will result in single logons and a better resource organization although I don't want to set up a role resulting in more complications, my primary focus is development and I'd like to keep focused on it, not spending half an hour a day or whatever trying to maintain something like Active Directory.
July 27, 2006 at 8:49 am
Check the Windows Firewall on your new workstation. Disable the firewall and try connecting again.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply