April 1, 2007 at 6:33 am
Hi All,
I'm not sure if I've put this thread in the correct area, but if you read on, you will find out that I know NOTHING about SQL, so I figured I would put this in the Access area - the only aspect of this whole thing that I 'sort of' understand.
Anyway, my problem is that I have no idea what I'm doing.
I am trying to 'network' several databases, so that the main stuff is on the server and the clients just connect to the network, and synchronise their system.
My big problem is actually getting the whole thing set up - forget the whole SQL code/queries or whatever it does - I’m not even up to that stage yet. I'M JUST TRYING TO GET THE COMPUTERS TO TALK TO EACH OTHER!
For the purposes of experimentation, I've got my laptop as the server and my desktop as the client.
I have the following software installed:
- MS SQL Desktop Engine (on both)
- MS SQL Server Management Studio 2005 & MS SQL Server Business Intelligence Development Studio (on the Laptop/server)
I've been toying with this for WEEKS and can't get my databases to connect. (I'm not really sure how this whole server thing works too!) I managed to get the SQL Server Management Studio to connect to the Laptop, but now it won't anymore saying:
"TITLE: Connect to Server
------------------------------
Cannot connect to LAPTOP.
------------------------------
ADDITIONAL INFORMATION:
An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not 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)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=10061&LinkId=20476
------------------------------
BUTTONS:
------------------------------
"
- I'm not sure what this means and I SWEAR I haven't changed anything! Plus the Microsoft help is more of a frustrating time waster than assistance.
Do I have to create special windows logins? Do I have to set up permissions in for my network? As far as my desktop is concerned, it can't connect to my laptop - it doesn't even see it.
If ANYONE can help me out with ANY of the above, or can point me to a step-by-step 'set up your server for frustrated dummies' website I would be very much grateful.
Cheers,
Jason.
April 1, 2007 at 9:48 am
Jason,
Take a deep breath. It can be frustrating, but let me try and explain a couple things. First you don't connect a SQL instance to another. At least not easy. There's linked servers and replication, but really both your installs are "servers".
Now, when you open Management Studio, it should be looking to connect to a server. Can you connect to 127.0.0.1 on the laptop? That would be your client (Management Studio) connecting to your local server (laptop). You can also use the Windows neighborhood name (My Computer/Proprties/Name tab).
If that works, or doesn't, now try connecting to your other computer.
If those don't work, you need to be sure both servers are running. Check your services and there should be an MSSQLServer service that is started. This is your database engine. It might be name something slightly different depending on your install, but look for a SQLServer service of some sort.
Then let us know and we'll go from there.
April 1, 2007 at 8:57 pm
Hi Steve,
Thanks for the help. I've moved on to yoga-style breaths, so I should be good for the moment. I've checked the neighborhood name - it's "Laptop". I've tried both this and "127.0.0.1" and neither works - I've attached the screenshot below:
I was playing about with the logins last night because I thought that's possibly why my other computer can't connect to this server. I don't think that I changed anything, but is it possible that I told it to disallow connections to the server? If so how do I get it back?
I appreciate the help.
Cheers,
Jason
April 2, 2007 at 6:35 am
You must put your image on a web server, or else only you, from you pc will be able to see it.
April 2, 2007 at 8:07 am
Oops - sorry, I don't actually have a web server to put it on. But it's the same error as before.
Also, I changed the name of my 'Laptop' to something else and it connected ok. Although this is a temporary solution it's a bit of an annoyance and also just down-right frustrating that there is nothing else different! I would really like to figure out how to fix this so that I don't keep doing the same thing.
Plus when I try to connect to the desktop over the network the connection times out - must I setup a guest account or something?
Cheers,
Jason
April 2, 2007 at 8:37 am
Sorry but I don't have time to troubleshoot this one for you... I hope Steve can spare a few minutes for this one...
April 3, 2007 at 12:07 pm
perhaps you can find some indication of the error in the windows event logs (searching on sql server).
Start->execute->eventvwr
April 3, 2007 at 10:44 pm
When you install MSDE engine the network protocols are disabled by default. You need to run SVRNETCN and enable TCP/IP before external devices can talk to your database.
Barry
April 4, 2007 at 12:14 am
Sorry - i forgot. if you are running XP with the firewall on you will also need to enable port 1433.
Barry
April 13, 2007 at 8:35 pm
If you are using SQL Server 2005 and connecting remotely, you must enable remote connections in the Surface Area Configuration Manager. Also, try creating a SQL Account with permissions on the server you want to connect to and use that account in the data source. If you are trying to connect through a custom .NET program, then you will have to set the timeout property in there.
April 16, 2007 at 5:51 am
"when I try to connect to the desktop over the network the connection times out - must I setup a guest account or something?"
What do you mean ? Before you try to connect to the Db make sure you can connect to the desktop. Can you ping the other computer ?
Viewing 11 posts - 1 through 10 (of 10 total)
You must be logged in to reply to this topic. Login to reply