Re: SQL 200 Dev edition on workgroup will not connect

Thank you for staying with this thread. I was speaking out of frustration when I said "I can't believe this is so difficult"

I have been using sql server for about 8 years but mainly working with sql 2000. this is my first attempt at working with 2008

I checked everything you suggested and it was all setup correct. I am going to uninstall and start over with a default instance and see if that makes a difference. I don't see why it should, but it is the only thing left to try. Maybe this can't be done with a peer-to-peer setup using vista home premium and vista ultimate. I do know when I try and connect to either of the boxes using the network browser, they always ask for a username and password to log into the windows machine. Maybe that is what is happening when the Datasource setup is attempting to log in. Not sure, just stabbing in the dark.

"Ekrem Önsoy" <ekrem@xxxxxxxxxxxx> wrote in message news:%23VISF2llJHA.4396@xxxxxxxxxxxxxxxxxxxxxxx
You know, things seem difficult when we do not know about them. I do not know your experience level with SQL Server and yes, sometimes things being messy but letting a SQL Server instance to accept remote connections and uninstalling it are generally straightforward tasks to perform.

To uninstall a SQL Server instance, you go to Control Panel->Programs & Features (or Add\Remove Programs) -> Microsoft SQL Server 2008 -> Click uninstall button. So a window shows up and you click Remove and proceed. Is your story something different?

Regarding to remote connection settings, I suggest you to check for the dynamic port number that your SQL Server graps. You can do this using SQL Server Configuration Manager. Go to TCP/IP protocol' s properties and ensure the following are the same:

Protocol Tab:
Enabled = yes
Listen all = yes

IP Addresses Tab:
Go to IPAll ->
TCP Dynamic Ports = <some port number>
TCP Port = <empty>

How about these settings for your SQL Server instance's TCP/IP protocol? Write down the port number in the "TCP Dynamic Ports" property and then run a Command Prompt and see if this port is bening listened. Run the following code to see if it' s:

Netstat -a

You must see the dynamic port number in the list when you run the above command line in Command Prompt so that you'll ensure it's being listened. For it to be propogated to your clients, you must ensure that Browser Service is running. I know you already said it's running but I just want to stress it out because it's really important if you want it to work.

If you do not want to use a dynamic port for your SQL Server instance, then you can use a static port instead. Static port is being used only for a Default Instance by default. Dynamic Ports are used for Named Ports by default.

If you want your SQL Server instance to use a static port, then you need to clear any value in the TCP Dynamic Ports property and then type an available port number in the TCP Port property then restart your SQL Server. You can again use "Netstat -a" command to confirm it's running or not.

--
Ekrem Önsoy



"w" <none@xxxxxxxxxxxx> wrote in message news:eJRMwXhlJHA.4520@xxxxxxxxxxxxxxxxxxxxxxx
Thank you for the suggestions. I did find the KB article during my search for a solution and found that everything in the article I had setup correctly. I don't have virus software installed so I don't think that is causing a problem.

When I installed SQL Server I made it a Named instance. I thought that might be a problem so I was going to uninstall and start over; however, there isn't an uninstall. I can't believe this product is without an uninstall.

If you have any other suggestions, I don't know what else to do. I can't believe this is so difficult.

"Ekrem Önsoy" <ekrem@xxxxxxxxxxxx> wrote in message news:%23IRrIpYlJHA.1292@xxxxxxxxxxxxxxxxxxxxxxx
Do not enable unnecessary ports. For instance, if the priority of Named Pipes is higher than TCP/IP and your clients try to connect via TCP/IP then you may have delay problems with connections.

I suggest you to go over this KB just in case... http://support.microsoft.com/kb/914277

For further, I doubt there might be problems with your protocol settings if you have changed anything?

Is your SQL Server instance a Named Instance or a Default Instance?

Do you have an Anti-virus software installed on the SQL Server server?

--
Ekrem Önsoy



"w" <none@xxxxxxxxxxxx> wrote in message news:uzRwVyTlJHA.5732@xxxxxxxxxxxxxxxxxxxxxxx
Yes, all of that has been checked and all except via are enabled. The sql browser service is also running.


"Ekrem Önsoy" <ekrem@xxxxxxxxxxxx> wrote in message news:C80FD428-EEB6-41EA-AFAF-9C092953AEE0@xxxxxxxxxxxxxxxx
TCP/IP or Named Pipes (according to your needs) protocol needs to be enabled for the SQL Server instance for which remote users to connect and these protocols are disabled by default for SQL Server 2005' s Developer Edition and I bet it must be the default configuration for 2008' s Dev. Ed. as well.

So, I suggest you to ensure that the appropriate protocol is enabled and if it's a Named Instance (probably it is) you must ensure that Browser Service run on that server.

--
Ekrem Önsoy



"w" <none@xxxxxxxxxxxx> wrote in message news:%23llgpEMlJHA.1928@xxxxxxxxxxxxxxxxxxxxxxx
I am testing (trying to test) a simple database with a new and very generic sql 2008 dev edition install. My installed sql server is on a laptop running vista Home Premium and I have two other machines (Vista ultimate and windows XP sp3) Neither of these two machines can connect to the server through a data source because it keeps returning an error that it can't find the server. I am using "mixed mode" or SQL Authentication and have tried various different login accounts that I setup on sql server. NONE Work. I can see the laptop and access its folders so I know the connection works. Additionally, I disabled the firewall on all the machines. Still no luck. I don't know what else to try. Suggestions?






.