Cannot connect with SQL Server Management Studio to SQL2K5

Hi
we are using SQL 2005 SP2 cluster with 3 instances. We are trying to connect
with SQL Server Management Studio thrue a Firewall that have only port
1433/TCP open. This has worked with SQL Auth and SQL 2000 perfectly. I also
tried to add 1433/UDP, 1434/TCP and 1434/UDP, but haven't had any success.
On the machines themself the connection is working well... i'm connecting to
the instances with server name "CLU1INS1\Instance1", "CLU1INS2\Instance2"
and "CLU1INS3\Instance3" and SQL Auth, but from remote it is not working.
What could be wrong here and how are we able to solve this problem?
Regards
MarcMarc
Do you get an error? If so , what?
"Marc Bauer" <marc.bau@.gmx.net> wrote in message
news:u06scMCXIHA.4440@.TK2MSFTNGP06.phx.gbl...
> Hi
> we are using SQL 2005 SP2 cluster with 3 instances. We are trying to
> connect with SQL Server Management Studio thrue a Firewall that have only
> port 1433/TCP open. This has worked with SQL Auth and SQL 2000 perfectly.
> I also tried to add 1433/UDP, 1434/TCP and 1434/UDP, but haven't had any
> success.
> On the machines themself the connection is working well... i'm connecting
> to the instances with server name "CLU1INS1\Instance1",
> "CLU1INS2\Instance2" and "CLU1INS3\Instance3" and SQL Auth, but from
> remote it is not working.
> What could be wrong here and how are we able to solve this problem?
>
> Regards
> Marc
>
>|||Only default instance of SQL Server (referring to it by computer's name)
uses port 1433, named instance (computerName\instanceName) uses other
port/dynamic port. You must determine which port the named SQL Server
instance uses and allow the port on the firewall.
"Marc Bauer" <marc.bau@.gmx.net> wrote in message
news:u06scMCXIHA.4440@.TK2MSFTNGP06.phx.gbl...
> Hi
> we are using SQL 2005 SP2 cluster with 3 instances. We are trying to
> connect with SQL Server Management Studio thrue a Firewall that have only
> port 1433/TCP open. This has worked with SQL Auth and SQL 2000 perfectly.
> I also tried to add 1433/UDP, 1434/TCP and 1434/UDP, but haven't had any
> success.
> On the machines themself the connection is working well... i'm connecting
> to the instances with server name "CLU1INS1\Instance1",
> "CLU1INS2\Instance2" and "CLU1INS3\Instance3" and SQL Auth, but from
> remote it is not working.
> What could be wrong here and how are we able to solve this problem?
>
> Regards
> Marc
>
>|||hi
> Only default instance of SQL Server (referring to it by computer's name)
> uses port 1433, named instance (computerName\instanceName) uses other
> port/dynamic port. You must determine which port the named SQL Server
> instance uses and allow the port on the firewall.
Ups... never heard about this... where can i change this setting? Every
instance has it's own IP... so i don't know why this should be dynamic...
Marc|||It is port, not IP Address. At the same IP address, different applications
use different ports. SQL Server's default instance uses port 1433 by
default, named instance uses different port. but you could configure it to
use whatever port you see fits. Use SQL Server's server configuration tool
to examine/set TCP/IP port used by an SQL Server instance.
"Marc Bauer" <marc.bau@.gmx.net> wrote in message
news:%23DQg3yDXIHA.4684@.TK2MSFTNGP06.phx.gbl...
> hi
>> Only default instance of SQL Server (referring to it by computer's name)
>> uses port 1433, named instance (computerName\instanceName) uses other
>> port/dynamic port. You must determine which port the named SQL Server
>> instance uses and allow the port on the firewall.
> Ups... never heard about this... where can i change this setting? Every
> instance has it's own IP... so i don't know why this should be dynamic...
>
> Marc
>|||Hi
> It is port, not IP Address. At the same IP address, different applications
Yep, i know, but i tried to understand why instances have dynamic ports...
normaly every instance need it's own IP adrress. If this is the case i can
bind 1433 to every instance without any collisions, isn't it?
> use different ports. SQL Server's default instance uses port 1433 by
> default, named instance uses different port. but you could configure it to
> use whatever port you see fits. Use SQL Server's server configuration tool
> to examine/set TCP/IP port used by an SQL Server instance.
This settings tool is somewhat strange... "0" enables dynamic ports and
"blank" disabled this... however there is a "AllIP" setting that have a
dynamic port value of 1512 (what ever this means). I switched this to blank
value and set the Port to 1433. Should this work as expected? I've only done
this on a testing system... not sure if i must configure every instance for
it's own or if there is a global setting.
Gruss
Alex