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 |
|
c567591
Starting Member
8 Posts |
 Posted - 2006-02-23 : 14:39:36
|
| I need help connecting to SQL server 2000 on another computer.One is a IIS Web server, the other is the SQL Server.Both Servers are Win2003 Standard, they are set on the same domain and can see each other just fine via windows. They can ping each other.SP4 has been applied to SQL 2000, Win2003 are patched to current.The error I get is the following:C:\Documents and Settings\administrator.DOMAIN>isql -U sa -P sa -S database1\sql2000DB-Library: Unable to connect: SQL Server is unavailable or does not exist. Unable to connect: SQL Server does not exist or network access denied.Net-Library error 1265: ConnectionOpen (Connect()).I know sa for pass is bad, and will be changed once I can get communications going.I get a blinking prompt if I telnet to port 1433 on the SQLServer while it is running. I get a connection error "Could not open connection to the host" if the service is not running. (I saw this as a troubleshooting step) This seems to indicate it is working.On the SQLServer itself, it can connect w. EM or whatever just fine. It seems to be remote connections not working.The Win2003 firewall is not running, there are no other firewalls active. As I can telnet to the port 1433, that seems to rule that out as well.I'm not sure what else to add, I'm about at my wits end with these systems. I've never run into this problem with connecting to SQL Server, I've set it up many times before.Help me please! |
|
|
c567591
Starting Member
8 Posts |
Posted - 2006-02-23 : 14:58:13
|
| I thought of some other things to add as well.On the SQL Server, I can connect to the DB via: DATABASE1\SQL2000 but if I try by ip: 192.168.0.105\SQL2000 again on the SQL Server, it fails.This seems odd to me since it works by name, and that I can telnet to the port via IP.I'm going to be bald by the end of the week at this rate. This machine is driving me nuts. |
 |
|
|
c567591
Starting Member
8 Posts |
Posted - 2006-02-23 : 18:05:55
|
| Woot!I think I found it finally!In Q318432 now BUG #: 356696 (SHILOH_BUGS)BUG: Cannot Connect to a Clustered Named Instance Through a FirewallThe key bit:Specify the TCP port number in the connection string. For example, if your virtual SQL Server server is named VSERVER1, and it is listening on TCP/IP port number 2433, your connection string will contain the following attributes:Data Source=VSERVER1\instancename,2433;This worked for me, it did not exactly solve my problem, which I'd still like to solve, but I can at least use the server now.The other solution that MS presented that I did not try was:Create a SQL Server alias on each client by using the Client Network Utility. In the alias, specify the Net-Library to use (TCP/IP), and the port number. Use this alias in your connection string, and do not specify the Network Library attribute in your connection string. |
|
|
|
|
|
|
|
|
Help connecting to SQL on another server