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 |
|
igendreau
Starting Member
6 Posts |
 Posted - 2009-08-17 : 16:19:19
|
| I have a desktop running SQL Server 2005 & Visual Studio 2005. I also have Visual Studio 2005 on my laptop. I'm trying to learn to create some basic data pages using VS.If I fire up VS on the desktop (the same machine that's running SQL Server), and try to add a data grid and create a new connection, I have no problem. When I create a new connection and click "Server Name", my desktop appears in the list. When I select it in the list, then click on the "Connect to a database" drop-down, I get a list of a dozen different SQL databases on that machine. If I click on "Test Connection", it's a success.Now I fire up VS on my laptop and try to connect from another machine. Clicking the "Server Name" drop-down, gives me the same list of servers, and I pick my desktop. However, the list of databases drop down gives me nothing and if I Test Connection, I get the following:"A network related or instance-specific error occurred while establishing a connection to the SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that the SQL Server is configured to allow remote connections."I assume there is a problem with my SQL Server accepting the remote connections. But I fire up SQL Server Mgmt Studio, right click my server, go to properties, and there is indeed a check in the box that says "Allow remote connections to this server".Not sure how to get it to work, so I can develop on my laptop while connecting to the remote SQL Server. Any thoughts? Thanks! |
|
|
webfred
Master Smack Fu Yak Hacker
8781 Posts |
Posted - 2009-08-17 : 16:29:43
|
Go to your computer where SQL Server is running.Start configuration manager from programs menu.There you can allow connections via TCP/IP.
No, you're never too old to Yak'n'Roll if you're too young to die. |
 |
|
|
igendreau
Starting Member
6 Posts |
Posted - 2009-08-17 : 16:43:41
|
| Okay, I started Configuration Manager, just not sure what to change. Under "SQL Server 2005 Network Config" I have an entry called "Protocols for MSSQLSERVER". Clicking on it gives me a list of protocols, and TCP/IP is listed as "Enabled". Is there somewhere else I need to enable it? |
|
|
|
webfred
Master Smack Fu Yak Hacker
8781 Posts |
Posted - 2009-08-17 : 16:51:32
|
No - that's what I meaned.Maybe youre connecting via Windows Authentication?From your client try to connect via SQL Server Authentication using SA user.
No, you're never too old to Yak'n'Roll if you're too young to die. |
|
|
|
igendreau
Starting Member
6 Posts |
Posted - 2009-08-18 : 09:55:23
|
| Okay, here is a list of things I've tried with no results. FYI, the machine the server is running on and my laptop are both on the same domain. This is an intranet type setup.-Changed my server's authentication mode from "Windows Auth Mode" to "SQL Server & Windows Auth Mode"-Tried connecting remotely using sa account. No luck. Reset sa password, no luck.-Created a new login, gave myself access to all the databases and sysadmin and public rights. Tried connecting remotely with that login. No luck.Any other ideas of what might cause this? Driving me crazy! Thanks for the help! |
|
|
|
|
|
|
|
|
SQL Server Connection Issue