Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

SQL 2005 on Server 2008 R2 not finding instances Expand / Collapse
Author
Message
Posted Thursday, August 1, 2013 6:43 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Thursday, August 1, 2013 9:57 AM
Points: 2, Visits: 5
Greetings all,

New to this site and it looks like just the place I need to ask about this problem.

Little background on the problem. We had an old server that was running Windows Server 2003 and on it had our TimeClock Plus program, which had a SQL 2005 instance on it. It worked all fine and dandy, but about 2 weeks ago the RAID controller went totally belly up. So we invested in a new server for the company and decided to do a bit of upgrading. Got a nice Dell PowerEdge 2950, installed Windows Server 2008 R2 64-bit on it. Everything was going along well till we tried to install the timeclock software, it gagged saying it wanted 64-bit SQL. OK. Got that installed, got the SQL database transferred without a problem, and everything works fine on the server. It even has no problems with the 3 remote timeclocks where people punch in and out.

Problem I am having is, nobody can remote connect to the SQL instance. I have set the firewall ports 1433, 1434, and 1711 (saw this one elsewhere on these forums) open. I have made sure it's enabled via TCP/IP. I have tried turning the firewall completely off (just to test) and still nothing.

Now comes the fun part. On my desktop computer, which is Windows 7 Pro 64-bit, I can go to the ODBC Data Source Administrator and try to connect to the SQL it comes in both 64-bit and 32-bit. On the 64-bit version I can connect to the instance with no problems, the 32-bit it connection fails with:



Please, if anyone can help me to get past this it would be most appreciated. I am sure it's probably something so simple.

Thank you,
Jeremy Armer
Post #1479910
Posted Thursday, August 1, 2013 10:00 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Thursday, August 1, 2013 9:57 AM
Points: 2, Visits: 5
Just wanted to reply. Think I got it solved myself. A few more hours of mucking around in server's newer firewall and it magically turned on about 20 minutes ago.

Added the dynamic ports, SQL Server exe and SQL Browser exe to the firewall. And also adjusted a few settings in the TCP/IP settings of the SQL Instance. I don't think the latter did much, but as it is working.. I am so not changing them back at this point.
Post #1480013
Posted Thursday, August 1, 2013 10:57 AM


SSC-Dedicated

SSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-Dedicated

Group: Administrators
Last Login: Yesterday @ 3:06 PM
Points: 33,169, Visits: 15,304
glad it's working for you. Usually if you install with defaults, the firewall isn't too much of an issue, but it can be frustrating to get it working.






Follow me on Twitter: @way0utwest

Forum Etiquette: How to post data/code on a forum to get the best help
Post #1480037
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse