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 |
BigSam
Starting Member
30 Posts |
Posted - 2006-06-28 : 09:48:28
|
I recently installed SQL2k5 Express edition, using many of the defaults in the setup wizard. I then configured Remote Access using TCP.Using SSMS running on a different PC on the LAN I was able to connect without incident using 192.168.0.144\SQLExpress. Then I tried to connect with an application originally written for SQL 2000 – it failed. Using Network Monitor I was able to determine that SSMS was connecting on port 1543. I modified my connection string in the SQL 2000 application to use port 1543 & the connection went through. I was able to reproduce this situation with Query Analyzer (192.168.0.144,1543). In neither the SQL application nor Query Analyzer was I able to connect using 192.168.0.144\SQLExpress.Since I wanted the connection to use port 1433, I un-installed SQL2k5 & re-installed it. However, this time I chose to use the Default instance of SQL; the setup wizard defaults to installing a named instance (SQLExpress in my case). Rather than creating an instance named SQLExpress, there was no name. When I tried to connect from the other PC I found that port 1433 was working; now SSMS, my application & Query Analyzer all connect with just the IP address.I haven’t found any documentation on this. Does anyone know how to control this, or know of Microsoft documentation?Thanks,BigSam |
|
|
|
|