Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
AjarnMark
SQL Slashing Gunting Master
3246 Posts |
 Posted - 2007-03-07 : 10:31:46
|
| We are in the late stages of collapsing two Active Directory domains into one. We migrated all user accounts before migrating hardware. In the last set of changes, we were moving four servers to the new domain. Two were SQL Servers (one 2000 and one 2005, both with multiple instances of SQL Server). One was an external web server and the other was an internal web server with Windows SharePoint Services 2.0. After the servers were moved into the new domain, the SQL 2000 instances stopped accepting connections by name (e.g. "Server=myserver\myinstance...").Specifically, we received error messages from our web applications when they tried to connect using SQL authentication and connecting by instance name. One message referenced [DBNETLIB], but I thought our connections were all TCP/IP. We do have multiple protocols enabled on the server because we have one application that uses something other than TCP/IP, so we can't just disable all other protocols. When we moved the servers back to the old domain, they did not recover. We have been able to temporarily work around this issue by changing the connection to explicitly reference TCP and the port number (e.g. "Server=tcp:myserver,9999").I understand we could create aliases on our servers, but we did not have those setup before the move, so why would that suddenly become necessary? Is there some server profile setting that got reset when we changed domains, and we just need to update it?Note that the SQL 2005 instances continued to work fine. Also note that I am not able to connect to the SQL 2000 instances from my own desktop using SQL 2005 Management Studio by using the instance name. I have to reference the port number in my connection information, too. I used to connect by name just fine, but now cannot, so it appears I am having the same problem that the web apps are.Any ideas?---------------------------EmeraldCityDomains.com |
|
|
pareshmotiwala
Constraint Violating Yak Guru
323 Posts |
Posted - 2007-03-07 : 12:40:07
|
| What are your services' startup accounts from the new domain? That is how it should be. |
 |
|
|
AjarnMark
SQL Slashing Gunting Master
3246 Posts |
Posted - 2007-03-12 : 16:45:06
|
quote:
Originally posted by pareshmotiwala
What are your services' startup accounts from the new domain? That is how it should be.
I don't quite understand your question. The startup accounts for the SQL Services are domain accounts in the new domain. The services start fine. I am able to connect to the SQL instance if I explicitly state the port number, but this was not necessary previously. I used to be able to just specify the server name and instance name. Is there a special service for that instance name to port number resolution?---------------------------EmeraldCityDomains.com |
|
|
|
|
|
|
|
|
Can't Connect to Instance After Domain Change