 | |
SQL Cluster Connection Problem from Windows 2008 Machine
microsoft.public.sqlserver.clustering microsoft.public.sqlserver.clustering
 |
| | Thread Tools | Display Modes |
#1
 
| |||
| |||
|
SQL Cluster Connection Problem from Windows 2008 Machine -
10-20-2008
, 09:09 PM
#2
| |||
| |||
|
|
Hi, We have a sql server 2005 cluster on Windows 2003 64 Bit Machine. From our whole network we can connect to the sql server fine. TCP/IP, Named Pipes are both allowed. Recently we installed couple of Windows 2008 machine on our network. When we try to connect to the cluster from Windows 2008 machines, it takes atleast 10 sec to connect. No error logs anywehere. We have profiled the connection from SQL Profiler and saw that when ever the windows 2008 machine trying to connet it's using named pipes. We have tried changing the protocol order, specifiying the protocol in connection string. But when we try to connet other Sql servers in the network, which is not clustered, it connects fine from Windows 2008. Spent last couple of days trying to look for solutions on the web with no luck. On the SQL cluster we also have a named instance sql server on a diff cluster group. From Windows 2008 we can't even connent to that named instance. In Summary: Server ------------ Client ---------------------------------------------------------------------------------------------- SQL Cluster 2005 64 bit SP2, OS: W2k3 64 Bit <--Slow Connection -- W2K8 SQL Cluster 2005 64 bit SP2, OS: W2k3 64 Bit <--No Connection -- W2K8 (Named Instance) SQL Browser Is also running on the cluster. We have no problem from any other domain machines, xp, w2k3, w2k. Our AD is Windows 2008 based with Domain Functional Level Set to -Windows 2008 Any help would be much appreciated. Thanks Sazzad |
Vista and Windows server 2008 incompatible for 8 years now:
https://connect.microsoft.com/SQLSer...dbackID=296165
Temporarily disable windows Firewall completely if it is possible or
add an Exception to test this.
Regards,
Peter
#3
| |||
| |||
|
|
Hi, We have a sql server 2005 cluster on Windows 2003 64 Bit Machine. From our whole network we can connect to the sql server fine. TCP/IP, Named Pipes are both allowed. Recently we installed couple of Windows 2008 machine on our network. When we try to connect to the cluster from Windows 2008 machines, it takes atleast 10 sec to connect. No error logs anywehere. We have profiled the connection from SQL Profiler and saw that when ever the windows 2008 machine trying to connet it's using named pipes. We have tried changing the protocol order, specifiying the protocol in connection string. But when we try to connet other Sql servers in the network, which is not clustered, it connects fine from Windows 2008. Spent last couple of days trying to look for solutions on the web with no luck. On the SQL cluster we also have a named instance sql server on a diff cluster group. From Windows 2008 we can't even connent to that named instance. In Summary: Server ------------ Client ---------------------------------------------------------------------------------------------- SQL Cluster 2005 64 bit SP2, OS: W2k3 64 Bit <--Slow Connection -- W2K8 SQL Cluster 2005 64 bit SP2, OS: W2k3 64 Bit <--No Connection -- W2K8 (Named Instance) SQL Browser Is also running on the cluster. We have no problem from any other domain machines, xp, w2k3, w2k. Our AD is Windows 2008 based with Domain Functional Level Set to -Windows 2008 Any help would be much appreciated. Thanks Sazzad |
Vista and Windows server 2008 incompatible for 8 years now:
https://connect.microsoft.com/SQLSer...dbackID=296165
Temporarily disable windows Firewall completely if it is possible or
add an Exception to test this.
Regards,
Peter
#4
| |||
| |||
|
|
Hi, We have a sql server 2005 cluster on Windows 2003 64 Bit Machine. From our whole network we can connect to the sql server fine. TCP/IP, Named Pipes are both allowed. Recently we installed couple of Windows 2008 machine on our network. When we try to connect to the cluster from Windows 2008 machines, it takes atleast 10 sec to connect. No error logs anywehere. We have profiled the connection from SQL Profiler and saw that when ever the windows 2008 machine trying to connet it's using named pipes. We have tried changing the protocol order, specifiying the protocol in connection string. But when we try to connet other Sql servers in the network, which is not clustered, it connects fine from Windows 2008. Spent last couple of days trying to look for solutions on the web with no luck. On the SQL cluster we also have a named instance sql server on a diff cluster group. From Windows 2008 we can't even connent to that named instance. In Summary: Server ------------ Client ---------------------------------------------------------------------------------------------- SQL Cluster 2005 64 bit SP2, OS: W2k3 64 Bit <--Slow Connection -- W2K8 SQL Cluster 2005 64 bit SP2, OS: W2k3 64 Bit <--No Connection -- W2K8 (Named Instance) SQL Browser Is also running on the cluster. We have no problem from any other domain machines, xp, w2k3, w2k. Our AD is Windows 2008 based with Domain Functional Level Set to -Windows 2008 Any help would be much appreciated. Thanks Sazzad |
Vista and Windows server 2008 incompatible for 8 years now:
https://connect.microsoft.com/SQLSer...dbackID=296165
Temporarily disable windows Firewall completely if it is possible or
add an Exception to test this.
Regards,
Peter
#5
| |||
| |||
|
|
Hi, We have a sql server 2005 cluster on Windows 2003 64 Bit Machine. From our whole network we can connect to the sql server fine. TCP/IP, Named Pipes are both allowed. Recently we installed couple of Windows 2008 machine on our network. When we try to connect to the cluster from Windows 2008 machines, it takes atleast 10 sec to connect. No error logs anywehere. We have profiled the connection from SQL Profiler and saw that when ever the windows 2008 machine trying to connet it's using named pipes. We have tried changing the protocol order, specifiying the protocol in connection string. But when we try to connet other Sql servers in the network, which is not clustered, it connects fine from Windows 2008. Spent last couple of days trying to look for solutions on the web with no luck. On the SQL cluster we also have a named instance sql server on a diff cluster group. From Windows 2008 we can't even connent to that named instance. In Summary: Server ------------ Client ---------------------------------------------------------------------------------------------- SQL Cluster 2005 64 bit SP2, OS: W2k3 64 Bit <--Slow Connection -- W2K8 SQL Cluster 2005 64 bit SP2, OS: W2k3 64 Bit <--No Connection -- W2K8 (Named Instance) SQL Browser Is also running on the cluster. We have no problem from any other domain machines, xp, w2k3, w2k. Our AD is Windows 2008 based with Domain Functional Level Set to -Windows 2008 Any help would be much appreciated. Thanks Sazzad |
Vista and Windows server 2008 incompatible for 8 years now:
https://connect.microsoft.com/SQLSer...dbackID=296165
Temporarily disable windows Firewall completely if it is possible or
add an Exception to test this.
Regards,
Peter
#6
| |||
| |||
|
|
Hi, We have a sql server 2005 cluster on Windows 2003 64 Bit Machine. From our whole network we can connect to the sql server fine. TCP/IP, Named Pipes are both allowed. Recently we installed couple of Windows 2008 machine on our network. When we try to connect to the cluster from Windows 2008 machines, it takes atleast 10 sec to connect. No error logs anywehere. We have profiled the connection from SQL Profiler and saw that when ever the windows 2008 machine trying to connet it's using named pipes. We have tried changing the protocol order, specifiying the protocol in connection string. But when we try to connet other Sql servers in the network, which is not clustered, it connects fine from Windows 2008. Spent last couple of days trying to look for solutions on the web with no luck. On the SQL cluster we also have a named instance sql server on a diff cluster group. From Windows 2008 we can't even connent to that named instance. In Summary: Server ------------ Client ---------------------------------------------------------------------------------------------- SQL Cluster 2005 64 bit SP2, OS: W2k3 64 Bit <--Slow Connection -- W2K8 SQL Cluster 2005 64 bit SP2, OS: W2k3 64 Bit <--No Connection -- W2K8 (Named Instance) SQL Browser Is also running on the cluster. We have no problem from any other domain machines, xp, w2k3, w2k. Our AD is Windows 2008 based with Domain Functional Level Set to -Windows 2008 Any help would be much appreciated. Thanks Sazzad |
Vista and Windows server 2008 incompatible for 8 years now:
https://connect.microsoft.com/SQLSer...dbackID=296165
Temporarily disable windows Firewall completely if it is possible or
add an Exception to test this.
Regards,
Peter
#7
| |||
| |||
|
|
Hi, We have a sql server 2005 cluster on Windows 2003 64 Bit Machine. From our whole network we can connect to the sql server fine. TCP/IP, Named Pipes are both allowed. Recently we installed couple of Windows 2008 machine on our network. When we try to connect to the cluster from Windows 2008 machines, it takes atleast 10 sec to connect. No error logs anywehere. We have profiled the connection from SQL Profiler and saw that when ever the windows 2008 machine trying to connet it's using named pipes. We have tried changing the protocol order, specifiying the protocol in connection string. But when we try to connet other Sql servers in the network, which is not clustered, it connects fine from Windows 2008. Spent last couple of days trying to look for solutions on the web with no luck. On the SQL cluster we also have a named instance sql server on a diff cluster group. From Windows 2008 we can't even connent to that named instance. In Summary: Server ------------ Client ---------------------------------------------------------------------------------------------- SQL Cluster 2005 64 bit SP2, OS: W2k3 64 Bit <--Slow Connection -- W2K8 SQL Cluster 2005 64 bit SP2, OS: W2k3 64 Bit <--No Connection -- W2K8 (Named Instance) SQL Browser Is also running on the cluster. We have no problem from any other domain machines, xp, w2k3, w2k. Our AD is Windows 2008 based with Domain Functional Level Set to -Windows 2008 Any help would be much appreciated. Thanks Sazzad |
Vista and Windows server 2008 incompatible for 8 years now:
https://connect.microsoft.com/SQLSer...dbackID=296165
Temporarily disable windows Firewall completely if it is possible or
add an Exception to test this.
Regards,
Peter
#8
| |||
| |||
|
|
Hi, We have a sql server 2005 cluster on Windows 2003 64 Bit Machine. From our whole network we can connect to the sql server fine. TCP/IP, Named Pipes are both allowed. Recently we installed couple of Windows 2008 machine on our network. When we try to connect to the cluster from Windows 2008 machines, it takes atleast 10 sec to connect. No error logs anywehere. We have profiled the connection from SQL Profiler and saw that when ever the windows 2008 machine trying to connet it's using named pipes. We have tried changing the protocol order, specifiying the protocol in connection string. But when we try to connet other Sql servers in the network, which is not clustered, it connects fine from Windows 2008. Spent last couple of days trying to look for solutions on the web with no luck. On the SQL cluster we also have a named instance sql server on a diff cluster group. From Windows 2008 we can't even connent to that named instance. In Summary: Server ------------ Client ---------------------------------------------------------------------------------------------- SQL Cluster 2005 64 bit SP2, OS: W2k3 64 Bit <--Slow Connection -- W2K8 SQL Cluster 2005 64 bit SP2, OS: W2k3 64 Bit <--No Connection -- W2K8 (Named Instance) SQL Browser Is also running on the cluster. We have no problem from any other domain machines, xp, w2k3, w2k. Our AD is Windows 2008 based with Domain Functional Level Set to -Windows 2008 Any help would be much appreciated. Thanks Sazzad |
Vista and Windows server 2008 incompatible for 8 years now:
https://connect.microsoft.com/SQLSer...dbackID=296165
Temporarily disable windows Firewall completely if it is possible or
add an Exception to test this.
Regards,
Peter
#9
| |||
| |||
|
|
Hi, We have a sql server 2005 cluster on Windows 2003 64 Bit Machine. From our whole network we can connect to the sql server fine. TCP/IP, Named Pipes are both allowed. Recently we installed couple of Windows 2008 machine on our network. When we try to connect to the cluster from Windows 2008 machines, it takes atleast 10 sec to connect. No error logs anywehere. We have profiled the connection from SQL Profiler and saw that when ever the windows 2008 machine trying to connet it's using named pipes. We have tried changing the protocol order, specifiying the protocol in connection string. But when we try to connet other Sql servers in the network, which is not clustered, it connects fine from Windows 2008. Spent last couple of days trying to look for solutions on the web with no luck. On the SQL cluster we also have a named instance sql server on a diff cluster group. From Windows 2008 we can't even connent to that named instance. In Summary: Server ------------ Client ---------------------------------------------------------------------------------------------- SQL Cluster 2005 64 bit SP2, OS: W2k3 64 Bit <--Slow Connection -- W2K8 SQL Cluster 2005 64 bit SP2, OS: W2k3 64 Bit <--No Connection -- W2K8 (Named Instance) SQL Browser Is also running on the cluster. We have no problem from any other domain machines, xp, w2k3, w2k. Our AD is Windows 2008 based with Domain Functional Level Set to -Windows 2008 Any help would be much appreciated. Thanks Sazzad |
Vista and Windows server 2008 incompatible for 8 years now:
https://connect.microsoft.com/SQLSer...dbackID=296165
Temporarily disable windows Firewall completely if it is possible or
add an Exception to test this.
Regards,
Peter
#10
| |||
| |||
|
|
Hi, We have a sql server 2005 cluster on Windows 2003 64 Bit Machine. From our whole network we can connect to the sql server fine. TCP/IP, Named Pipes are both allowed. Recently we installed couple of Windows 2008 machine on our network. When we try to connect to the cluster from Windows 2008 machines, it takes atleast 10 sec to connect. No error logs anywehere. We have profiled the connection from SQL Profiler and saw that when ever the windows 2008 machine trying to connet it's using named pipes. We have tried changing the protocol order, specifiying the protocol in connection string. But when we try to connet other Sql servers in the network, which is not clustered, it connects fine from Windows 2008. Spent last couple of days trying to look for solutions on the web with no luck. On the SQL cluster we also have a named instance sql server on a diff cluster group. From Windows 2008 we can't even connent to that named instance. In Summary: Server ------------ Client ---------------------------------------------------------------------------------------------- SQL Cluster 2005 64 bit SP2, OS: W2k3 64 Bit <--Slow Connection -- W2K8 SQL Cluster 2005 64 bit SP2, OS: W2k3 64 Bit <--No Connection -- W2K8 (Named Instance) SQL Browser Is also running on the cluster. We have no problem from any other domain machines, xp, w2k3, w2k. Our AD is Windows 2008 based with Domain Functional Level Set to -Windows 2008 Any help would be much appreciated. Thanks Sazzad |
Vista and Windows server 2008 incompatible for 8 years now:
https://connect.microsoft.com/SQLSer...dbackID=296165
Temporarily disable windows Firewall completely if it is possible or
add an Exception to test this.
Regards,
Peter
|
« 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.