How do i fix "Error establishing socket" !!!

I get the following error:
SQLException: [Microsoft][SQLServer 2000 Driver for JDBC]Error establishing socket.
I have included the driver jar files in the classpath. How can i fix this?
Thank u all for your time

No.. That's not the real answer.Which one?
If it can't create the socket then something is interferring with the socket creation.
I'm getting the same problem trying to connect to an
MSSQLServer box from JDBC.
I believe that my connect string is fine, as I use
jdbc on many databases - SWLServer being the only one
I can't connect to. Both machines are using TCP/IP,
and the server is accepting TCP/IP connections on port
1433. My connect URL is:
jdbc:microsoft:sqlserver://DBHOST:1433
This works on an NT box. This doesn't work on my
linux box.
I've attempted to use the IP address of the database
in the connect string, but that only produces a
different error from the driver "INVALID URL"
The only way I have been able to get this to work is
by bypassing JDBC and using the JDBC/ODBC bridge,
which STINKS. There must be a better answer.
Nope, don't think so. You said it doesn't work on linux. Are you claiming that you have a MS SQL Server ODBC driver for linux? If so you need to share it with the world.
Can you ping the SQL server box from your linux box? Can you telnet to the 1433 port (that tells you if it is open from the linux box.)
Presumably the SQL Server was NOT installed with NT authorization. Rather it was installed with Database authorization.

Similar Messages

  • JDBC Communication channel : Error establishing socket

    Dear friends,
    Im using JDBC comm channel. JDBC driver has been insatlled for SQL Server 2000 (SP3) .
    However for the JDBC comm. channel i get an error
    "SQLException: [Microsoft][SQLServer 2000 Driver for JDBC]Error establishing socket.'
    following parameters are used :
    JDBC driver:  com.microsoft.jdbc.sqlserver.SQLServerDriver
    DB connection :
    jdbc:microsoft:sqlserver://<ip address>:1433;databaseName=<dbname>
    i looked up some blogs in SDN, & tried some other options,
    eg: com.microsoft.sqlserver.jdbc.SQLServerDriver
    DB name:
    jdbc:microsoft:sqlserver://<ip address>:1433;DatabaseName=<dbname>
    However still get the same error
    Can somebody help ?

    Hi
    The following should fix your problem
    <i>I had this problem using SQLServer 2000 Driver for JDBC and finally solved it. Here's what I did:
    1. Make sure that SQL Server is set to mixed authentication. To do this, open enterprise manager, right click on server/properties; go to security tab and select SQL Server and Windows Authentication. Apparently, the driver from Microsoft cannot handle windows integrated authentication.
    2. Keeping the server properties dialog up, go to the general tab and push the network configuration button. <b>Enable TCP/IP (it is disabled by default). If you wish, press properties to change the default port (1433).</b>
    3. Add an SQL Server login account (NOT a WINDOWS account (see 1)). You can also use your sa account, but I don't recommend it.
    4. Use the login setup in step 3.
    Some final notes:
    (1) I've seen ads for third party drivers that can use Windows integrated authentication. Try one if you need this feature.
    (2) One responder suggested telneting to port 1433 to verify TCP connectivity. The connection is refused on my machine even though I can connect through the driver. And this is how it should be; otherwise there'd be a security risk.</i>
    Courtesy:XI installation Configuration of J2EE engine problem
    Regards
    krishna
    <i>Note:Reward points if helpful</i>

  • AttachToDocument - Error establishing socket.

    I'm encountering a problem where the calls to attachToDocument are generating SQLExceptions (CWS in Java for 4.5WS). It's a strange error that I am unfamiliar with. Please advise on how to fix this. Here is the complete stack trace:
    java.sql.SQLException: Pool connect failed : weblogic.common.ResourceException:
    0:Could not create pool connection. The DBMS driver exception was: [BEA][SQLServ
    er JDBC Driver]Error establishing socket. Too many open files - with nested exce
    ption:
    [weblogic.common.ResourceException: Could not create pool connection. The DBMS d
    river exception was: [BEA][SQLServer JDBC Driver]Error establishing socket. Too
    many open files]
    at weblogic.jdbc.common.internal.JDBCUtil.wrapAndThrowResourceException(
    JDBCUtil.java:160)
    at weblogic.jdbc.pool.Driver.connect(Driver.java:155)
    at weblogic.jdbc.jts.Driver.getNonTxConnection(Driver.java:444)
    at weblogic.jdbc.jts.Driver.connect(Driver.java:138)
    at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSour
    ce.java:298)
    at com.ml.mlim.enterprise.common.util.MCServiceLocator.getDBConn(MCServi
    ceLocator.java:183)
    at com.ml.mlim.marketing.estudio.cws.DocumentProvider.connect(Unknown So
    urce)
    at com.ml.mlim.marketing.estudio.cws.DocumentProvider.getConnection(Unkn
    own Source)
    at com.ml.mlim.marketing.estudio.cws.DocumentProvider.initialize(Unknown
    Source)
    at com.plumtree.remote.crawler.NativeDocumentProvider.Initialize(NativeD
    ocumentProvider.java:47)
    at com.plumtree.remote.crawler.xp.XPDocumentProvider.Initialize(XPDocume
    ntProvider.java:62)
    at com.plumtree.remote.crawler.soap.DocumentProviderSoapBindingImpl.Init
    ialize(DocumentProviderSoapBindingImpl.java:73)
    at com.plumtree.remote.crawler.soap.DocumentProviderSoapBindingSkeleton.
    Initialize(DocumentProviderSoapBindingSkeleton.java:150)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
    java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
    sorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:324)
    at org.apache.axis.providers.java.RPCProvider.invokeMethod(RPCProvider.j
    ava:402)
    at org.apache.axis.providers.java.RPCProvider.processMessage(RPCProvider
    .java:309)
    at org.apache.axis.providers.java.JavaProvider.invoke(JavaProvider.java:
    333)
    at org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrateg
    y.java:71)
    at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:150)
    at org.apache.axis.SimpleChain.invoke(SimpleChain.java:120)
    at org.apache.axis.handlers.soap.SOAPService.invoke(SOAPService.java:481
    at org.apache.axis.server.AxisServer.invoke(AxisServer.java:323)
    at org.apache.axis.transport.http.AxisServlet.doPost(AxisServlet.java:85
    4)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
    at org.apache.axis.transport.http.AxisServletBase.service(AxisServletBas
    e.java:339)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
    at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run
    (ServletStubImpl.java:1053)
    at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubIm
    pl.java:387)
    at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubIm
    pl.java:305)
    at weblogic.servlet.internal.WebAppServletContext$ServletInvocationActio
    n.run(WebAppServletContext.java:6310)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(Authenticate
    dSubject.java:317)
    at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:
    118)
    at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppSe
    rvletContext.java:3622)
    at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestIm
    pl.java:2569)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)

    This is happening because you are running out of file descriptors. You can see how many file descriptors you have open by using the following command:
    lsof -p<process id of your JVM>
    Cause: you might have a file descriptor leak. The oracle OCI driver is known to have this type of issue! You must find out what is causing this leak. Or if you are not closing your connections. Use the lsof command to monitor your file descriptors and try to isolate the leak.
    Fix: Increase the number of file descriptor to 4096 if you still run out you must restart the process to rest them to 0. If you have a leak you must address it if not it could be a case of you application just needing more desciptors.
    Email me if you want to talk more:
    [email protected]

  • Error Establishing Socket jdbc

    hello guys i have the problem of error establishing socket in tomacat 4.0.1 and i am using sqlserver 2000.My Application works well for n number of users but then application server hangs giving the "error establishing socket".
    i am closing all the statements and i am calling connection object in init() and closing it in destoy(). And I am not using connection pooling.
    please specify the changes needed to work with SQL server connection with jdbc
    do help me guys its urgent for me
    tell me as soon as possible.

    hello guys i have the problem of error establishing
    socket in tomacat 4.0.1 and i am using sqlserver
    2000.My Application works well for n number of users
    but then application server hangs giving the "error
    establishing socket".
    i am closing all the statements and i am calling
    connection object in init() and closing it in
    destoy(). And I am not using connection pooling.
    please specify the changes needed to work with SQL
    server connection with jdbc
    do help me guys its urgent for me
    tell me as soon as possible. sql server and windows are terrible under load. i know this from
    personal experience ahving spent a great deal of time fixing an ASP site
    that used ADO to access SQL Server 2000. what happens eventually with
    windows and sql server is that when the server gets really busy the os
    does not prioritize itself very well and you can run out of sockets
    temporarily because even though you have programmtically released them
    the operating system is still holding on to them.
    part of the solution i used was to use pooled connections. i suggest the
    same for you.

  • Error establishing socket (Microsoft SQL Server 2000 Driver for JDBC)

    I tray connect to MS-SQL2000 using JDeveloper and retrieve an error: "[Microsoft][SQLServer 2000 Driver for JDBC]Error establishing socket.[Microsoft][SQLServer 2000 Driver for JDBC]PC160832\NCI_DBA_01"
    I followed the steps:
    1 - Install the JDBC Driver for MS-SQL2000
    2 - Create a new AddJavaLibPath :"AddJavaLibPath C:/Program files/Microsoft SQL Server 2000 Driver for JDBC/lib"
    3 - Specify Default Project Libraries: "msbase.jar, msutil.jar and mssqlserver.jar"
    4 - Create a new connection: "Java class name: com.microsoft.jdbc.sqlserver.SQLServerDriver" "URL: jdbc:microsoft:sqlserver://PC160832\NCI_DBA_01:1433;SelectMethod=cursor"
    5 - Retrieve the error: "[Microsoft][SQLServer 2000 Driver for JDBC]Error establishing socket.[Microsoft][SQLServer 2000 Driver for JDBC]PC160832\NCI_DBA_01"

    Were you able to resolve this? If so could you tell me how. I have the same problem.
    Thanks!!!

  • Intermittent error establishing socket on SQL Server 2000

    I have a suite of 130 JUnit tests. Recently, they started to give me intermittent "error establishing socket" errors when trying to connect to a local instance of SQL Server 2000 via JDBC.
    Each test creates one or more connections. I've used wrappers to prove that I'm closing all of the connections, statements, prepared statements and result sets. The first 70 or 80 tests succeed. After that every test gets the "error establishing socket" exception. Sometimes (but not always) SQL Server continues to refuse connections when I re-run the suite. When that happens I have to let it sit for 30 seconds or so (or restart the server) before it will accept connections.
    I've tested this with both Microsoft's and WebLogic's JDBC drivers with the same results. There's nothing in the SQL Server logs when this happens. There's nothing in the Windows event logs, either.
    If I sleep for 5 seconds between each test the problem goes away.
    I installed the latest service pack (SP3a) for SQL Server 2000 with no change in behavior.
    All of this leads me to believe that something is wrong with SQL Server. Has anyone else run into this problem? Any ideas?

    I am not overly familiar with the SQL Server network architecture, but there are scenarios that could explain your intermittent failures.
    When you connect to a database one of two things can happen, you can start your own process on the server that acts as communication to from the server locally, or you are put in a queue for a static (shared) process that does the same thing.
    Assuming that most databases are initially setup with singular processes per connection, and you have established a connection then you disconnect from the database you do not automatically or instantly kill your process running on the server. There are two primary reasons for this as far as I know. First, the database puts more priority on doing something then doing nothing. Cleaning up and removing your process would be considered doing nothing, accepting incoming connections would be considered doing something. Second, the process may have to stay around to ensure all commit or rollback is completed properly (not always true in every database).
    So, I would expect that there is a connection limit (perhaps between 50-80) that you are exceeding because you are firing these connections rapidly and even though you close the connection in your remote program, the database simply doesn't keep up. Most databases will "cleanup" reasonably quickly if they have the resources to do so, so if you were to put a 30 second delay between every connection it would probably work just fine. It would probably work fine if you put a 30 second delay between after every 20 connections too. It's a bit of balancing act.
    There would be a couple of ways to alleviate this constraint. Putting in delays can demonstrate that this is in fact a work load problem (constrained by total count of connections), but doesn't really help in production instances. You can change the maximum number of connections allowed by the database, however this threshold may be caused by hardware resource (memory) limitations as much as it is a parameter in the database. You may have to add memory to accommodate this many connections. You may have to constrain how much memory each connection gets (again controlled by database parameters). You may have to accept this as a resource constraint and write your code accordingly. This often manifests itself by taking advantage of transaction managers (or transaction manager logic) that will queue up requests until database resources are available.
    Again, I'm not a SQL Server expert, but I'm reasonably certain that most of what I said applies if not specifically at least generally.
    Good Luck.

  • Error Establishing Socket with SQL Server 2000

    I have a java application that uses JDBC to connect to a source of data.
    The application has been installed on many platforms using many different data sources, but one combination has beaten me.
    I am using Windows Server 2003 and SQL Server 2000 Enterprise, when the application starts up it fails to connect to the database with the following message:
    [Microsoft][SQL Server 2000 Driver for JDBC] Error Establishing Socket
    I have looked at a lot of forums and tried many things but nothing has fixed the problem for me:
    To summarise:
    The URL I am using is jdbc:microsoft:sqlserver://locahost:1433
    I have also tried using the name of the machine and it's actual IP address
    I have checked that TCP/IP is enabled and using the correct port (1433)
    Both SQL Server and Windows authentication are enabled and I can connect using both method from ODBC
    I can connect to it and use it with c#.net, vb.net and ODBC from the same machine
    I have installed the latest SQL Server 2000 service pack
    The application works with SQL Server 2000 Developer on Windows XP
    If anyone has any other suggestions, I would love to hear from you.

    If you printed out the SQL state and error code that would be a bit more info:
    catch (SQLException e)
        e.printStackTrace();
        System.err.println("SQL state: " + e.getSQLState());
        System.err.println("SQL error: " + e.getErrorCode());
    }Maybe that will give you more detail as to exactly why this is happening.
    The only other thought I had was security. Maybe there's a permission to access the port that would have to be granted explicitly as part of M$'s new emphasis on security. You did say it was Windoze Server 2003. Maybe that's the difference between all the other installs and this one.
    No joy from me, sorry. - MOD

  • How do i fix Error 1002

    how do i fix Error 1002

    Let the phone completeley run out of battery (so the 'plug into itunes' image is no longer there) - this may take 3 or 4 days. So when you try to turn it on normally it wont work. Then plug the phone into a wall socket until the 'plug into itunes' image comes up again.
    Now plug into your computer and the restore should work.
    This worked for me.Basically you need to let the iphone run out of battery before you can restore using itunes.

  • Getting "Error Establishing Socket " error while running the application

    Hi,
    Can Any one help me as I getting the following error while inserting data into database for after some rows and will insert for some rows then again some error . I googled but but didnt get any proper solution.
    Soultion what I got it is
    1) turn off windows firewall.
    2) change server TCP/IP settings.
    3) It will give probelm with windows XP SP 2
    I tried all but didnt able to solve that.
    I am using Java 1.5, MSSQL server 2000,and eclipse 3.2,windows XP SP2
    java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for JDBC]Error establishing socket.
    at com.microsoft.jdbc.base.BaseExceptions.createException(Unknown Source)
    at com.microsoft.jdbc.base.BaseExceptions.getException(Unknown Source)
    at com.microsoft.jdbc.base.BaseExceptions.getException(Unknown Source)
    at com.microsoft.jdbc.sqlserver.tds.TDSConnection.<init>(Unknown Source)
    at com.microsoft.jdbc.sqlserver.SQLServerImplConnection.open(Unknown Source)
    at com.microsoft.jdbc.base.BaseConnection.getNewImplConnection(Unknown Source)
    at com.microsoft.jdbc.base.BaseConnection.open(Unknown Source)
    at com.microsoft.jdbc.base.BaseDriver.connect(Unknown Source)
    at java.sql.DriverManager.getConnection(Unknown Source)
    at java.sql.DriverManager.getConnection(Unknown Source)
    at com.aztecsoft.quality.DatabaseConnectionQLTYSRV.getCon(DatabaseConnectionQLTYSRV.java:25)
    at com.aztecsoft.quality.DatabaseQuery.getDaytoCountRow(DatabaseQuery.java:147)
    at com.aztecsoft.quality.ProjectTrackerUtil.getNetworkDays(ProjectTrackerUtil.java:73)
    at com.aztecsoft.quality.ProjectPlan.calODurationinDays(ProjectPlan.java:81)
    at com.aztecsoft.quality.ProjectPlan.projectSummary(ProjectPlan.java:25)
    at com.aztecsoft.quality.ProjectPlan.main(ProjectPlan.java:126)
    Thanks in advance.

    Hi this is gopi,Hyd.Is your Problem "Getting "Error Establishing Socket " error while running the application" solved if so can you reply me i am waiting for this answer

  • How do I fix error 4310 when i want to burn a cd in windows 8?

    Hi ,
    How can I fix error 3410 when I want to burn a cd in I Tunes on my Windows 8 Lenovo G580 Notebook?

      Microsoft Windows Vista x64 x64 Home Premium Edition Service Pack 2 (Build 6002)
    SAMSUNG ELECTRONICS CO., LTD. 350V5C/350V5X/350V4C/350V4X/351V5C/351V5X/351V4C/351V4X/3540VC/3
    iTunes 11.0.2.26
    QuickTime not available
    FairPlay 2.3.31
    Apple Application Support 2.3.3
    iPod Updater Library 10.0d2
    CD Driver 2.2.3.0
    CD Driver DLL 2.1.3.1
    Apple Mobile Device 6.1.0.13
    Apple Mobile Device Driver 1.64.0.0
    Bonjour 3.0.0.10 (333.10)
    Gracenote SDK 1.9.6.502
    Gracenote MusicID 1.9.6.115
    Gracenote Submit 1.9.6.143
    Gracenote DSP 1.9.6.45
    iTunes Serial Number 0164B8580B9D29C8
    Current user is an administrator.
    The current local date and time is 2013-04-05 20:52:38.
    iTunes is not running in safe mode.
    WebKit accelerated compositing is enabled.
    HDCP is supported.
    Core Media is supported.
    **** External Plug-ins Information ****
    No external plug-ins installed.
    iPodService 11.0.2.26 (x64) is currently running.
    iTunesHelper 11.0.2.26 is currently running.
    Apple Mobile Device service 3.3.0.0 is currently running.
    **** CD/DVD Drive Tests ****
    No drivers in LowerFilters.
    UpperFilters: GEARAspiWDM (2.2.3.0),
    D: TSSTcorp CDDVDW, Rev
    Audio CD in drive.
    Found 13 songs on CD, playing time 61:26 on Audio CD.
    Track 1, start time 00:02:00
    Track 2, start time 03:39:55
    Track 3, start time 08:17:50
    Track 4, start time 12:53:69
    Track 5, start time 18:24:17
    Track 6, start time 28:46:23
    Track 7, start time 34:08:20
    Track 8, start time 38:02:72
    Track 9, start time 44:08:57
    Track 10, start time 47:24:54
    Track 11, start time 50:41:26
    Track 12, start time 55:01:28
    Track 13, start time 57:47:70
    Audio CD reading succeeded.
    Get drive speed succeeded.
    The drive CDR speeds are: 10 16 20 24.
    The drive CDRW speeds are: 10.
    The drive DVDR speeds are: 10.
    The drive DVDRW speeds are: 10.
    The last failed audio CD burn had error code 4310(0x000010d6). It happened on drive D: TSSTcorp CDDVDW on CDR media at speed 10X.
    I have the same problem and here is my diagnostics.....please help this is really annoying

  • Error in JDBC Adapter-"Error establishing socket"

    Hi,
    I am getting an error in the seander JDBC adapter. PFB the error:
    Error during database connection to the database URL 'jdbc:microsoft:sqlserver://Server Name;DatabaseName=DB Name;SelectMethod=cursor' using the JDBC driver 'com.microsoft.jdbc.sqlserver.SQLServerDriver': 'com.sap.aii.adapter.jdbc.sql.DriverManagerException: Cannot establish connection to URL 'jdbc:microsoft:sqlserver://Server Name;DatabaseName=DB Name;SelectMethod=cursor': SQLException: [Microsoft][SQLServer 2000 Driver for JDBC]Error establishing socket.'
    Can any one hlep me to resolve the error.
    Thanks,
    RK

    Hi,
    Also check whether you have given database connection parameters in the following format:
    JDBC Driver:
    com.microsoft.jdbc.sqlserver.SQLServerDriver
    Connection:   jdbc:microsoft:sqlserver://<HOSTNAME>:1433;DatabaseName=<xxxx>;SelectMethod=cursor
    I think the deployment is done, because you have not got "SAPClassNotFoundException" error.(If the deployment is not done, the driver file cant be located so this will be thrown...)
    Thanks & Regards,
    Senthil.

  • How do you fix error message "There is a problem with Adobe Acrobat/Reader. (6:6)

    How does one fix error message "There is a problem with Adobe Acrobat/Reader.
    If it is running, please exit and try again. (6:6)

    http://www.essexinfo.net/queens-road-residents-association/assets/documents/village-voices is one example but a whole lot of the material which has been uploaded as pdf files over the last four years is now unviewable - if you click on the link you just get a black page.  The main site url is http://www.essexinfo.net and our site is the Queens Road Residents Association.  I have just gone through every link on the site and a number of links when clicked on will not bring up the material.  I tried going into Adobe 10 on my computer and disenabling protected mode as was suggested on your forum and at first when I went back into the essex info site it seemed to have worked when I clicked on a link that had only produced a black page.  However when I went back to test all the other links I found that the problem was still re-occuring.  This is really weird as the site and my connections to it which I sometimes make by directly accessing the site and sometime via a link from our QRRA blog have always worked perfectly with no problems up to now.  I downloaded adobe 10.1 on 8 March 2011.
    I contacted essexinfo separately but they said everything seemed to be OK at their end working from within the system.
    If you can help I would appreciate it.
    Pat

  • How do I fix error cannot connect to Itunes store, How do I fix error cannot connect to Itunes store

    How do I fix error cannot connect to Itunes store, How do I fix error cannot

    Refer to this article:
    Can't connect to the iTunes Store
    http://support.apple.com/kb/TS1368

  • How do I fix error message "This document contains a link to an asset being upsampled. You should resize it smaller or right-mouse click on the asset in the Assets panel to see additional options." Which asset is it?

    I ab in Muse. How do I fix error message, This document contains a link to an asset being upsampled. You should resize it smaller or right-mouse click on the asset in the Assets panel to see additional options.

    You should ask in Help with using Adobe Muse CC
    This Cloud forum is not about using individual programs
    This Cloud forum is about the Cloud as a delivery & install process
    If you will start at the Forums Index https://forums.adobe.com/welcome
    You will be able to select a forum for the specific Adobe product(s) you use
    Click the "down arrow" symbol on the right (where it says All communities) to open the drop down list and scroll

  • "Error establishing socket" error on JDBC Receiver Channel.

    Dear All,
    Scenario: Soap to JDBC.
    I m getting error on JDBC Receiver Channel. messages are processed succesfully on ABAP Stack and receiver channel is on below error:
    ERROR : Message processing failed. Cause: com.sap.aii.af.ra.ms.api.RecoverableException: Error when attempting to get processing resources: com.sap.aii.af.service.util.concurrent.ResourcePoolException: Unable to create new pooled resource: DriverManagerException: Cannot establish connection to URL 'jdbc:microsoft:sqlserver://156.5.202.194:3312;DatabaseName=ODW': SQLException: [Microsoft][SQLServer 2000 Driver for JDBC]Error establishing socket.
    Note: i already tested another interface with this same IP and it was fine with different port.
    jdbc:microsoft:sqlserver://IP:PORT;DatabaseName=Name
    Regards,
    Manikandan

    and it was fine with different port
    socket exception is (always) related to port....did you check with the network team about this new Port?

Maybe you are looking for