Firewalls and Sql Server
-
As you may recall from yesterday, my dlink firewall died yesterday and was replaced. The default firewall settings lock everything down nicely. However, running Sql Server Management Studio 2005, I can now no longer connect to the db on my hosting company's server. Conversations with them and Google indicate that TCP port 1433 needs to be opened in both directions, which I've done, but still no connection to the remote db. Anyone fought this battle and won? It's been 6 years since I set this up on the old firewall, and I've slept since then.
Christopher Duncan www.PracticalUSA.com Author of The Career Programmer and Unite the Tribes Got a career question? Ask the Attack Chihuahua!
-
As you may recall from yesterday, my dlink firewall died yesterday and was replaced. The default firewall settings lock everything down nicely. However, running Sql Server Management Studio 2005, I can now no longer connect to the db on my hosting company's server. Conversations with them and Google indicate that TCP port 1433 needs to be opened in both directions, which I've done, but still no connection to the remote db. Anyone fought this battle and won? It's been 6 years since I set this up on the old firewall, and I've slept since then.
Christopher Duncan www.PracticalUSA.com Author of The Career Programmer and Unite the Tribes Got a career question? Ask the Attack Chihuahua!
Christopher Duncan wrote:
TCP port 1433 needs to be opened in both directions, which I've done
No, it only needs to be open outbound (from you to the SQL Server). Have you made sure that the SQL Server is listening on port 1433? What connection protocol are you using?
-
As you may recall from yesterday, my dlink firewall died yesterday and was replaced. The default firewall settings lock everything down nicely. However, running Sql Server Management Studio 2005, I can now no longer connect to the db on my hosting company's server. Conversations with them and Google indicate that TCP port 1433 needs to be opened in both directions, which I've done, but still no connection to the remote db. Anyone fought this battle and won? It's been 6 years since I set this up on the old firewall, and I've slept since then.
Christopher Duncan www.PracticalUSA.com Author of The Career Programmer and Unite the Tribes Got a career question? Ask the Attack Chihuahua!
Open SQL Server Config Manager, selection SQL Native Client Config->Client Protocols and make sure TCP/IP is enabled.
:..::. Douglas H. Troy ::..
Bad Astronomy |VCF|wxWidgets|WTL -
Christopher Duncan wrote:
TCP port 1433 needs to be opened in both directions, which I've done
No, it only needs to be open outbound (from you to the SQL Server). Have you made sure that the SQL Server is listening on port 1433? What connection protocol are you using?
Yeah, I talked to my support guys and they're listening on 1433. This was all working before I had to replace the firewall.
Christopher Duncan www.PracticalUSA.com Author of The Career Programmer and Unite the Tribes Got a career question? Ask the Attack Chihuahua!
-
Open SQL Server Config Manager, selection SQL Native Client Config->Client Protocols and make sure TCP/IP is enabled.
:..::. Douglas H. Troy ::..
Bad Astronomy |VCF|wxWidgets|WTLThis was all working before I had to replace the firewall, so none of that has changed.
Christopher Duncan www.PracticalUSA.com Author of The Career Programmer and Unite the Tribes Got a career question? Ask the Attack Chihuahua!
-
This was all working before I had to replace the firewall, so none of that has changed.
Christopher Duncan www.PracticalUSA.com Author of The Career Programmer and Unite the Tribes Got a career question? Ask the Attack Chihuahua!
Well then, obviously that's not it. :rolleyes: Check your firewall logs, see what's being blocked?
:..::. Douglas H. Troy ::..
Bad Astronomy |VCF|wxWidgets|WTL -
This was all working before I had to replace the firewall, so none of that has changed.
Christopher Duncan www.PracticalUSA.com Author of The Career Programmer and Unite the Tribes Got a career question? Ask the Attack Chihuahua!
But are you connecting using TCP/IP. You can also connect to an SQL Server using named pipes. If the old firewall wasn't blocking NetBIOS traffic, and the new one is, that would explain your symptoms. The first thing to check is that you are connecting using the TCP protocol (and the second is to see what the firewall logs say about blocked traffic).
-
As you may recall from yesterday, my dlink firewall died yesterday and was replaced. The default firewall settings lock everything down nicely. However, running Sql Server Management Studio 2005, I can now no longer connect to the db on my hosting company's server. Conversations with them and Google indicate that TCP port 1433 needs to be opened in both directions, which I've done, but still no connection to the remote db. Anyone fought this battle and won? It's been 6 years since I set this up on the old firewall, and I've slept since then.
Christopher Duncan www.PracticalUSA.com Author of The Career Programmer and Unite the Tribes Got a career question? Ask the Attack Chihuahua!
Ummm...I missed yesterday's post. have you done a trace route to be sure you are getting to the SQL Server?
"My interest is in the future because I'm going to spend the rest of my life there." - Charles F. Kettering
-
As you may recall from yesterday, my dlink firewall died yesterday and was replaced. The default firewall settings lock everything down nicely. However, running Sql Server Management Studio 2005, I can now no longer connect to the db on my hosting company's server. Conversations with them and Google indicate that TCP port 1433 needs to be opened in both directions, which I've done, but still no connection to the remote db. Anyone fought this battle and won? It's been 6 years since I set this up on the old firewall, and I've slept since then.
Christopher Duncan www.PracticalUSA.com Author of The Career Programmer and Unite the Tribes Got a career question? Ask the Attack Chihuahua!
Definitely check your firewall logs. On SQL2005, port 1433 is used for the SQL Browser process but may not apply to the instance itself. Port 1434 is another common SQL Server port for the default instance; named instances typically use a randomly-assigned port number. Ed