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 |
|
CanadaDBA
583 Posts |
 Posted - 2005-07-19 : 15:20:33
|
| I have three instance of SQL Server on my test server. One is the default and the others are A and B. The default instance is using port 1433, the A port 4354 and the B is using 3537. From my computer I can connect to both default and A using the EM or QA. But I cannot connect to the instance B. I am using sa and even changed the sa password on the insance B but still I have deficulty to connect. Is it related to the port number?I have tried both IP and Machine Name but no progress.It says SQL Server does not exist or access denied.Any idea?Thanks,Canada DBA |
|
|
mcrowley
Aged Yak Warrior
771 Posts |
Posted - 2005-07-19 : 15:23:53
|
| Any firewalls between you and your server? Or any other device that would be filtering packets (VPN switches)? One test you could try is to telnet to that port, and see if you get a valid connection, even if SQL Server won't really know what to do with the connection. I would not suggest this trick on a running production SQL Server, but it should be OK for a brand new setup, or a test server. |
 |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2005-07-19 : 15:25:11
|
| You need to add an alias via Client Network Utility which can be found in the Microsoft SQL Server program group. Go to the alias tab. This is done on your client machine. Server alias is the name that you will be referring to on your client machine. Select TCP/IP. Server name can be the name of the server or the IP address. Uncheck the dynamic port option and specify which port to use for this alias.Tara |
|
|
|
CanadaDBA
583 Posts |
Posted - 2005-07-19 : 16:07:39
|
| Tara, you are really The Wonder Woman!!Thank you!Canada DBA |
|
|
|
|
|
|
Connect to an instance of SQL Server