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

Cannot connect to SQL Server or MSDE when enable ICF

Hi,
I enable Internet Connection Firewall (ICF) on my machine (WinXP SP1). I have installed both MSDE and SQL server on my machine, while I test my application from another machine my App cannot connect to my machine. Then I think the problem is because the I
CF.
Is there anyone know how to configure the port for SQL server or MSDE?
Cheer,
KPH
Hi,
when you look in the properties of your server there you can see the port,
the server is using.
I dont know if the icf can be configured so that a special port is open.
Perhaps you should use zonealarm for this or an other firewall which can be
more configured.
Or disable the icf, if possible.
I think the standardport is 1433.
Regards
Alexander
"KPH" <KPH@.discussions.microsoft.com> schrieb im Newsbeitrag
news:2D296E26-38B1-48A4-8414-9D8C84A366C7@.microsoft.com...
> Hi,
> I enable Internet Connection Firewall (ICF) on my machine (WinXP SP1). I
have installed both MSDE and SQL server on my machine, while I test my
application from another machine my App cannot connect to my machine. Then I
think the problem is because the ICF.
> Is there anyone know how to configure the port for SQL server or MSDE?
> Cheer,
> KPH

Cannot connect to SQL Server or MSDE when enable ICF

Hi,
I enable Internet Connection Firewall (ICF) on my machine (WinXP SP1). I have installed both MSDE and SQL server on my machine, while I test my application from another machine my App cannot connect to my machine. Then I think the problem is because the ICF.
Is there anyone know how to configure the port for SQL server or MSDE?
Cheer,
KPHHi,
when you look in the properties of your server there you can see the port,
the server is using.
I don´t know if the icf can be configured so that a special port is open.
Perhaps you should use zonealarm for this or an other firewall which can be
more configured.
Or disable the icf, if possible.
I think the standardport is 1433.
Regards
Alexander
"KPH" <KPH@.discussions.microsoft.com> schrieb im Newsbeitrag
news:2D296E26-38B1-48A4-8414-9D8C84A366C7@.microsoft.com...
> Hi,
> I enable Internet Connection Firewall (ICF) on my machine (WinXP SP1). I
have installed both MSDE and SQL server on my machine, while I test my
application from another machine my App cannot connect to my machine. Then I
think the problem is because the ICF.
> Is there anyone know how to configure the port for SQL server or MSDE?
> Cheer,
> KPH

Cannot connect to SQL Server or MSDE when enable ICF

Hi,
I enable Internet Connection Firewall (ICF) on my machine (WinXP SP1). I hav
e installed both MSDE and SQL server on my machine, while I test my applicat
ion from another machine my App cannot connect to my machine. Then I think t
he problem is because the I
CF.
Is there anyone know how to configure the port for SQL server or MSDE?
Cheer,
KPHHi,
when you look in the properties of your server there you can see the port,
the server is using.
I dont know if the icf can be configured so that a special port is open.
Perhaps you should use zonealarm for this or an other firewall which can be
more configured.
Or disable the icf, if possible.
I think the standardport is 1433.
Regards
Alexander
"KPH" <KPH@.discussions.microsoft.com> schrieb im Newsbeitrag
news:2D296E26-38B1-48A4-8414-9D8C84A366C7@.microsoft.com...
> Hi,
> I enable Internet Connection Firewall (ICF) on my machine (WinXP SP1). I
have installed both MSDE and SQL server on my machine, while I test my
application from another machine my App cannot connect to my machine. Then I
think the problem is because the ICF.
> Is there anyone know how to configure the port for SQL server or MSDE?
> Cheer,
> KPH

Cannot connect to SQL server behind firewall

I'm using SQL server enterprise manager to try and register to the SQL serve
r, however since I'm behind a firewall, I cannot connect to it and it says t
imeout expires. I just checked and the ports on 1433 and 1434 are opened on
the firewall. I also try
to connect without the firewall and everything works fine. Any ideas as to
what could cause this?
Thanks,
Alan"Alan" <Alan@.discussions.microsoft.com> wrote in message
news:CA29961F-76B2-4CEE-98F8-888AF56366D8@.microsoft.com...
> I'm using SQL server enterprise manager to try and register to the SQL
server, however since I'm behind a firewall, I cannot connect to it and it
says timeout expires. I just checked and the ports on 1433 and 1434 are
opened on the firewall. I also try to connect without the firewall and
everything works fine. Any ideas as to what could cause this?
>
It might be that you are making the connection (inbound) to SQL Server, but
the outbound connection never completes.
http://support.microsoft.com/defaul...2&Product=sql2k
You could also try substituting the IP address instead of the server name to
rule out any name resolution issues.
Steve|||I did use the IP address instead of the server name.
What do you mean by the outbound connection never completes. How do I fix t
hat? I read the page you posted already and I did try to make the port 1433
to *any* open, however still timeout expired.
Confused?
"Steve Thompson" wrote:

> "Alan" <Alan@.discussions.microsoft.com> wrote in message
> news:CA29961F-76B2-4CEE-98F8-888AF56366D8@.microsoft.com...
> server, however since I'm behind a firewall, I cannot connect to it and it
> says timeout expires. I just checked and the ports on 1433 and 1434 are
> opened on the firewall. I also try to connect without the firewall and
> everything works fine. Any ideas as to what could cause this?
> It might be that you are making the connection (inbound) to SQL Server, bu
t
> the outbound connection never completes.
> [url]http://support.microsoft.com/default.aspx?scid=kb;en-us;287932&Product=sql2k[/ur
l]
> You could also try substituting the IP address instead of the server name
to
> rule out any name resolution issues.
> Steve
>
>|||Is the instance of the SQL Server using port 1433?
"Alan" wrote:
[vbcol=seagreen]
> I did use the IP address instead of the server name.
> What do you mean by the outbound connection never completes. How do I fix
that? I read the page you posted already and I did try to make the port 14
33 to *any* open, however still timeout expired.
> Confused?
>
> "Steve Thompson" wrote:
>|||It's hard to say without knowing your configuration. This is likely one of
those times where a network trace (esp: from the SQL Server perspective)
would help. If you do not have access to the network monitor included with
SMS, check out Etheral http://www.ethereal.com/
Steve
"Alan" <Alan@.discussions.microsoft.com> wrote in message
news:F71E4436-5090-48B0-87A3-C5BC6B9D4E8A@.microsoft.com...
> I did use the IP address instead of the server name.
> What do you mean by the outbound connection never completes. How do I fix
that? I read the page you posted already and I did try to make the port
1433 to *any* open, however still timeout expired.[vbcol=seagreen]
> Confused?
>
> "Steve Thompson" wrote:
>
it[vbcol=seagreen]
but[vbcol=seagreen]
http://support.microsoft.com/defaul...2&Product=sql2k[vbcol=seagreen]
name to[vbcol=seagreen]

Cannot connect to SQL server behind firewall

I'm using SQL server enterprise manager to try and register to the SQL server, however since I'm behind a firewall, I cannot connect to it and it says timeout expires. I just checked and the ports on 1433 and 1434 are opened on the firewall. I also try
to connect without the firewall and everything works fine. Any ideas as to what could cause this?
Thanks,
Alan
"Alan" <Alan@.discussions.microsoft.com> wrote in message
news:CA29961F-76B2-4CEE-98F8-888AF56366D8@.microsoft.com...
> I'm using SQL server enterprise manager to try and register to the SQL
server, however since I'm behind a firewall, I cannot connect to it and it
says timeout expires. I just checked and the ports on 1433 and 1434 are
opened on the firewall. I also try to connect without the firewall and
everything works fine. Any ideas as to what could cause this?
>
It might be that you are making the connection (inbound) to SQL Server, but
the outbound connection never completes.
http://support.microsoft.com/default...&Product=sql2k
You could also try substituting the IP address instead of the server name to
rule out any name resolution issues.
Steve
|||I did use the IP address instead of the server name.
What do you mean by the outbound connection never completes. How do I fix that? I read the page you posted already and I did try to make the port 1433 to *any* open, however still timeout expired.
Confused?
"Steve Thompson" wrote:

> "Alan" <Alan@.discussions.microsoft.com> wrote in message
> news:CA29961F-76B2-4CEE-98F8-888AF56366D8@.microsoft.com...
> server, however since I'm behind a firewall, I cannot connect to it and it
> says timeout expires. I just checked and the ports on 1433 and 1434 are
> opened on the firewall. I also try to connect without the firewall and
> everything works fine. Any ideas as to what could cause this?
> It might be that you are making the connection (inbound) to SQL Server, but
> the outbound connection never completes.
> http://support.microsoft.com/default...&Product=sql2k
> You could also try substituting the IP address instead of the server name to
> rule out any name resolution issues.
> Steve
>
>
|||Is the instance of the SQL Server using port 1433?
"Alan" wrote:
[vbcol=seagreen]
> I did use the IP address instead of the server name.
> What do you mean by the outbound connection never completes. How do I fix that? I read the page you posted already and I did try to make the port 1433 to *any* open, however still timeout expired.
> Confused?
>
> "Steve Thompson" wrote:
|||It's hard to say without knowing your configuration. This is likely one of
those times where a network trace (esp: from the SQL Server perspective)
would help. If you do not have access to the network monitor included with
SMS, check out Etheral http://www.ethereal.com/
Steve
"Alan" <Alan@.discussions.microsoft.com> wrote in message
news:F71E4436-5090-48B0-87A3-C5BC6B9D4E8A@.microsoft.com...
> I did use the IP address instead of the server name.
> What do you mean by the outbound connection never completes. How do I fix
that? I read the page you posted already and I did try to make the port
1433 to *any* open, however still timeout expired.[vbcol=seagreen]
> Confused?
>
> "Steve Thompson" wrote:
it[vbcol=seagreen]
but[vbcol=seagreen]
http://support.microsoft.com/default...&Product=sql2k[vbcol=seagreen]
name to[vbcol=seagreen]