ODBC DSN not Connecting
-
I am trying to connect through ODBC, using the SQL Server Driver, to an MSDE database located on an NT server. I am able to ping the server without any problem, but when trying to connect through ODBC I am getting a Connection Failed. I am using the SQL Server authentication, entering 'sa' as the login, and leaving the password blank. I am able to connect without any problem from the server itself, but not from any client machines which are all Windows 98. I have used TPC/IP and Other in the connection methods, and both fail.
If anyone has ever run across this and can shed some light on the subject, I would be happy to hear about it. Also if anyone has any debugging tricks to finding out anything out, please let me know.
Thanks!!
-
I'm assuming you are changing the connection settings on the clients... TCP/IP should work. Of course, Windows 98 doesn't support Named Pipes, which is why they have to be explicitly set to TCP/IP. One thing you might want to do is go to the command prompt on the server and type: netstat -an
See if there is an active TCP connection for the IP address of the server for port 1433.
K. Brian Kelley
http://www.sqlservercentral.com/columnists/bkelley/
K. Brian Kelley
@kbriankelley -
Just to be sure...you're using SA/blank password from the other machines as well?
Andy
-
Can you install the client tools on a workstation and see if this works?
Also, please don't use sa and blank for anything other than this test.
Steve Jones
-
Can you install the client tools on a workstation and see if this works?
Also, please don't use sa and blank for anything other than this test.
Steve Jones
-
I have been having similar problems. I try connecting from a remote machine using the ODBC Data Source Administrator and receive the following 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." This started happening shortly after I installed a new(er) patch to IE5.5 (don't know if it affected SQL Server or not!) I tried the netstat -an command and found that the port used is 2433, with Foreign Address 0.0.0.0:0, state: LISTENING. I also have the loopback address listening as well. I haven't, as yet, installed the client tools. I was told that this wasn't necessary since no "foreign" machine can access the server. Can you suggest something for me to try? Thank you.
-
Go into your Server Network Utility and see what TCP port SQL Server should be listening on. Then compare with the netstat -an. If you don't see the port in the list, check your event log to see if SQL Server had problems binding to that port. If so, stop and restart the SQL Server service.
If it's a port other than 1433, make sure you configure an ODBC connection to that server using the proper port.
K. Brian Kelley
http://www.sqlservercentral.com/columnists/bkelley/
K. Brian Kelley
@kbriankelley -
That was the problem. The server was listening to port 2433 and all connections were trying to access port 1433. I'd like to know how that got changed (I don't remember changing it; doesn't sound like something I mess with not being an expert and all!). Is there some way the system would have reconfigured the port (like port 1433 was busy or blocked during configuration)? Just curious. Suppose I should just accept it, forget it move on to the next problem.
Many thanks for your assistance!
Joe
-
I've not seen it go to a different port, though that doesn't mean it didn't happen. Glad it was as simple as that!
K. Brian Kelley
http://www.sqlservercentral.com/columnists/bkelley/
K. Brian Kelley
@kbriankelley -
1433 is the SQL Server standard as specified in an RFC. If you use something else, this is ok, but no expected behavior. AFAIK, nothing changes this except manual intervention.
Steve Jones
-
I must have had a dumb attack on this one! Usually, I log any changes in a maintenance log I keep for just these purposes. Duh!! Anyway, thank you guys for your help. One of these days, I will have enough experience to pay back with some solutions of my own, and will always remember those who got me where I am!
Much abliged!
-
Viewing 12 posts - 1 through 11 (of 11 total)
You must be logged in to reply to this topic. Login to reply