December 19, 2007 at 11:49 pm
I have 2 - XP SP2 computers in a LAN network. Both computers can connect to each other as described below. For troubleshooting purposes, I turned off both computer's windows firewalls.
Computer1: Server
1. Can ping computer2.
2. Can remote computer2 using remote desktop.
3. SQL Server port number is verified as default, 1433 and is confirmed to listen to port 1433.
4. Using ODBC connection, my client program, installed locally, can connect to the SQL server.
Computer2: Client
1. Can ping computer1.
2. Can remote computer1 using remote desktop.
4. Using ODBC connection, my client program, installed locally, cannot connect to the SQL server on Computer1.
Error message:
Connection Failed:
SQLState:'01000'
SQL Server Error: 10061
[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]ConnectionOpen(Connect())
Connection failed:
SQLState:'08001'
SQL Server Error: 17
[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]SQL Server does not exist or access denied.
Can anybody tell me what is preventing Computer1 from accessing SQL Server From Computer1?
Thank you very much. Your help will be ggreatly appreciated.
Erick
December 21, 2007 at 7:40 pm
Not sure if this will help or not. I had a somewhat similar issue trying to access data between a data collection application on 1 server and the reporting application on another server.
I checked all of my ODBC settings and protocols and was still getting permission denied errors.
My final solution was too basic that it took me 2 days to realize it.
What I ended up finding was the the system service account on my domain controller (with the reporting app) did not have "local" administrator rights on the 2nd application server. With my report application the service account was not allowed to have domain administrator permissions.
As soon as I added the service account to the local admin group on the 2nd server, the report app was able to retrieve the data perfectly.
BTW we had just upgraded the hardware and O.S. from W2K server to W2003R2 server.
Scott.
December 22, 2007 at 3:16 pm
If you installed express, by default it doesn't take remote connections, only local ones. Might not be listening on a TCP port. Check the SQL error log to see if it is listening when it starts up.
December 25, 2007 at 5:23 pm
Hello guys,
Thanks for all your replies. I finally solved the problem after so many attempts at changing and tweaking all settings, nothing of which helps. The solution, although I'm not so sure how it works, is just to update my SQL Server 2000 to sp4.
This may seem embarrassing since this should be the very basic thing to do but there are other installations that I've performed wherein I did not apply any service pack updates and the connections were fine.
However, I thank you for your help. This just shows that I am very fortunate in joining this forum cause everybody helps.
Erick
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply