I have three boxes: a web server running windows 2003, a database server
running Windows 2000 and sql server 7 and another database server running
windows 2003 and sql server 2000 (with sp4). The sql 2000 box is a
replacement for the sql 7 box. The web server is in the DMZ while the
database servers are in our internal network.
The web server can get through our firewall to the sql 7 box with no issues.
However, when we try connecting from the web server to the sql 2000 box, we
keep getting 'Error establishing socket. Connection Refused' messages.
The firewall rules for the sql 7 and sql 2000 boxes are the same. I have
also reviewed the TCP/IP settings suggested in other posts but have still
come up with nothing. Have I overlooked something else?Check the "Server Network Configuration" to find out whether "TCP-IP"
protocol has been added.
"Mike Smith" wrote:
> I have three boxes: a web server running windows 2003, a database server
> running Windows 2000 and sql server 7 and another database server running
> windows 2003 and sql server 2000 (with sp4). The sql 2000 box is a
> replacement for the sql 7 box. The web server is in the DMZ while the
> database servers are in our internal network.
> The web server can get through our firewall to the sql 7 box with no issue
s.
> However, when we try connecting from the web server to the sql 2000 box, w
e
> keep getting 'Error establishing socket. Connection Refused' messages.
> The firewall rules for the sql 7 and sql 2000 boxes are the same. I have
> also reviewed the TCP/IP settings suggested in other posts but have still
> come up with nothing. Have I overlooked something else?|||TCP-IP is the only protocol enabled.
"Jason Lu" wrote:
[vbcol=seagreen]
> Check the "Server Network Configuration" to find out whether "TCP-IP"
> protocol has been added.
> "Mike Smith" wrote:
>
No comments:
Post a Comment