Failed Connection to SQL Srvr 2005

(newbie here)
I'm unable to create a DSN to connect to my instance of SQL Server 2005
running on my Domain Server (Windows Srv 2003).
I'm running the Developer edition. I can create a DSN on the server itself
(so local connections work) but cannot from another machine on the LAN
(Windows XP pro).
I am also running SQL 2000 on the same server and can successfully connect
from other workstations so the LAN connection is good. The SQL 2000
({servername})is the default instance and the SQL 2005 is the named ins
tance
({servername}/{servername}_2005).
Okay, I've done my homework including trying everything suggested here as
well as MS Knowledgebase and of cource my reference books on srv 2005 (enabl
e
TCP/IP, set as dynamic port etc. I've tested with the server's firewall
turned off but nothing works)
I have installed the same SQL 2005 (developer) on a workstation (Windows XP
pro) and can connect to this instance from other computers on the LAN
(connections work).
What am I doing wrong? Could it be that SQL 2005 does not run on a Domain
Controller? If so, is there a setting or other work around? What is it about
the Domain Controller that is stopping other computers from seeing the serve
r
2005?Ah, why are you creating a DSN at all and why are you using ODBC? If you're
(still) using COM-based ADO you should be using the native SQLOLEDB provider
for SQL Server--it does not require a registered DSN. If you're using
ADO.NET you should be using the SqlClient provider.
Okay, let's assume that there is a good reason to do so. Understand that SQL
Server has been configured for some time now to be invisible to the network
(local and WAN). The server must be reconfigured to open ports and enable
protocols and the SQLBrowser service must be started to get connected. See
Chapter 9 of my book for details and a step-by-step set of instructions.
There is also a long topic on my blog about these issues.
hth
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
INETA Speaker
www.betav.com/blog/billva
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
Visit www.hitchhikerguides.net to get more information on my latest book:
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
----
---
"Carl K." <CarlK@.discussions.microsoft.com> wrote in message
news:AE3C5773-D862-449D-AD7A-8649AC58A0C9@.microsoft.com...
> (newbie here)
> I'm unable to create a DSN to connect to my instance of SQL Server 2005
> running on my Domain Server (Windows Srv 2003).
> I'm running the Developer edition. I can create a DSN on the server itself
> (so local connections work) but cannot from another machine on the LAN
> (Windows XP pro).
> I am also running SQL 2000 on the same server and can successfully connect
> from other workstations so the LAN connection is good. The SQL 2000
> ({servername})is the default instance and the SQL 2005 is the named
> instance
> ({servername}/{servername}_2005).
> Okay, I've done my homework including trying everything suggested here as
> well as MS Knowledgebase and of cource my reference books on srv 2005
> (enable
> TCP/IP, set as dynamic port etc. I've tested with the server's firewall
> turned off but nothing works)
> I have installed the same SQL 2005 (developer) on a workstation (Windows
> XP
> pro) and can connect to this instance from other computers on the LAN
> (connections work).
> What am I doing wrong? Could it be that SQL 2005 does not run on a Domain
> Controller? If so, is there a setting or other work around? What is it
> about
> the Domain Controller that is stopping other computers from seeing the
> server
> 2005?
>|||Ahh... I've got it working now. 2 things I was doing wrong. First I did not
have SQLBrowser running. Next (but less obvious) when DSN, by default, was
configured to dynamically determine the port. When I set this (the DSN set u
p
on the client machine) to port 1433 - shazaam - it worked.
I don't quite understand the port issue though. On the server (Server Config
Manager), the TCP/IP protocol has the TCP Dynamic Ports set to 0 (zero -
which should be dynamic)
To explain the use of DSN, I have an Access application which uses tables
linked from SQL via ODBC. I have a range of clients, some who have SQL 2000
and others who are migrating to SQL 2005. My app uses bound forms so the
linked tables is my only option.
I have plans to upgrade the app to VB.net but that is another story.
"William (Bill) Vaughn" wrote:

> Ah, why are you creating a DSN at all and why are you using ODBC? If you'r
e
> (still) using COM-based ADO you should be using the native SQLOLEDB provid
er
> for SQL Server--it does not require a registered DSN. If you're using
> ADO.NET you should be using the SqlClient provider.
> Okay, let's assume that there is a good reason to do so. Understand that S
QL
> Server has been configured for some time now to be invisible to the networ
k
> (local and WAN). The server must be reconfigured to open ports and enable
> protocols and the SQLBrowser service must be started to get connected. See
> Chapter 9 of my book for details and a step-by-step set of instructions.
> There is also a long topic on my blog about these issues.
> hth
> --
> ____________________________________
> William (Bill) Vaughn
> Author, Mentor, Consultant
> Microsoft MVP
> INETA Speaker
> www.betav.com/blog/billva
> www.betav.com
> Please reply only to the newsgroup so that others can benefit.
> This posting is provided "AS IS" with no warranties, and confers no rights
.
> __________________________________
> Visit www.hitchhikerguides.net to get more information on my latest book:
> Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
> and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
> ----
---
> "Carl K." <CarlK@.discussions.microsoft.com> wrote in message
> news:AE3C5773-D862-449D-AD7A-8649AC58A0C9@.microsoft.com...
>
>