Sql server 2000 connect with other than jdbc?

Question

Is there any other way to connect to a Sql Server 2000 database other than with jdbc? My problem actually resides in the fact that I did a small program to test the connection to the database and it works perfectly on my computer but on the server that it's going to stay on, it doesn't.
the program is classic:
try{
     DriverManager.registerDriver(new com.microsoft.jdbc.sqlserver.SQLServerDriver());     
     Connection connection = DriverManager.getConnection("jdbc:microsoft:sqlserver://12.345.67.890\ \INSTANCENAME:1433;databaseName=NAME;selectMethod=cursor;","user","pass");
if (connection != null) {
     System.out.println("Successfully connected");
this small program works ok on my computer(win xp, tomcat 6) but on the other computer(ubuntu, tomcat 5.2) says
Exceptionjava.sql.SQLException: [Microsoft][SQLServer 2000 Driver for JDBC]The requested instance is either invalid or not running.
I pinged the ip(12.3...) from the server and it works. So I can't figure out what could cause the error. I tried 20 different connection string and don't work. I'm thinking it might have to do with using MS jdbc drivers on a unix platform? or maybe it's from the server firewall(it's a virtual server), anybody can confirm if they had similar problem? Since I can't figure out the problem, I'm trying to test connection using something else than jdbc but google didn't help much
thanks in advance!
Edited by: Biggie_mac on Sep 28, 2007 6:48 AM

Answer 1

Biggie_mac wrote:
Is there any other way to connect to a Sql Server 2000 database other than with jdbc? My problem actually resides in the fact that I did a small program to test the connection to the database and it works perfectly on my computer but on the server that it's going to stay on, it doesn't.Something's different between the two servers. Obviously.
I pinged the ip(12.3...) from the server and it works. So I can't figure out what could cause the error. I tried 20 different connection string and don't work. Why did you do that if the Tomcat version "works"? You're looking in the wrong place.
I'm thinking it might have to do with using MS jdbc drivers on a unix platform? Why would that matter if you're using type IV 100% Java JDBC drivers?
or maybe it's from the server firewall(it's a virtual server), anybody can confirm if they had similar problem? If you can ping it successfully, how can it be a firewall issue?
You're doing something else wrong.
%