October 1, 2003 at 9:25 am
Help! here's background: I installed MSDE on server, then installed our software, which connects to a SQL database which I had attached. No problem with this when I installed our software on the server. However, when I installed our software on a separate workstation and tried to connect to SQL database, could not connect. Used ODBC Data Source Administrator to ensure the connection protocol was TCP/IP, didn't connect. Updated MDAC to 2.6 SP2, didn't connect. Used netstat on server and discovered that the server wasn't listening on port 1433. Also couldn't telnet to port 1433 on the server. There was a firewall on the server, so we uninstalled the firewall, uninstalled MSDE, reinstalled MSDE, and the server still wasn't listening on port 1433. Any thoughts?
Edited by - danatdatawise on 10/01/2003 09:26:01 AM
October 1, 2003 at 9:34 am
Check the netlibs that are configured. If it's not using TCP/IP, that explains. If it is, that should tell you the proper port. Since MSDe doesn't drop a handy link in Start >> Programs, the server network utility program is what you'll be looking for and you'll have to find it in the file system. The file you're looking for is: svrnetcn.exe.
Not sure about MSDE, but a typical SQL 2K install has it here:
\Program Files\Microsoft SQL Server\80\Tools\Binn
K. Brian Kelley
http://www.truthsolutions.com/
Author: Start to Finish Guide to SQL Server Performance Monitoring
K. Brian Kelley
@kbriankelley
October 1, 2003 at 9:45 am
I found and opened the server network utility, and all protocols were disabled. I enabled TCP/IP, stopped and restarted the SQL server service, and now the server is listening on port 1433. Thank you thank you thank you!
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply