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]
Showing posts with label register. Show all posts
Showing posts with label register. Show all posts
Friday, February 24, 2012
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]
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]
Subscribe to:
Posts (Atom)