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 |
|
acesover
Starting Member
15 Posts |
 Posted - 2011-07-26 : 15:09:57
|
| Due to newly introduced corporate security reasons, I need to run 3 instances of SQL Server 2005 on the same host computer, all on port 1433. I got this to work by doing the following:- Adding additional IP addresses to the computer, one for each instance- Configuring each instance to listen on only one of those IP addresses, each on port 1433. - Enabling Named Pipes on each instanceThe last item is the one that has me curious. If I only enable TCP/IP on the server instance, it does not work, and I'm unsure as to why. On the client side, I don't seem need to have the Named Pipes protocol enabled, which is adding further questions in my mind. Yes, it is working, but I'm trying to be as complete as I can in understanding how this solution works to overcome any other security restrictions I may come across in the future. Thanks.Dan |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
|
|
acesover
Starting Member
15 Posts |
Posted - 2011-07-26 : 16:58:45
|
| 1433 is the only port they will open on their application tier to our database server sitting in another location, so I'm stuck with that unfortunately. |
 |
|
|
acesover
Starting Member
15 Posts |
Posted - 2011-07-27 : 12:54:13
|
| I got the solution from another source. The problem was I wasn't specifying the IP address in my connection string. By doing this, and also specifying port 1433 when connecting, it is now working. I've also added an alias in the form of 'host\instance' so that from the client application perspective, the connection string can remain the same. |
|
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
|
|
|
|
|
|
|
Multiple instances on same port and Named Pipes