-
Well, you could have a share that all clients mount and have their individual CLASSPATHs reference the jar file from that share. I guess it depends on your systems: if you have a custom application that you are distributing out to all 50 clients then just include the jTDS jar with your application.
2009-07-21 14:58:06 UTC in jTDS - SQL Server and Sybase JDBC driver
-
The JAR file needs to be accessible by the client application, since this is what is making the actual JDBC calls: hence it must be in the CLASSPATH of the client. The JDBC DriverManager will actually handle loading the JTDS driver so that it is used for your connection strings.
2009-07-21 13:54:53 UTC in jTDS - SQL Server and Sybase JDBC driver
-
Stupid question, but it's good to rule them out: are you sure that the SQL Server account exists with the password you are providing, and that the server is configured to accept remote connections? Also, are you able to log into the server with those credentials from SQL Server Management Studio on the remote machine using the SQL Server authentication?.
2009-07-08 16:40:47 UTC in jTDS - SQL Server and Sybase JDBC driver
-
jTDS will only attempt to use Windows authentication if you include the 'domain' parameter in your connection string: otherwise it uses SQL Server authentication. Is it possible that the user name you are getting from the call to 'localConf.getDbUserName()' includes a domain? For example, if the string returned is really "DOMAIN\USER" then the server is attempting to authenticate with...
2009-07-08 16:23:34 UTC in jTDS - SQL Server and Sybase JDBC driver
