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.
| Author |
Topic |
|
deji
Starting Member
2 Posts |
 Posted - 2002-03-29 : 15:02:59
|
| We have a cluster of 2 SQL 2000 servers. We have a problem whereby TCP/IPconnections to the cluster fails for anyone from anywhere. Netstat does notlist port 1433 as one of the ports being listened on. This happen on eitherof the server.We have both TCP/IP and Named Pipe in both Nework and Client utility.Connections by name have no problem. Just can't do by IP. Even on theindividual servers themselves, anyODBC connection test fails with "SQL server error: 10061". The errorlog shows something like "Bind Failed (or Failed to bind) on port 1433"Could anyone please point us in the right directions.ThanksDejiEdited by - deji on 03/29/2002 15:05:14 |
|
|
AjarnMark
SQL Slashing Gunting Master
3246 Posts |
Posted - 2002-03-29 : 18:45:26
|
| Well... if you have the SQL Client Network Utility installed, then why do you care about connecting by IP instead of name?------------------------GENERAL-ly speaking... |
 |
|
|
deji
Starting Member
2 Posts |
Posted - 2002-03-29 : 19:30:34
|
| I don't understand your reasoning, but thanks anyway.I care about whether they connect by name or IP BECAUSE there are custom applications that make TCP socket connections to the SQL. They connect by IP, not name.Again, thanks for the response.Deji |
|
|
|
|
|
|
SQL not listening on port 1433