"Sue Hoegemeier" wrote:

> Yes other computers can connect to Developers Edition. There
> are no limitations of not being able to connect from other
> computers just because it's developer's edition
> If you can't telnet to the port, it may not be listening on
> that port. If it's a named instance, you need to specify the
> instance name. When trying to telnet, you need to check the
> port SQL Server is listening on and telnet to that port.
> Make sure SQL Server is listening on the correct protocols
> as well. Make sure you have TCP/IP enabled.
> You can check the SQL Server error log from when it started
> up to determine what ports and protocols SQL Server is
> listening on.
> For more information, refer to the following troubleshooting
> article:
> Potential causes of the "SQL Server does not exist or access
> denied" error message
> http://support.microsoft.com/?id=328306
>
> -Sue
>
> On Sat, 29 Oct 2005 21:53:02 -0700, "jlp3630"
> <jlp3630@discussions.microsoft.com> wrote:
>
> >Does SQL Server 2000 Personal Edition or SQL Server 2000 Developer Edition
> >have connection limitations compared to SQL Server 2000 Enterprise Edition?
> >Specifically, should a database running SQL Server 2000 Developer's Edition
> >(or Personal Edition) on a Windows XP Professional SP2 computer be accessible
> >from another computer? I am familiar with the following article, which
> >explains the differences between the different SQL Server editions:
> >
> >http://download.microsoft.com/download/8/1/7/817bb6e6-9d97-4a5d-be8d-
> >508256ae4045/ChoosEd.doc
> >
> >I wrote some C# code to access an identical database on 3 different
> >computers (specifically Computer A, Computer B, Server A described below).
> >When I try to open the connection from Computer A to Computer B in my code,
> >it returns an error stating that the connection can not be opened. This also
> >occurs when I run my code on Computer B and access the database on Computer
> >A. However, my code executing on Computer A can
> >access Server A, and my code executing on Computer B can access Server A.
> >(The only change I made to the code involved the name of the data source:
> >[Computer A's Name], [Computer B's Name], [Server A's Name]).
> >
> >Here is my current computer setup:
> >
> >Computer A: Windows XP SP2 with SQL Server 2000 Personal Edition (firewall
> >turned off)
> >Computer B: Windows XP SP2 with SQL Server 2000 Developer Edition (firewall
> >turned off)
> >Server A: Windows 2003 Server Enterprise Edition with SQL Server 2000
> >Enterprise Edition
> >
> >Using Enterprise Manager on Computer A, I can successfully add Computer A.
> >On the other hand, I could not add Computer B's SQL Server via Computer A's
> >Enterprise Manager "New SQL Server Registration" Command (Right click Sql
> >Server Group -> New SQL Server Registration -> [Computer B's name] -> [Enter
> >appropriate SQL Server Registration Information]). I receive the following
> >error:
> >
> >Computer_A - SQL Server does not exist or access denied. ConnectionOpen
> >(Connect())
> >
> >I've tried typing the following lines at the command prompt (which should
> >return a blank screen if successful):
> >
> >1. telnet Computer_b's_name 1433
> >2. telnet Computer_b's_IP_Address 1433
> >
> >This returns the error "Could not open connection to the host, on port 1433:
> >Connect failed". I am able to successfully ping Computer B from Computer A.
> >
> >Attempting to access Computer A from Computer B, I tried the same tests
> >(using Enterprise Manager and telnet) and received the same problematic
> >results. I am able to successfully ping Computer A from Computer B.
> >
> >However, using Computer A to access Server A via Enterprise Manager and
> >telnet works fine. Additionally, using Computer B to access Server A via
> >Enterprise manager and telnet works fine. I am able to ping Server A from
> >both Computer A and Computer B.
> >
> >I've verified that both computers are running mixed-mode authentication (by
> >checking the appropriate windows registry keys).
> >
> >I assume that my code will work if I can get either the "Enterprise
> >manager test" or "telnet test" to work.
> >
> >Any help or insight would be greatly appreciated.
> >
> >Thanks in advance,
> >Jon
>