SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Why can I connect to my new cluster via ODBC but not in SSMS?


Why can I connect to my new cluster via ODBC but not in SSMS?

Author
Message
pwilly
pwilly
SSC Rookie
SSC Rookie (37 reputation)SSC Rookie (37 reputation)SSC Rookie (37 reputation)SSC Rookie (37 reputation)SSC Rookie (37 reputation)SSC Rookie (37 reputation)SSC Rookie (37 reputation)SSC Rookie (37 reputation)

Group: General Forum Members
Points: 37 Visits: 101
I have made several attempts to create a 2008 R2 failover cluster in my virtual environment. I can create the cluster, SQL validates the install, install SQL successfully and access the database via SSMS from the SQL server itself. I go to a another machine (virtual application server) and I can create a successful ODBC connection to the db. But when I try to connect from the app server to the db via SSMS with the cluster name I get the "Timeout expired. The timeout period elapsed prior to completion..." error. When I try with the IP address assigned to the cluster I get "A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible." "Named Pipes Provider, error: 40"

This a default instance and according to Configuration Manager it is using port 1433. Named Pipes and TCP/IP are enabled in Config Manager. The IP address of the cluster is listed in the IP addresses list in config manager. Remote access is allowed. Again I can connect via ODBC. So far this is a single node cluster as I'm trying to keep it simple until I can get it functional.

Any ideas?
Perry Whittle
Perry Whittle
SSCoach
SSCoach (19K reputation)SSCoach (19K reputation)SSCoach (19K reputation)SSCoach (19K reputation)SSCoach (19K reputation)SSCoach (19K reputation)SSCoach (19K reputation)SSCoach (19K reputation)

Group: General Forum Members
Points: 19912 Visits: 17242
Can you provide more detailed info on how the virtual environmment is setup?

Can you post details of the odbc connection steps too?

-----------------------------------------------------------------------------------------------------------

"Ya can't make an omelette without breaking just a few eggs" ;-)
pwilly
pwilly
SSC Rookie
SSC Rookie (37 reputation)SSC Rookie (37 reputation)SSC Rookie (37 reputation)SSC Rookie (37 reputation)SSC Rookie (37 reputation)SSC Rookie (37 reputation)SSC Rookie (37 reputation)SSC Rookie (37 reputation)

Group: General Forum Members
Points: 37 Visits: 101
It is a Hyper-V environment with 32 bit Server 2008 installed on the SQL Server and the application server. They are on the same physical host. They can ping each other by name and they can connect to each others file system via UNC path. The ODBC connection uses the SQL Server driver. I simply put in the SQL cluster name and the database users name and password and when I click Finish and then Test Data Source, it tells me that the Tests Completed Succesfully. But if I try open the database in SSMS it can't find the SQL Server. I only experience this trying to connect to this clustered database. I can connect to other database servers from this machine just fine. I have also tried to connect to the cluster via SSMS from machines other than my application server and get the same error.
pwilly
pwilly
SSC Rookie
SSC Rookie (37 reputation)SSC Rookie (37 reputation)SSC Rookie (37 reputation)SSC Rookie (37 reputation)SSC Rookie (37 reputation)SSC Rookie (37 reputation)SSC Rookie (37 reputation)SSC Rookie (37 reputation)

Group: General Forum Members
Points: 37 Visits: 101
By the way, I get the error connecting to the cluster through SSMS from physical machines as well as virtual. But I can ping the cluster name from everywhere as well as connect through ODBC from everywhere.
pwilly
pwilly
SSC Rookie
SSC Rookie (37 reputation)SSC Rookie (37 reputation)SSC Rookie (37 reputation)SSC Rookie (37 reputation)SSC Rookie (37 reputation)SSC Rookie (37 reputation)SSC Rookie (37 reputation)SSC Rookie (37 reputation)

Group: General Forum Members
Points: 37 Visits: 101
I have discovered that I cannot telnet to the 1433 port on the db server which seems to indicate that it is not accepting connections for some reason. I used NetMon and discovered that I see communication from the app server to the db server but nothing ever comes back from the db server. This only happens when trying to connect to this cluster. I can communicate with all of my non clustered db's just fine. I don't know if there's something i've not configured correctly or what. I don't much experience setting up clustered db's but i've set up plenty of stand alones and usually this is caused by the protocols not being enabled or that or a named instance is not being accounted for but this is a default instance.

Any ideas why I wouldn't be able to telnet to 1433 with the firewall off?
Perry Whittle
Perry Whittle
SSCoach
SSCoach (19K reputation)SSCoach (19K reputation)SSCoach (19K reputation)SSCoach (19K reputation)SSCoach (19K reputation)SSCoach (19K reputation)SSCoach (19K reputation)SSCoach (19K reputation)

Group: General Forum Members
Points: 19912 Visits: 17242
First check the windows firewall and ensure it is completely disabled, the firewall has 3 profiles. Best thing is to stop the service and set it to manual.

-----------------------------------------------------------------------------------------------------------

"Ya can't make an omelette without breaking just a few eggs" ;-)
pwilly
pwilly
SSC Rookie
SSC Rookie (37 reputation)SSC Rookie (37 reputation)SSC Rookie (37 reputation)SSC Rookie (37 reputation)SSC Rookie (37 reputation)SSC Rookie (37 reputation)SSC Rookie (37 reputation)SSC Rookie (37 reputation)

Group: General Forum Members
Points: 37 Visits: 101
Guys, I regret to inform you it was an id10t error causing the problem. I stopped the firewall service but forgot to reboot. After I rebooted I was able to connect. Thank you for your time and effort!
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search