New SQL 2005

[fmrock]

We recently migrated our 2000 Server to 2005. In the process the system admin gave it a new name.

Moved all our data to the new server.

Now the issue is one of our reporting servers, cant connect to this database.

For example, when you try to setup a ODBC connection to this server, by the server name it just fails, how ever if you change it to use the ip address like 111.11.111/DB the odbc works.

Our report server does not use ODBC but sounds like, what ever is the problem, is affecting both.

Any ideas?

 

[gmmastros]

99.9% of the time, when you can connect to the server using IP address, but NOT server name, it means you have a DNS problem.



-George

"The great things about standards is that there are so many to choose from." - Fortune Cookie Wisdom

 

[fmrock]

You can ping the new server and the IP address resolves.

The system admin things its a driver issue on that server as the driver looks very outdated. Alot older then some of our other servers.

 

[fmrock]

We changed the new SQL Servers to use Named Pipes and TCP.

The system admin also said that the DSN connection does not work using the IP like he thought, plus you can ping the SQL servers from this server and the IP address resolves and no lost packets.

Any other ideas on why we cant connect to these new servers from an older server?

 

[mrdenny]

Can you telnet to the SQL server on port 1433?

Denny
MCSA (2003) / MCDBA (SQL 2000)
MCTS (SQL 2005 / Microsoft Windows SharePoint Services 3.0: Configuration / Microsoft Office SharePoint Server 2007: Configuration)
MCITP Database Administrator (SQL 2005) / Database Developer (SQL 2005)

My Blog

 

[fmrock]

The sys admin said no. But he thought that had changed in SQL 2005.

 

[MDXer]

Is this from a specific machine or is it from all machines?

Paul
---------------------------------------
Shoot Me! Shoot Me NOW!!!
- Daffy Duck

 

[fmrock]

One specific server. Its our Crystal Enterprise Report server. this server has over 50 reports that connect to these production databases (the ones that were upgraded from 2000 to 2005).

Now from my local PC these reports can connect, and I can setup an ODBC, but from this server nothing works.

 

[MDXer]

have you checked the hosts file and lmhost to make sure that nothing was hard coded?

Paul
---------------------------------------
Shoot Me! Shoot Me NOW!!!
- Daffy Duck

 

[fmrock]

These servers have new names also, so nothing would be hard coded yet.

 

[macleod1021]

try this....
1. Create an ODBC connection on the actual SQL Server and make sure it works. If it doesn't, then there' something wrong with the service...check to make sure you're using the proper instance (default or named).

2. If above works, turn off your fire wall on the SQL Server temporarily and go to another machine and create a new ODBC connection. See if it works. If it does, then you need to go to your sql server...turn the fire wall back on and create an exception for the ports that SQL Server needs.

3. If it doesn't work, get the SQL 2005 CD/DVD and install the 2005 native client on the remote machine and create an ODBC with that driver. If that works, great. If it doesn't...well...I dunno

im in ur stakz, overflowin ur heapz!

 

[mrdenny]

If you can't telnet from the Crystal Reports server to the SQL Server nothing else will work.

You've got some sort of firewall blocking the connection. SQL 2005 still uses port 1433 by default. Have you told the SQL Server to accept remote connections?

Denny
MCSA (2003) / MCDBA (SQL 2000)
MCTS (SQL 2005 / Microsoft Windows SharePoint Services 3.0: Configuration / Microsoft Office SharePoint Server 2007: Configuration)
MCITP Database Administrator (SQL 2005) / Database Developer (SQL 2005)

My Blog

 

[fmrock]

The system admin update the mdac on the report server and we were finally able to connect.