 | |
cluster connection issue
microsoft.public.sqlserver.clustering microsoft.public.sqlserver.clustering
 |
| | Thread Tools | Display Modes |
#1
 
| |||
| |||
|
cluster connection issue -
09-21-2008
, 05:35 AM
#2
| |||
| |||
|
|
Hi We have an application *running on an NLB cluster in the DMZ. Application data is stored on a standalone SQL 2005 Std server located not in the DMZ but inside the company's private network. *Have recently setup a 2-node SQL 2005 Std failover cluster running on Windows 2008 Ent, all 64-bit and in the process of pointing the application to it. For some reason I'm having problems connecting to the new cluster. Have tried allowing all traffic thru the firewall between dmz and trust zones but no luck. I can ping the SQL cluster as well as the standalone SQL server from the DMZ and vice versa, but can only get a successful test ODBC connection to the standalone server. Windows firewall already disabled on the SQL cluster and no antivirus is installed. Any ideas? Thanks TI |
the standalone was default...thanks in advance!
#3
| |||
| |||
|
|
Hi We have an application *running on an NLB cluster in the DMZ. Application data is stored on a standalone SQL 2005 Std server located not in the DMZ but inside the company's private network. *Have recently setup a 2-node SQL 2005 Std failover cluster running on Windows 2008 Ent, all 64-bit and in the process of pointing the application to it. For some reason I'm having problems connecting to the new cluster. Have tried allowing all traffic thru the firewall between dmz and trust zones but no luck. I can ping the SQL cluster as well as the standalone SQL server from the DMZ and vice versa, but can only get a successful test ODBC connection to the standalone server. Windows firewall already disabled on the SQL cluster and no antivirus is installed. Any ideas? Thanks TI |
the standalone was default...thanks in advance!
#4
| |||
| |||
|
|
Hi We have an application *running on an NLB cluster in the DMZ. Application data is stored on a standalone SQL 2005 Std server located not in the DMZ but inside the company's private network. *Have recently setup a 2-node SQL 2005 Std failover cluster running on Windows 2008 Ent, all 64-bit and in the process of pointing the application to it. For some reason I'm having problems connecting to the new cluster. Have tried allowing all traffic thru the firewall between dmz and trust zones but no luck. I can ping the SQL cluster as well as the standalone SQL server from the DMZ and vice versa, but can only get a successful test ODBC connection to the standalone server. Windows firewall already disabled on the SQL cluster and no antivirus is installed. Any ideas? Thanks TI |
the standalone was default...thanks in advance!
#5
| |||
| |||
|
|
Hi We have an application *running on an NLB cluster in the DMZ. Application data is stored on a standalone SQL 2005 Std server located not in the DMZ but inside the company's private network. *Have recently setup a 2-node SQL 2005 Std failover cluster running on Windows 2008 Ent, all 64-bit and in the process of pointing the application to it. For some reason I'm having problems connecting to the new cluster. Have tried allowing all traffic thru the firewall between dmz and trust zones but no luck. I can ping the SQL cluster as well as the standalone SQL server from the DMZ and vice versa, but can only get a successful test ODBC connection to the standalone server. Windows firewall already disabled on the SQL cluster and no antivirus is installed. Any ideas? Thanks TI |
the standalone was default...thanks in advance!
#6
| |||
| |||
|
|
Hi We have an application *running on an NLB cluster in the DMZ. Application data is stored on a standalone SQL 2005 Std server located not in the DMZ but inside the company's private network. *Have recently setup a 2-node SQL 2005 Std failover cluster running on Windows 2008 Ent, all 64-bit and in the process of pointing the application to it. For some reason I'm having problems connecting to the new cluster. Have tried allowing all traffic thru the firewall between dmz and trust zones but no luck. I can ping the SQL cluster as well as the standalone SQL server from the DMZ and vice versa, but can only get a successful test ODBC connection to the standalone server. Windows firewall already disabled on the SQL cluster and no antivirus is installed. Any ideas? Thanks TI |
the standalone was default...thanks in advance!
#7
| |||
| |||
|
|
Hi We have an application *running on an NLB cluster in the DMZ. Application data is stored on a standalone SQL 2005 Std server located not in the DMZ but inside the company's private network. *Have recently setup a 2-node SQL 2005 Std failover cluster running on Windows 2008 Ent, all 64-bit and in the process of pointing the application to it. For some reason I'm having problems connecting to the new cluster. Have tried allowing all traffic thru the firewall between dmz and trust zones but no luck. I can ping the SQL cluster as well as the standalone SQL server from the DMZ and vice versa, but can only get a successful test ODBC connection to the standalone server. Windows firewall already disabled on the SQL cluster and no antivirus is installed. Any ideas? Thanks TI |
the standalone was default...thanks in advance!
#8
| |||
| |||
|
|
Hi We have an application *running on an NLB cluster in the DMZ. Application data is stored on a standalone SQL 2005 Std server located not in the DMZ but inside the company's private network. *Have recently setup a 2-node SQL 2005 Std failover cluster running on Windows 2008 Ent, all 64-bit and in the process of pointing the application to it. For some reason I'm having problems connecting to the new cluster. Have tried allowing all traffic thru the firewall between dmz and trust zones but no luck. I can ping the SQL cluster as well as the standalone SQL server from the DMZ and vice versa, but can only get a successful test ODBC connection to the standalone server. Windows firewall already disabled on the SQL cluster and no antivirus is installed. Any ideas? Thanks TI |
the standalone was default...thanks in advance!
#9
| |||
| |||
|
|
Hi We have an application *running on an NLB cluster in the DMZ. Application data is stored on a standalone SQL 2005 Std server located not in the DMZ but inside the company's private network. *Have recently setup a 2-node SQL 2005 Std failover cluster running on Windows 2008 Ent, all 64-bit and in the process of pointing the application to it. For some reason I'm having problems connecting to the new cluster. Have tried allowing all traffic thru the firewall between dmz and trust zones but no luck. I can ping the SQL cluster as well as the standalone SQL server from the DMZ and vice versa, but can only get a successful test ODBC connection to the standalone server. Windows firewall already disabled on the SQL cluster and no antivirus is installed. Any ideas? Thanks TI |
the standalone was default...thanks in advance!
#10
| |||
| |||
|
|
Hi We have an application *running on an NLB cluster in the DMZ. Application data is stored on a standalone SQL 2005 Std server located not in the DMZ but inside the company's private network. *Have recently setup a 2-node SQL 2005 Std failover cluster running on Windows 2008 Ent, all 64-bit and in the process of pointing the application to it. For some reason I'm having problems connecting to the new cluster. Have tried allowing all traffic thru the firewall between dmz and trust zones but no luck. I can ping the SQL cluster as well as the standalone SQL server from the DMZ and vice versa, but can only get a successful test ODBC connection to the standalone server. Windows firewall already disabled on the SQL cluster and no antivirus is installed. Any ideas? Thanks TI |
the standalone was default...thanks in advance!
|
« Previous Thread
|
Next Thread »
| Thread Tools | |
| Display Modes | |
Linear Mode
| |
Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.