March 16, 2012 at 7:13 am
Hi,
I just installed SQL SERVER 2008 R2 and trying to create an odbc connection to a database on that server. I am using the same server to create the odbc connection as the sql server is installed.
I have set the server settings to allow remote connections.
Have done this many times for earlier servers...
Thanks
Bill
March 16, 2012 at 7:43 am
Bill Maners (3/16/2012)
Hi,I just installed SQL SERVER 2008 R2 and trying to create an odbc connection to a database on that server. I am using the same server to create the odbc connection as the sql server is installed.
I have set the server settings to allow remote connections.
Have done this many times for earlier servers...
Thanks
Bill
1. Ensure SQL Server service is running.
2. Ensure Browser service is running.
3. Ensure you are specifying correct IPAddress/ServerName.
4. If it is a named instance verify that you are specifying correct port number.
March 16, 2012 at 7:44 am
is the server an express instance , where remote connections are not enabled by default?
is it the default instance or a named isntance, and is the SLq broswer service running?
from a different server, can you connect to the new server via SSMS?
what specific error do you get when you try to connect? that will tell us a lot.
Lowell
March 16, 2012 at 10:35 pm
I also have sql 2008 installed on that server. I can still connect remotely to it.
The name is e521/R2 and e521 (slq 2008).
Allow remote connections is checked.
TCP/IP, Named Pipes and SharedMemory are enabled.
I do not the port nuimber to use...I am using Dynamic Determination of the port.
All services are runinng.
I cannot using SSMS locally but not remotely (using ssms for 2008)
Thanks for the reply.
Bill
March 17, 2012 at 5:25 am
First check the windows firewall. Disable it on the server, and then try to connect via SSMS from a remote machine. If it connect, you know you have to add the sql service to the allowed programs list. That's where i would look next.
Lowell
March 19, 2012 at 6:10 am
Triple checked everything. Not sure what it was, but I am able to connect now.
Thanks.
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply