- This topic has 4 replies, 3 voices, and was last updated 15 years, 4 months ago by
.
-
Posts
-
I had a problem connecting to an MS SQL Server instance other than default, that I tracked down (finally!) to a Vista firewall problem – I overcame it by adding the SQL Server Studio executable to the firewall program exceptions.
Looks like I may have the same problem with the DB Explorer – I can connect to any of my MS SQL Server databases if they are running on a default instance but not a named instance – the myeclipse.exe is in the firewall program exceptions to no avail!
The connection string I am using is jdbc:jtds:sqlserver://<server>/<instance>/<databasename>
Any ideas anyone?
Using ME 7.5 and SQL Server 2005 – my client OS is Vista Ultimate SP1
Thanks
Chris Parsons
Chris,
This sounds more like a Vista security issue. I haven’t seen this one being reported earlier. I would suggest you cross post this query on the vista forums. I’ll check with my team and let you know if they have any inputs on this.Yes, I think you are right, but I am not sure how to get around this – the myeclipse.exe is a firewall exception and I still get the problem, but not with a database that is a default rather than named instance!
The M$ website has some info on this which pointed to a connectivity issue which is how I got SQL Server Management Studio to work but the same approach doesn’t seem to help with DB Explorer – which is not an .exe but a library run under the JRE which is also not an .exe (by the looks of it you cannot add a firewall exception for a .dll, ie jvm.dll so I am stumped)
I could turn the firewall off but my company would not be very happy <g>
Think the response from any Vista forum will be ‘Java?…dump it and use .NET instead’ which is NOT going to happen!
I’ll keep experimenting
Thanks
Chris Parsons
Moving to Off Topic >> Software Developement.
The users on the Software Development forum could give their inputs.
