January 6, 2011 at 10:52 am
Hey everyone,
I am probably missing something rather silly, or Microsoft has added something I haven't found yet, but I am having issues connecting remotely to SQL Server 2008 R2 default database.
I have validated the following:
1) Instance > Properties > Connections - Allow Remote Connections to this Server
2) Both SQL Server Authentication and Windows Authentication are both active. Both methods Fail.
3) I have tried both creating a login and using the 'sa' login with sql server auth and can connect locally with them, but not remotely.
4) Windows authentication is failing because I have to have admin rights in active directory to be able to use logins with Sysadmin rights
5) The firewall on the server is disabled.
6) There are no error massages in the log file or the event view for me to debug.
The message I get from SSMS is as follows:
"A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: TCP Provider, error: 0 - No connection could be made because the target machine actively refused it.) (Microsoft SQL Server, Error: 10061)"
Additionally, there is one small fun fact about this server.
The physical machine name and the machine name on the domain is DBDEV. However, when you do an @@ServerName we get the name DBTest. This was intentional as we will be renaming the machine to DBTest after a small migration. I bring this up as I want to make sure it isn't the issue.
Lastly, this machine is currently be uses for internal reporting using SSRS. There are no issues with connections to the report server.
Thanks everyone.
Fraggle
January 6, 2011 at 11:33 am
servername must match the windows name. Sp_dropserver/sp_addserver needed.
Also, you can do a netstat from the command line, and see what port is open and listening. Should be 1433.
January 6, 2011 at 12:49 pm
Steve,
Thanks. I was leaning that way and it does correct the issue. However, my reporting server breaks. 🙁
I don't suppose there is a way around this until I change the physical machine name in the next 2 weeks?
Thanks,
Fraggle
January 7, 2011 at 7:14 am
Not that I know of. You can try connecting by IP, port. That might work.
Can you not reconfigure SSRS to point to the new name? Or you don't want to, I guess.
That connection between SQL and the host server is pretty strong.
January 7, 2011 at 1:44 pm
I would prefer not to simply because we will be renaming the server to DBTest in the next month. I would need to alter all of the security rights with the windows authentiations that the system is currenty using for reporting servers to go with it, which would be a larger pain.
Oh well, I will just deal with it and take the reporting server down at odd times. Management is going to love that one. 😀
Fraggle
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply