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 |
|
jen
Master Smack Fu Yak Hacker
4110 Posts |
 Posted - 2006-03-30 : 03:01:27
|
| i read in the ms articles that multiple instance uses dynamic ports and if you need static ports, you'll need to define in the server network utilityi did what was advised, can see that the servers are listening on their designated ports but have a major problem.Here are the scenarios:using windows authentication--> connect via tcp to instance 1 ok, but to instance 2 failed--> connect via named pipes, both okusing sql login--> both ok via tcp and named pipesanyone encountered the same scenario?TIA--------------------keeping it simple... |
|
|
mr_mist
Grunnio
1870 Posts |
Posted - 2006-03-30 : 03:15:28
|
| What's the failure message?Any firewalls involved?Different domains?-------Moo. :) |
 |
|
|
jen
Master Smack Fu Yak Hacker
4110 Posts |
Posted - 2006-03-30 : 03:18:47
|
| cannot generate the sspi context...firewall oksame domain--------------------keeping it simple... |
|
|
|
mr_mist
Grunnio
1870 Posts |
Posted - 2006-03-30 : 03:23:28
|
| It does sound like a network issue, because the required credentials are not being passed through. You could try creating a local account on the sql server to match the credientials of the windows login that you'll be using in order to act as a pass-through. Otherwise you have to do all sorts of faff with kerberos and SPNs ( http://support.microsoft.com/?id=811889 ). If you've got a firewall open specifically for SQL Server try seeing if it is blocking any authentication traffic eg ports 138,139, 445.-------Moo. :) |
|
|
|
jen
Master Smack Fu Yak Hacker
4110 Posts |
Posted - 2006-03-30 : 03:34:48
|
thanks for the link moo but that's the article i was referring toi was also considering the blocking, the other article says that if an application chooses and binds the port for a sql server instance, the problem will persist, something like first come first served (because it implies that if you restart the server and sql binds it first, no problem... atleast that's how i interpreted it  )I need to check with our firewall guys if this is the case (i've bugged them enough yesterday  )keep the ideas coming...--------------------keeping it simple... |
|
|
|
|
|
|
|
|
multiple instance, force tcp