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.

 All Forums
 SQL Server 2000 Forums
 MSDE (2000)
 Can't connect to SQL server

Author  Topic 

fusionman
Starting Member

5 Posts

Posted - 2003-02-10 : 10:44:43
Hi all,

I am a newbie to the world of sql... We have a network consisting of 2 PCs. The WIN98SE PC contains the database and the MSDE 8.0 (acts as a server). The WINXP PC is the client. For days I have been trying to contact the SQL server from the WINXP PC via an application. Unfortunately no sucess. I alway get the following error message:

Module: frmUserLogin
Procedure: Command1_Click_Method
Status-Number: -2147467259
Message: [DBNETLIB][ConnectionOpen (Connect()).]Server does not exist or acess denied.()

Please be aware that this error message was translated from German. On the WIN98SE PC, the MSDE seems to run finde, due to the fact that I can open there the database via the application program.

Both PCs are linked via D-Link router. I did try ODBC and the connectivity test was positive.

Any help would be much apreciated.

Thanks in advance,

Mark


tfountain
Constraint Violating Yak Guru

491 Posts

Posted - 2003-02-10 : 13:00:32
Have you ran a trace using SQL Profiler to see if you're even hitting the database? If it is and getting denied check the login used and make sure it's a valid login that has access. If you get no trace from SP then chances are the server name and/or ODBC name supplied from the application is incorrect. If that's not the case for one reason or another, the router isn't allowing the server to be 'seen' on the network. Also, if you could supply the code being used that might provide some insight.

Go to Top of Page

fusionman
Starting Member

5 Posts

Posted - 2003-02-11 : 07:30:27
Hi tfountain,

Thanks for your reply. Unfortunately we do not have SQL Profiler. Do you know of any demo version? Microsoft descibes in 319930 a test how to verify connectivity. On our WinXP PC, this test is positive. Do you happen to know if the application registers the server name and/or ODBC name in the Windows registry? Good point on the router... Any idea how I can test that? Furthermore, what code can I supply to provide more insight and where do I find it?

Thanks again,

Mark

Go to Top of Page

Doug G
Constraint Violating Yak Guru

331 Posts

Posted - 2003-02-11 : 17:32:30
You probably need to connect using TCP/IP. W9x computers don't support named pipes. Somewhere in the MS Knowledgebase there is an article on how to configure MSDE1.0 to use TCP/IP on W9x computers. I assume the same limitation will apply to MSDE2000 on W9x computers.




======
Doug G
======
Go to Top of Page

fusionman
Starting Member

5 Posts

Posted - 2003-02-12 : 02:51:42
Hi Doug,

Thanks for your posting. We are actually connecting via TCP/IP. In the mean time I checked the error logs and guess what... Super Socket Info: Bind failed on TCP port 1433. Going through a couple of postings and Microsoft articles, I suspect that another program is using port 1433 before SQL server does. Unfortunately I don't know of any way how to check which application is using this port. I did try netstat -an but it only comes up for a split second and disappears again. No luck with portmon.exe either, only shows a blank screen...

Any ideas?

Mark

Go to Top of Page
   

- Advertisement -