'Connection reset by peer' and other punchlines - Help!

I recently downloaded the latest version of the the JDBC driver and now the connection to the database drops within a few minutes with the exception "Connection reset by peer". The driver version is
Version 8.0.5.2 JDBC(Thin) for NT. I am connecting to the 8.0.5 on a DEC Alpha machine.
How does one keep the connection alive and prevent it from dropping so often. Why does the connection drop so quickly? Is there a setting on the database?
Any help would be appreciated!
With the older version of the driver the connection dropped intermittently after a few hours or even days with the exception:
"No more data to read from socket". Subsequent attempts to reconnect within the code gave exceptions like:
"Bigger type length than Maximum" and
"Protocol violation"
null

This could be a number of things.  The DB could be killing sessions with something like a resource manager.  The network could be dropping. There could be an ora-600 that is aborting a connection.  Turn the debugging on by following this blog entry and let us know the results
https://cdivilly.wordpress.com/2013/03/08/configuring-logging-in-oracle-application-express-listener-2-0-1/

Similar Messages

  • Javax.servlet.ServletException: Connection reset by peer....Help needed..

    Initially, when I clicked on my JSPs, everything was fine. I was able to retrieve data successfully from all the JSPs. However, after much clicking through the JSPs. I was not able to access the JSPs and the Internal Servlet Error was shown.
    Below is my Tomcat.log:
    Context log: path="/Aedge" Error in jsp service() : Connection reset by peer: socket write error
    javax.servlet.ServletException: Connection reset by peer: socket write error
         at org.apache.jasper.runtime.JspServlet.service(JspServlet.java:375)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at org.apache.tomcat.core.ServletWrapper.handleRequest(ServletWrapper.java:503)
         at org.apache.tomcat.core.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:163)
         at org.apache.tomcat.servlets.DefaultServlet.doGet(DefaultServlet.java:187)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at org.apache.tomcat.core.ServletWrapper.handleRequest(ServletWrapper.java:503)
         at org.apache.tomcat.core.ContextManager.service(ContextManager.java:559)
         at org.apache.tomcat.service.http.HttpConnectionHandler.processConnection(HttpConnectionHandler.java:160)
         at org.apache.tomcat.service.TcpConnectionThread.run(SimpleTcpEndpoint.java:338)
         at java.lang.Thread.run(Unknown Source)
    Context log: path="/Aedge" <b>Internal Servlet Error:</b><br>.....
    What is the problem here? How can I solve this as I had to restart my Tomcat once a while due to this problem.

    ok.. I have db classes where all my sql statements methods are being displayed.. In each db class, there will be a getInstance() method to create the connection. Below is one of my db class.. How to I modified the things you had mentioned in my codes..
    package aedgeSoft.access;
    import aedgeSoft.business.*;
    import java.sql.*;
    import java.util.*;
    import java.util.Date;
    import java.io.*;
    public class DBMemberType
         private Connection con;
         private static DBMemberType instance = null;
         public static DBMemberType getInstance()
              try
                   if(instance==null)
                        instance = new DBMemberType();
              catch(SQLException e)
                   System.out.println("Problems with loading database in DBMemberType");
              catch(ClassNotFoundException e)
                   System.out.println("Problems with loading db driver in DBMemberType");
              finally
                   return instance;
         private DBMemberType() throws SQLException, ClassNotFoundException
              try{
              Class.forName("com.microsoft.jdbc.sqlserver.SQLServerDriver").newInstance();
              con = DriverManager.getConnection("jdbc:microsoft:sqlserver://localhost:1433;user=username;password=password;DatabaseName=db");
              catch(InstantiationException e)
                   e.printStackTrace();
              catch(IllegalAccessException e)
                   e.printStackTrace();
         //add memberType
         public boolean addMemberType(MemberType mt)
    ..........

  • Connection reset by peer, broken pipe...

    This part of sockets is just needlessly confusing. Perhaps someone can shed some light on this?
    Sometimes I get an IOException with as message "Connection reset by peer". Other times, it's "broken pipe". What is the difference? Why isn't there a way other than parsing the exception message text to figure out if it's a client 'hanging up on you' unexpectedly or something else?
    Secondly, in my NIO server, all webbrowsers, but for some reason firefox especially, really likes to make a full request, than grab 0 to 99 bytes (the full return HTTP message size is much larger than that), and then silently hang up and immediately re-request the same resource again. Sometimes 10 to 15 times in a row. Firefox shows no errors of any kind when it does this. the read() operation on the socket returns -1 which is what ends up causing the close.
    Is this because '-1' doesn't really mean: The socket is closed, it actually just means: the socket INPUT is closed but you can still send?
    And if it is the latter, how the heck do I detect a connection in lockdown state in a non-blocking environment?

    Sometimes I get an IOException with as message
    "Connection reset by peer". Other times, it's "broken
    pipe". What is the difference? Why isn't there a way
    other than parsing the exception message text to
    figure out if it's a client 'hanging up on you'
    unexpectedly or something else?I agree: I would love there to be a ConnectionResetException. Anyway, practically any IOException on a socket operation means you should close it (and forget about it if you're a server).
    Secondly, in my NIO server, all webbrowsers, but for
    some reason firefox especially, really likes to make
    a full request, than grab 0 to 99 bytes (the full
    return HTTP message size is much larger than that),
    and then silently hang up and immediately re-request
    the same resource again.Maybe it is doing a HEAD request?
    Is this because '-1' doesn't really mean: The socket
    is closed, it actually just means: the socket INPUT
    is closed but you can still send?It actually means a one-way close originating from the other end, which could be the result of either a close or a shutdownOutput() by the peer. If it was a shutdownOutput() you can indeed still send.
    And if it is the latter, how the heck do I detect a
    connection in lockdown state in a non-blocking
    environment?What do you mean by 'lockdown state'? If you mean how do you detect when the peer finally closes after a shutdown, the answer is that you eventually get a connection reset when writing, which is where we came in. If you have a socket channel which has detected EOS as above and you don't have any more data to send to it, close it.

  • WSAECONNRESET Connection reset by peer every 10 min

    We are getting an error WSAECONNRESET Connection reset by peer every 10 min. We are running SAP on windows Small Business Server.
    If I log in on server or within LAN it is working file without any problem. When we use WAN or outside network and connect SAP using SAP router it is giving an error of Connection reset by peer every 10 min.
    I have reviewed OSS 155147 - WinNT: Connection reset by peer, 107407 - Win95: Connection Reset by Peer and 500235 - Network Diagnosis with NIPING without any success. I have played with registry parameters as per OSS 413330.
    Could any one explain how to resolve this problem?
    Thanks in advance...

    > But the consistency is It reset exactly every 10 min.
    Maybe you connection (whatever technical kind it is) resets connections all 10 minutes, maybe a firewall tears down the connection after that time... without knowing anything about the infrastructure I can just guess.
    If the system is running internally fine without any interruptions then it's not a problem of the SAP system.
    Markus

  • "Connection reset by peer"   Help Me

    Hi
    I have j2re1.4.2_08 and Oracle 9.2
    When I tried to update database with huge data I got following exception:
    java.sql.SQLException: Io exception: Connection reset by peer: socket write error
    at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:134)
    at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:179)
    at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:333)
    at oracle.jdbc.driver.OracleStatement.executeNonQuery(OracleStatement.java:2061)
    at oracle.jdbc.driver.OracleStatement.doExecuteOther(OracleStatement.java:1940)
    at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:2709)
    at oracle.jdbc.driver.OraclePreparedStatement.executeUpdate(OraclePreparedStatement.java:589)
    at edu.bnmit.BookDBUpdateThread.run(BookDBUpdateThread.java:80)
    at edu.bnmit.BookDBUpdateThread.update(BookDBUpdateThread.java:46)
    at java.lang.Thread.run(null:-1)
    method used to update database is:
    void update(Books b[]){
    Connection dbConnection;
    PreparedStatement stmt;
    try{
    dbConnection = DriverManager.getConnection(
    dbConnection.setAutoCommit(false);
    String sqlStmt = "UPDATE Books SET " +
    "bookName=?, bookAuthor=?" +
    "WHERE bookId=?";
    stmt = dbConnection.prepareStatement(sqlStmt);
    for(int i = 0; i < b.length; i++){
    stmt.setString(1,b.bookName);
    stmt.setString(2,b.bookAuthor);
    stmt.setInt(3,b.bookId);
    stmt.executeUpdate();
    dbConnection.commit();
    stmt.close();
    dbConnection.close();
    }catch(SQLException e){
    System.err.println("Error While Updating Table");
    String s = e.toString();
    StackTraceElement trace[] = e.getStackTrace();
    for(int j = 0; j < trace.length; j++){
    s += "\n\tat "
    + trace[j].getClassName() + trace[j].getMethodName()
    + "(" + trace[j].getFileName()
    + ": " + trace[j].getLineNumber() + ")";
    System.err.println(s);
    }Orcale server is distently placed. I get this exception when I send 10,000+ records to update.
    Can anyone help me.
    Thanks

    [Just a note: the stack does not match the code posted here. In the stack, executeUpdate() is called from BookDBUpdateThread.run() whereas your code shows that it's called from BookDBUpdateThread.update().  It helps to post the correct stack/code.)
    The problem might just be that you have an unreliable connection. The fact that you have a long running operation is just exposing connection drops that may otherwise go unnoticed.
    I suggest that you test this over a more reliable connection. If that is not possible, split the update into multiple shorter running updates. Of course, this would only work if the updates do not require a single transaction. If a single transaction is required, you can use your own XATransaction (the details on XATransactions are beyond the scope of this forum.)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           

  • "Connection reset by peer" using firewall between iFS API and Database

    Hi ..
    We have a webapplication running on a websphere server using the iFS API to connect to a iFS schema through a firewall ( PIX ). The firewall will close idle connections after a while, and this results in "Connection reset by peer" errors in our application.
    Firewall guys says that configuring the firewall not to close connections, is not an option.
    Does anybody have experiences with this, suggestions on how to deal with this?
    We are running iFS 9.0.1.
    Thanks
    Anders Monrad
    Danisco IT

    I'm having the same problem, using a PIX firewall, however, I have the firewall setup between OHS & OC4J, also between OC4J and our application database.
    I have a solution for the OC4J and app DB. If I set the expire_time = 10 in sqlnet.ora, this will ensure that sqlnet will ping the connection between OC4j and the DB every 10 minutes, thus the firewall will not close the connection due to inactivity.
    However, does anyone have a solution for the OHS & OC4J connection? Can this be resolved with configuration rather than having to use an app to ping it?
    [I realise I could write an app to retrieve a page every so often to keep the connection open, but I want to do it with configuration]
    Thanks in Advance.

  • Idle Timeout and "Connection reset by peer"

    Is there a connection between the Idle Timeout Setting and getting the "Connection reset by peer error". If I increase the  Idle Timeout value am I less likely to get the "Connection reset by peer " issue. It is currently set to 30 seconds
    We are printing over a WAN and regularly get this error on a hp LaserJet 4250n
    Also what is the difference between Idle Timeout and I-O timeout ?

    Interesting, I am going to do some research into this tomorrow, as this is not a feature that I work with much. I will get back in touch with you once I have more information so we can test different settings to see if we are able to resolve the issue. 
    -Spencer 
    Have a wonderful day!  

  • HT5313 I have been trying for weeks to download update 10.7.5 and cannot do so.  I do get a message at the end - "connection reset by peer".  Can anyone shed any light on why I cannot download this update and what the message may mean?  Thanks.

    I have been trying for weeks to download update 10.7.5 and cannot do so.  I do get a message at the end - "connection reset by peer".  Can anyone shed any light on why I cannot download this update and what the message may mean?  Thanks.

    Take a look at this discussion and the ones listed under "more like this" in the right column:
    https://discussions.apple.com/thread/4166820?start=0&tstart=0

  • HT5167 When I try to install the update"MAC OS X Update Combined, I get a message that says it cannot be saved & connection reset by peer.  What do I need to do to get this update installed.  I just purchased my first iMAC and don't know anything about it

    When I try to install the update"MAC OS X Update Combined, I get a message that says it cannot be saved & connection reset by peer.  What do I need to do to get this update installed.  I just purchased my first iMAC and don't know anything about it.

    Try here:
    http://support.apple.com/kb/DL1524

  • Socket read error: connection reset by peer

    Hi.
    Has anybody experienced the error message �Socket read error: connection reset by peer�
    Please see below for detailed information.
    Appreciate your help
    Regards
    RT
    Enviroment specification
    Server: HP/UX 11.00 64-bit, Oracle RDBMS 8.1.6.0.0 64-bit
    2 firewalls between client and db.
    Client:
    Win 2000,
    SP3,
    Oracle Client 8.1.7.0.0 ,JDBC OCI (thin JDBC driver,class12.zip)
    JDK 1.3
    JRUN3.0
    The TCP protocol is being used in the communication
    Error messages
    Web Users receive:           Socket read error: connection reset by peer
    Trace files on the sever:      Read unexpected EOF ERROR on 18.
    Explanation: The error in the server sqlnet trace file, suggests that a client connection has terminated abnormally, i.e. client machine powered off, a cable removed or a network connection aborted without warning. No user has complained of such a problem and there is no client trace with an error.
    The problem
    The users of the java web application, experiencing an exception almost once or twice a day.
    The JRUN web-server reports broken connections to the db and client are receiving "connection reset by peer".
    At the moment when the errors occurs the users just have to wait a while(2-10 min) and then they can use the web application again.(no action is taken)
    This problem can not be reproduced. The problem happens only occasionally when the network is under heavy load and new DB connection is being created.
    The application
    The java web-application uses a customized connection pooling against the database. This pool is shared among all the users of the website. whenever a user process needs to fetch data from the database, a free connection from this pool is allocated. The application is testing if the connection is valid before making a transaction (select '1' from dual). When the error occurs a ORA-3113 end-of-file on communication channel is returned to the application.
    The path between the client and db involves at least two firewalls. The firewalls are opened for sql*net traffic. The network group can tell that enquiries from the app.server is not getting feedback from the db. They have not however, identified if the enquiries are reaching the db-srever, or if they are stopped earlier in the network.
    Around 1000 users, are using other applications which uses dedicated sqlnet connections against the db and they have not experienced any problems.
    Issues considered
    Connection pooling
    It is a customized connection pooling, developed by Lindorff developers.
    I have read through the source code for the connection pooling and it does the job as it should, and in case of bad connection, it tries to create a new connection.
    The log file shows that the call to the method DriverManager.getConnection() hangs until the server goes down, which is probably because of the fact that the method DriverManager.setLoginTimeout(), does not take effect and timeout value is Zero. ( According to oracle , Oracle JDBC does not support login timeouts and calling the static DriverManager.setLoginTimeout() method will have no effect).
    Firewall
    One thing to consider is when the firewall may decide to shut down the socket due to long inactivity of a connection. This will cause problems to JDBC Connection Pool because the pool is not aware of this disconnection at the TCP/IP level; until someone checks out the connection from the pool and tries to use it. The user will get a Socket read error: connection reset by peer.
    Jrun timeout paramter is less than the firewall�s timeout so the firewall will not close a connection before Jrun does.
    Number of processes the DB can handle
    Processes parameter is 1300, , they have not experienced the Oracle error msg �max # of processes reached�.
    Port redirection through a firewall:
    Since the firewall has a sql net proxy Port redirection through a firewall is not a problem. Problems with port redirection only appear at connect time, but in this situation the connections fail long after the connection is established.
    The network group
    The network people who investigaged the problem at Lindorff report that there are a significant amount of "dropped packages" between the database server and the jdbc client (web-application) 24 hrs. The reason for this is "unknown established TCP packet" which means that the firewall does not consider these packages to be part of an already established session. The network group believes this happen because one of the hosts send a RESET or FIN signal which the firewall have noticed but are not received by the other host.
    It seems like the firewall are dropping packages bacause of "Unknown
    established TCP packet" from both the JDBC client and the TNSLISTENER on the database server. The dropped packages are SQL*Net v2 traffic so clearly Oracle products are involved

    Presumably something is working.
    Thus the problem is not with your code. At least not the database part that you have control over.
    That error occurs when the other side closes the socket. Presumably you are catching lost connection exceptions and trying to restore it.

  • Connection reset by peer problem

    I have the following code, and every time I run it i get a "java.net.SocketException: Connection reset by peer: socket write error" exception. Why is that? This is the first time I'm writing a network client application, so please help :)
    Socket s = new Socket("127.0.0.1",8080);
    OutputStream out = new BufferedOutputStream(s.getOutputStream());
    InputStream in = new BufferedInputStream(s.getInputStream());
    out.write("server status\r\n".getBytes());
    //out.flush();
    StringBuffer responseLine = new StringBuffer();
    int c;
    while(in.available() > 0) {
      c = in.read();
      responseLine.append((char)c);
    //out.close();
    //in.close();
    //s.close();
    System.out.println(responseLine.toString());P.S. It's the same problem with or wothout the out.flush(), and with or wothout closing my streams and socket.

    InputStream = new BufferedReader
    Um..just look at that code, oh boy.
    InputStream is a class and so is
    BufferedReader
    Two different classes (event if they are subclasses)
    cant be directly assigned to each other.The human eye sometimes sees what it wants to see and not what it is... :-)
    I think the problem is with the protocol and the timing. The while loop may never execute due to timing:
    1. Client's "server status" request takes a few ms to arrive in the server.
    2. In the meanwhile, in.available is zero and the client does not enter the loop and does not append any characters to the string buffer.
    3. Server writes its status on the socket which arrives at the client which is no longer reading it a few ms later.
    Which brings us to the protocol:
    If the server status is a fixed length block of data, try reading it into a single byte buffer.
    If it is variable length or text, use a BufferedReader on the socket, read the response a line at a time and make the server end the report with a token (like a last line of "END_OF_SERVER_STATUS_REPORT" or "01234567890123456789012345678901234567890123456789", whatever).
    Don't check if data is available on a socket if you know it should be, sooner or later, and you don't want to multiplex your flow on data availability.

  • Io exception: Connection reset by peer: JVM_recv in socket input stream read

    We are developing a new J2EE app using JDev, OC4J, servlets, and EJBs. We have determined that our firewall is closing database connections that have been idle for 1 hour. This is a security requirement that cannot be changed. When we try to use these idle connections in both stateless and entity beans, we consistently receive this or a similar error message:
    "ServletSACategoryList: Error invoking EJB procedure. Exception: java.sql.SQLException: StatelessSysAdminBean::getCategoryList - Io exception: Connection reset by peer: JVM_recv in socket input stream read "
    Environment:
    Oracle 9iAS 9.0.2.0.0
    Database: Oracle 8.1.7
    JDBC 8.1.7
    JDK 1.3
    JDev 9.0.2.829
    We are using the ejb-location attribute within data-sources.xml for JNDI lookup of the DataSource. Here is what this file looks like:
    <data-sources>
    <data-source
    class="oracle.jdbc.pool.OracleDataSource"
    name="jdbc/OracleDS"
    location="jdbc/OracleCoreDS"
    xa-location="jdbc/xa/OracleXADS"
    ejb-location="jdbc/OraclePoolDS"
    url="jdbc:oracle:thin:@###.###.#.###:1521:dev1"
    connection-driver="oracle.jdbc.driver.OracleDriver"
    username="????????"
    password="????????"
    max-connections="4"
    wait-timeout="20"
    min-connections="1"
    inactivity-timeout="60"
    connection-retry-interval="1"
    max-connect-attempts="3"
    />
    </data-sources>
    After calling getConnection() on the Connection object in my stateless bean, I have tried checking if the Connection object is null or isClosed(), I have caught any Exception, and looped to try again, but nothing has worked.
    Please respond to [email protected] or directly to this post if you can help in any way.
    Thank you,
    - Rob

    Hi Robert,
    If you don't mind, I can only offer a few suggestions for things
    to try -- I'm afraid I don't have a solution for you. Of-course,
    you may have already tried these things, so please excuse me if
    this is the case.
    Firstly, your "data-sources.xml" file looks "different". Have
    you read the "Data Sources" chapter of the "Oracle9iAS Containers
    for J2EE Services Guide, Release 2 (9.0.2)"? It is accessible
    from here:
    http://otn.oracle.com/docs/products/ias/doc_library/90200doc_otn/web.902/a95879/ds.htm#1004903
    Also, have you tried running OC4J in "debug" mode? This web
    page has more details:
    http://kb.atlassian.com/content/atlassian/howto/orionproperties.jsp
    I get the impression from the information you have supplied,
    that you may not be explicitly closing your database connections
    in your code. It looks to me like you are obtaining a database
    connection in your session bean, and then keeping it for the
    lifetime of that bean. Is that correct? I think it's better
    to obtain a connection when you need to interact with the database,
    and then close the connection immediately after completing the
    interaction with the database (but that's just my opinion).
    Lastly, if you haven't already discovered them, these web sites
    may also be of help:
    http://www.orionserver.com
    http://www.orionsupport.com
    http://www.elephantwalker.com
    Hope this helps you.
    Good Luck,
    Avi.

  • IOException: Connection reset by peer: JVM_recv in socket input stream read

    hi
    I encountered a problem : a program throw out an exception:java.io.IOException: Io exception:
    Connection reset by peer: JVM_recv in socket input stream read.
    I tried my best to resolve it ,but unfortunately,i didn't know what caused the exception.
    the following is my application environment:
    I have two PC(Win2000os),one is a server which installed oracle9.2.0.2 and jdeveloper9.0.3,the another is a
    client which only intalled jdeveloper9.0.3.Two days ago,i performed a web application on my client with
    jdeveloper,and it includes some JSP and a javabean files.JSP Page finished uploading client xml file to a
    folder on server and the javabean finished loading the xml file into a xmltype column.I can make sure the
    connection is established and the javabean is OK,beacause my some jsp page can successfully use
    <jsp:usebean> tag and use the javabean's some other public interfaces,except the interface that finishs
    loading the xml file into a xmltype(clob) column.
    Then i do many tests!I changed the javabean to a java class incluse a main method beacause it is easy to
    debug.Finally i found the following code caused the exception:
    public CLOB writetoClob( CLOB clob, InputStream is )throws SQLException, IOException {
    InputStreamReader reader = new InputStreamReader( is );
    Writer writer = clob.getCharacterOutputStream( );
    char[] buffer = new char[clob.getChunkSize(  )];
    int charsRead;
    for ( charsRead = reader.read( buffer ); charsRead > -1;charsRead = reader.read( buffer ) ) {
    writer.write( buffer, 0, charsRead );
    writer.close();
    return clob;
    when it runs to writer.close(),the exception is caused!
    Then i copy the java class to the server,it runs ok!
    That is to say ,the same code,the different result!
    But when i run my web application on server with jdeveloper Embedded OC4J Server and a jsp page loaded javabean
    and run to mentioned code ,the same exception occured!
    I checked the application log in event viewer,the descriptions was:
    The data buffer created for the "AppleTalk" service in the "C:\WINNT\system32\atkctrs.dll" library is not
    aligned on an 8-byte boundary. This may cause problems for applications that are trying to read the
    performance data buffer. Contact the manufacturer of this library or service to have this problem corrected or
    to get a newer version of this library.
    I search some some resolution about this exception with web and someone sayed :
    This basically means that a network error occurred while the client was receiving data from the server. But
    what is really happening is that the server actually accepts the connection, processes the request, and sends a
    reply to the client. However, when the server closes the socket, the client believes that the connection has
    been terminated abnormally because the socket implementation sends a TCP reset segment telling the client to
    throw away the data and report an error.
    Sometimes, this problem is caused by not properly closing the input/output streams and the socket connection.
    Make sure you close the input/output streams and socket connection properly. If everything is closed properly,
    however, and the problem persists, you can work around it by adding Thread.sleep(1000) before closing the
    streams and the socket. This technique, however, is not reliable and may not work on all systems.
    In general,the following information is conclution:
    Web application runs error both on client and on server.
    If it was changed to a client java class,it only run ok on server!
    i have done anything that i can do now,i feel depressed very much!
    how can i resolve the problem!
    Any a little help will be appreciated!
    regards!
    Thanks
    Jiawei ZHAO

    How can i solve the problem.
    Thanks in advance!
    Jiawei Zhao

  • Trying to insert a Large CLOB : connection reset by peer

    I am Trying to insert a Large CLOB .. i get this error message
    java.sql.SQLException: Io exception: connection reset by peer
    I am using a prepared statement to insert a Clob. It works fine with small data.
    Thanks for your help in advance.

    It might help if you gave more information - this probably depends on your database and driver, so giving info on them will help.

  • Remote Desktop on Mac connecting to 2008 R2 Server produces "Connection Reset by Peer" error when idle 20 mins

    Mac Clients are running 10.9.2 Mavericks. 
    Client is Microsoft Remote Desktop 8.05.
    Clients are mixed in how they connect to the Windows 2008 R2 server, some
    are on Wifi some are on Wired Ethernet.
    If you connect to the Server through the RD Client, and get on you work 
    and if you then say go idle  ( still connected but not doing anything such as 
    printing from the Server or in an Application on the Server) then after 20 mins it
    (the client) throws up a "Connection reset by Peer" error.
    You click OK, and then it breaks connection. You can however reconnect without issue.
    We have currently about six users who are using the RD Connection to access QuickBooks on
    this 2008 R2 server. Four are on Macs and get the errors. Two are on PCs and do not get the errors.
    Here is the log file from one of the Macs that had the error:
    [2014-Apr-07 10:34:07] RDP (0): Server shows cursor
    [2014-Apr-07 10:34:09] RDP (0): Server hides cursor
    [2014-Apr-07 10:34:21] RDP (0): Server shows cursor
    [2014-Apr-07 10:34:22] RDP (0): Server hides cursor
    [2014-Apr-07 10:34:25] RDP (0): Server shows cursor
    [2014-Apr-07 11:00:29] RDP (0): Protocol state changed to: ProtocolDisconnected(8)
    [2014-Apr-07 11:00:29] RDP (0): ------ END ACTIVE CONNECTION ------
    [2014-Apr-07 11:00:29] RDP (0): Exception caught: Exception in file '../../librdp/legacytcpstreamadapter.cpp' at line 322
    User Message : Failed to read from socket: -1
    [2014-Apr-07 11:02:35] RDP (0): Final rdp configuration used: screen mode id:i:2
    use multimon:i:1
    session bpp:i:24
    full address:s:192.168.16.x
    audiomode:i:0
    username:s:m
    disable wallpaper:i:0
    disable full window drag:i:0
    disable menu anims:i:0
    disable themes:i:0
    alternate shell:s:
    shell working directory:s:
    authentication level:i:2
    connect to console:i:0
    gatewayusagemethod:i:0
    disable cursor setting:i:0
    allow font smoothing:i:1
    allow desktop com:1
    bookmarktype:i:3
    use redirection server name:i:0
    [2014-Apr-07 11:02:35] RDP (0): --- BEGIN INTERFACE LIST ---
    [2014-Apr-07 11:02:35] RDP (0): lo0 af=18 addr= netmask=
    [2014-Apr-07 11:02:35] RDP (0): lo0 af=30 (AF_INET6) addr=::1 netmask=ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff
    [2014-Apr-07 11:02:35] RDP (0): lo0 af=2 (AF_INET) addr=127.0.0.1 netmask=255.0.0.0
    [2014-Apr-07 11:02:35] RDP (0): lo0 af=30 (AF_INET6) addr=fe80::1%lo0 netmask=ffff:ffff:ffff:ffff::
    [2014-Apr-07 11:02:35] RDP (0): gif0 af=18 addr= netmask=
    [2014-Apr-07 11:02:35] RDP (0): stf0 af=18 addr= netmask=
    [2014-Apr-07 11:02:35] RDP (0): en0 af=18 addr= netmask=
    [2014-Apr-07 11:02:35] RDP (0): en0 af=30 (AF_INET6) addr=fe80::12dd:b1ff:febe:9771%en0 netmask=ffff:ffff:ffff:ffff::
    [2014-Apr-07 11:02:35] RDP (0): en0 af=2 (AF_INET) addr=192.168.16.1xx netmask=255.255.255.0
    [2014-Apr-07 11:02:35] RDP (0): en1 af=18 addr= netmask=
    [2014-Apr-07 11:02:35] RDP (0): en4 af=18 addr= netmask=
    [2014-Apr-07 11:02:35] RDP (0): en3 af=18 addr= netmask=
    [2014-Apr-07 11:02:35] RDP (0): p2p0 af=18 addr= netmask=
    [2014-Apr-07 11:02:35] RDP (0): bridge0 af=18 addr= netmask=
    [2014-Apr-07 11:02:35] RDP (0): --- END INTERFACE LIST ---
    [2014-Apr-07 11:02:35] RDP (0): ----- BEGIN ACTIVE CONNECTION -----
    [2014-Apr-07 11:02:35] RDP (0): client version: 8.0.24428
    [2014-Apr-07 11:02:35] RDP (0): Protocol state changed to: ProtocolConnectingNetwork(1)
    [2014-Apr-07 11:02:35] RDP (0): Resolved '192.168.16.x' to '192.168.16.x' using NameResolveMethod_DNS(1)
    [2014-Apr-07 11:02:35] RDP (0): Protocol state changed to: ProtocolNegotiatingCredentials(2)
    [2014-Apr-07 11:02:35] RDP (0): Protocol state changed to: ProtocolConnectingRDP(3)
    [2014-Apr-07 11:02:35] RDP (0): Protocol state changed to: ProtocolInactive(4)
    [2014-Apr-07 11:02:35] RDP (0): Server supports RAIL
    [2014-Apr-07 11:02:35] RDP (0): Protocol state changed to: ProtocolActive(5)
    [2014-Apr-07 11:02:35] RDP (0): Protocol state changed to: ProtocolInactive(4)
    [2014-Apr-07 11:02:35] RDP (0): Server supports RAIL
    [2014-Apr-07 11:02:35] RDP (0): Protocol state changed to: ProtocolActive(5)
    [2014-Apr-07 11:09:38] RDP (0): Server hides cursor
    [2014-Apr-07 11:09:38] RDP (0): Server shows cursor
    [2014-Apr-07 11:09:38] RDP (0): Server hides cursor
    [2014-Apr-07 11:09:38] RDP (0): Server shows cursor
    [2014-Apr-07 11:09:38] RDP (0): Server hides cursor
    [2014-Apr-07 11:09:38] RDP (0): Server shows cursor
    [2014-Apr-07 12:16:31] RDP (0): Protocol state changed to: ProtocolDisconnected(8)
    [2014-Apr-07 12:16:31] RDP (0): Exception caught: Exception in file '../../librdp/legacytcpstreamadapter.cpp' at line 322
    User Message : Failed to read from socket: -1
    [2014-Apr-07 12:16:31] RDP (0): ------ END ACTIVE CONNECTION ------
    [2014-Apr-07 12:21:42] RDP (0): Final rdp configuration used: screen mode id:i:2
    use multimon:i:1
    session bpp:i:24
    full address:s:192.168.16.x
    audiomode:i:0
    username:s:m
    disable wallpaper:i:0
    disable full window drag:i:0
    disable menu anims:i:0
    disable themes:i:0
    alternate shell:s:
    shell working directory:s:
    authentication level:i:2
    connect to console:i:0
    gatewayusagemethod:i:0
    disable cursor setting:i:0
    allow font smoothing:i:1
    allow desktop com:1
    bookmarktype:i:3
    use redirection server name:i:0
    [2014-Apr-07 12:21:42] RDP (0): --- BEGIN INTERFACE LIST ---
    [2014-Apr-07 12:21:42] RDP (0): lo0 af=18 addr= netmask=
    [2014-Apr-07 12:21:42] RDP (0): lo0 af=30 (AF_INET6) addr=::1 netmask=ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff
    [2014-Apr-07 12:21:42] RDP (0): lo0 af=2 (AF_INET) addr=127.0.0.1 netmask=255.0.0.0
    [2014-Apr-07 12:21:42] RDP (0): lo0 af=30 (AF_INET6) addr=fe80::1%lo0 netmask=ffff:ffff:ffff:ffff::
    [2014-Apr-07 12:21:42] RDP (0): gif0 af=18 addr= netmask=
    [2014-Apr-07 12:21:42] RDP (0): stf0 af=18 addr= netmask=
    [2014-Apr-07 12:21:42] RDP (0): en0 af=18 addr= netmask=
    [2014-Apr-07 12:21:42] RDP (0): en0 af=30 (AF_INET6) addr=fe80::12dd:b1ff:febe:9771%en0 netmask=ffff:ffff:ffff:ffff::
    [2014-Apr-07 12:21:42] RDP (0): en0 af=2 (AF_INET) addr=192.168.16.1xx netmask=255.255.255.0
    [2014-Apr-07 12:21:42] RDP (0): en1 af=18 addr= netmask=
    [2014-Apr-07 12:21:42] RDP (0): en4 af=18 addr= netmask=
    [2014-Apr-07 12:21:42] RDP (0): en3 af=18 addr= netmask=
    [2014-Apr-07 12:21:42] RDP (0): p2p0 af=18 addr= netmask=
    [2014-Apr-07 12:21:42] RDP (0): bridge0 af=18 addr= netmask=
    [2014-Apr-07 12:21:42] RDP (0): --- END INTERFACE LIST ---
    [2014-Apr-07 12:21:42] RDP (0): ----- BEGIN ACTIVE CONNECTION -----
    [2014-Apr-07 12:21:42] RDP (0): client version: 8.0.24428
    [2014-Apr-07 12:21:42] RDP (0): Protocol state changed to: ProtocolConnectingNetwork(1)
    [2014-Apr-07 12:21:42] RDP (0): Resolved '192.168.16.x' to '192.168.16.x' using NameResolveMethod_DNS(1)
    [2014-Apr-07 12:21:42] RDP (0): Protocol state changed to: ProtocolNegotiatingCredentials(2)
    [2014-Apr-07 12:21:43] RDP (0): Protocol state changed to: ProtocolConnectingRDP(3)
    [2014-Apr-07 12:21:43] RDP (0): Protocol state changed to: ProtocolInactive(4)
    [2014-Apr-07 12:21:43] RDP (0): Server supports RAIL
    [2014-Apr-07 12:21:43] RDP (0): Protocol state changed to: ProtocolActive(5)
    [2014-Apr-07 12:21:43] RDP (0): Protocol state changed to: ProtocolInactive(4)
    [2014-Apr-07 12:21:43] RDP (0): Server supports RAIL
    [2014-Apr-07 12:21:43] RDP (0): Protocol state changed to: ProtocolActive(5)
    [2014-Apr-07 15:30:19] RDP (0): Protocol state changed to: ProtocolDisconnected(8)
    [2014-Apr-07 15:30:19] RDP (0): Exception caught: Exception in file '../../librdp/legacytcpstreamadapter.cpp' at line 322
    User Message : Failed to read from socket: -1
    [2014-Apr-07 15:30:19] RDP (0): ------ END ACTIVE CONNECTION ------
    [2014-Apr-07 15:30:22] RDP (0): Final rdp configuration used: screen mode id:i:2
    use multimon:i:1
    session bpp:i:24
    full address:s:192.168.16.x
    audiomode:i:0
    username:s:m
    disable wallpaper:i:0
    disable full window drag:i:0
    disable menu anims:i:0
    disable themes:i:0
    alternate shell:s:
    shell working directory:s:
    authentication level:i:2
    connect to console:i:0
    gatewayusagemethod:i:0
    disable cursor setting:i:0
    allow font smoothing:i:1
    allow desktop com:1
    bookmarktype:i:3
    use redirection server name:i:0
    [2014-Apr-07 15:30:22] RDP (0): --- BEGIN INTERFACE LIST ---
    [2014-Apr-07 15:30:22] RDP (0): lo0 af=18 addr= netmask=
    [2014-Apr-07 15:30:22] RDP (0): lo0 af=30 (AF_INET6) addr=::1 netmask=ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff
    [2014-Apr-07 15:30:22] RDP (0): lo0 af=2 (AF_INET) addr=127.0.0.1 netmask=255.0.0.0
    [2014-Apr-07 15:30:22] RDP (0): lo0 af=30 (AF_INET6) addr=fe80::1%lo0 netmask=ffff:ffff:ffff:ffff::
    [2014-Apr-07 15:30:22] RDP (0): gif0 af=18 addr= netmask=
    [2014-Apr-07 15:30:22] RDP (0): stf0 af=18 addr= netmask=
    [2014-Apr-07 15:30:22] RDP (0): en0 af=18 addr= netmask=
    [2014-Apr-07 15:30:22] RDP (0): en0 af=30 (AF_INET6) addr=fe80::12dd:b1ff:febe:9771%en0 netmask=ffff:ffff:ffff:ffff::
    [2014-Apr-07 15:30:22] RDP (0): en0 af=2 (AF_INET) addr=192.168.16.1xx netmask=255.255.255.0
    [2014-Apr-07 15:30:22] RDP (0): en1 af=18 addr= netmask=
    [2014-Apr-07 15:30:22] RDP (0): en4 af=18 addr= netmask=
    [2014-Apr-07 15:30:22] RDP (0): en3 af=18 addr= netmask=
    [2014-Apr-07 15:30:22] RDP (0): p2p0 af=18 addr= netmask=
    [2014-Apr-07 15:30:22] RDP (0): bridge0 af=18 addr= netmask=
    [2014-Apr-07 15:30:22] RDP (0): --- END INTERFACE LIST ---
    [2014-Apr-07 15:30:22] RDP (0): ----- BEGIN ACTIVE CONNECTION -----
    [2014-Apr-07 15:30:22] RDP (0): client version: 8.0.24428
    [2014-Apr-07 15:30:22] RDP (0): Protocol state changed to: ProtocolConnectingNetwork(1)
    [2014-Apr-07 15:30:22] RDP (0): Resolved '192.168.16.x' to '192.168.16.x' using NameResolveMethod_DNS(1)
    [2014-Apr-07 15:30:22] RDP (0): Protocol state changed to: ProtocolNegotiatingCredentials(2)
    [2014-Apr-07 15:30:22] RDP (0): Protocol state changed to: ProtocolConnectingRDP(3)
    [2014-Apr-07 15:30:22] RDP (0): Protocol state changed to: ProtocolInactive(4)
    [2014-Apr-07 15:30:22] RDP (0): Server supports RAIL
    [2014-Apr-07 15:30:22] RDP (0): Protocol state changed to: ProtocolActive(5)
    [2014-Apr-07 15:30:23] RDP (0): Protocol state changed to: ProtocolInactive(4)
    [2014-Apr-07 15:30:23] RDP (0): Server supports RAIL
    [2014-Apr-07 15:30:23] RDP (0): Protocol state changed to: ProtocolActive(5)
    [2014-Apr-07 16:52:24] RDP (0): Protocol state changed to: ProtocolDisconnected(8)
    [2014-Apr-07 16:52:24] RDP (0): Exception caught: Exception in file '../../librdp/legacytcpstreamadapter.cpp' at line 322
    User Message : Failed to read from socket: -1
    [2014-Apr-07 16:52:24] RDP (0): ------ END ACTIVE CONNECTION ------
    [2014-Apr-07 16:52:27] RDP (0): Final rdp configuration used: screen mode id:i:2
    use multimon:i:1
    session bpp:i:24
    full address:s:192.168.16.x
    audiomode:i:0
    username:s:m
    disable wallpaper:i:0
    disable full window drag:i:0
    disable menu anims:i:0
    disable themes:i:0
    alternate shell:s:
    shell working directory:s:
    authentication level:i:2
    connect to console:i:0
    gatewayusagemethod:i:0
    disable cursor setting:i:0
    allow font smoothing:i:1
    allow desktop com:1
    bookmarktype:i:3
    use redirection server name:i:0
    [2014-Apr-07 16:52:27] RDP (0): --- BEGIN INTERFACE LIST ---
    [2014-Apr-07 16:52:27] RDP (0): lo0 af=18 addr= netmask=
    [2014-Apr-07 16:52:27] RDP (0): lo0 af=30 (AF_INET6) addr=::1 netmask=ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff
    [2014-Apr-07 16:52:27] RDP (0): lo0 af=2 (AF_INET) addr=127.0.0.1 netmask=255.0.0.0
    [2014-Apr-07 16:52:27] RDP (0): lo0 af=30 (AF_INET6) addr=fe80::1%lo0 netmask=ffff:ffff:ffff:ffff::
    [2014-Apr-07 16:52:27] RDP (0): gif0 af=18 addr= netmask=
    [2014-Apr-07 16:52:27] RDP (0): stf0 af=18 addr= netmask=
    [2014-Apr-07 16:52:27] RDP (0): en0 af=18 addr= netmask=
    [2014-Apr-07 16:52:27] RDP (0): en0 af=30 (AF_INET6) addr=fe80::12dd:b1ff:febe:9771%en0 netmask=ffff:ffff:ffff:ffff::
    [2014-Apr-07 16:52:27] RDP (0): en0 af=2 (AF_INET) addr=192.168.16.195 netmask=255.255.255.0
    [2014-Apr-07 16:52:27] RDP (0): en1 af=18 addr= netmask=
    [2014-Apr-07 16:52:27] RDP (0): en4 af=18 addr= netmask=
    [2014-Apr-07 16:52:27] RDP (0): en3 af=18 addr= netmask=
    [2014-Apr-07 16:52:27] RDP (0): p2p0 af=18 addr= netmask=
    [2014-Apr-07 16:52:27] RDP (0): bridge0 af=18 addr= netmask=
    [2014-Apr-07 16:52:27] RDP (0): --- END INTERFACE LIST ---
    [2014-Apr-07 16:52:27] RDP (0): ----- BEGIN ACTIVE CONNECTION -----
    [2014-Apr-07 16:52:27] RDP (0): client version: 8.0.24428
    [2014-Apr-07 16:52:27] RDP (0): Protocol state changed to: ProtocolConnectingNetwork(1)
    [2014-Apr-07 16:52:27] RDP (0): Resolved '192.168.16.x' to '192.168.16.x' using NameResolveMethod_DNS(1)
    [2014-Apr-07 16:52:27] RDP (0): Protocol state changed to: ProtocolNegotiatingCredentials(2)
    [2014-Apr-07 16:52:27] RDP (0): Protocol state changed to: ProtocolConnectingRDP(3)
    [2014-Apr-07 16:52:27] RDP (0): Protocol state changed to: ProtocolInactive(4)
    [2014-Apr-07 16:52:28] RDP (0): Server supports RAIL
    [2014-Apr-07 16:52:28] RDP (0): Protocol state changed to: ProtocolActive(5)
    [2014-Apr-07 16:52:28] RDP (0): Protocol state changed to: ProtocolInactive(4)
    [2014-Apr-07 16:52:28] RDP (0): Server supports RAIL
    [2014-Apr-07 16:52:28] RDP (0): Protocol state changed to: ProtocolActive(5)
    [2014-Apr-07 16:52:40] RDP (0): Protocol state changed to: ProtocolInactive(4)
    [2014-Apr-07 16:52:40] RDP (0): Disconnect initiated by server
    [2014-Apr-07 16:52:45] RDP (0): Protocol state changed to: ProtocolDisconnected(8)
    [2014-Apr-07 16:52:45] RDP (0): ------ END ACTIVE CONNECTION ------
    [2014-Apr-07 16:52:45] RDP (0): Exception caught: Exception in file '../../librdp/legacytcpstreamadapter.cpp' at line 322
    User Message : Failed to read from socket: -1
    [2014-Apr-07 16:58:19] RDP (0): *** Application terminated ***
    [2014-Apr-08 10:00:23] RDP (0): Final rdp configuration used: screen mode id:i:2
    use multimon:i:1
    session bpp:i:24
    full address:s:192.168.16.x
    audiomode:i:0
    username:s:m
    disable wallpaper:i:0
    disable full window drag:i:0
    disable menu anims:i:0
    disable themes:i:0
    alternate shell:s:
    shell working directory:s:
    authentication level:i:2
    connect to console:i:0
    gatewayusagemethod:i:0
    disable cursor setting:i:0
    allow font smoothing:i:1
    allow desktop com:1
    bookmarktype:i:3
    use redirection server name:i:0
    [2014-Apr-08 10:00:23] RDP (0): --- BEGIN INTERFACE LIST ---
    [2014-Apr-08 10:00:23] RDP (0): lo0 af=18 addr= netmask=
    [2014-Apr-08 10:00:23] RDP (0): lo0 af=30 (AF_INET6) addr=::1 netmask=ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff
    [2014-Apr-08 10:00:23] RDP (0): lo0 af=2 (AF_INET) addr=127.0.0.1 netmask=255.0.0.0
    [2014-Apr-08 10:00:23] RDP (0): lo0 af=30 (AF_INET6) addr=fe80::1%lo0 netmask=ffff:ffff:ffff:ffff::
    [2014-Apr-08 10:00:23] RDP (0): gif0 af=18 addr= netmask=
    [2014-Apr-08 10:00:23] RDP (0): stf0 af=18 addr= netmask=
    [2014-Apr-08 10:00:23] RDP (0): en0 af=18 addr= netmask=
    [2014-Apr-08 10:00:23] RDP (0): en0 af=30 (AF_INET6) addr=fe80::12dd:b1ff:febe:9771%en0 netmask=ffff:ffff:ffff:ffff::
    [2014-Apr-08 10:00:23] RDP (0): en0 af=2 (AF_INET) addr=192.168.16.1xx netmask=255.255.255.0
    [2014-Apr-08 10:00:23] RDP (0): en1 af=18 addr= netmask=
    [2014-Apr-08 10:00:23] RDP (0): en4 af=18 addr= netmask=
    [2014-Apr-08 10:00:23] RDP (0): en3 af=18 addr= netmask=
    [2014-Apr-08 10:00:23] RDP (0): p2p0 af=18 addr= netmask=
    [2014-Apr-08 10:00:23] RDP (0): bridge0 af=18 addr= netmask=
    [2014-Apr-08 10:00:23] RDP (0): --- END INTERFACE LIST ---
    [2014-Apr-08 10:00:23] RDP (0): ----- BEGIN ACTIVE CONNECTION -----
    [2014-Apr-08 10:00:23] RDP (0): client version: 8.0.24428
    [2014-Apr-08 10:00:23] RDP (0): Protocol state changed to: ProtocolConnectingNetwork(1)
    [2014-Apr-08 10:00:23] RDP (0): Resolved '192.168.16.25' to '192.168.16.25' using NameResolveMethod_DNS(1)
    [2014-Apr-08 10:00:23] RDP (0): Protocol state changed to: ProtocolNegotiatingCredentials(2)
    [2014-Apr-08 10:00:23] RDP (0): Protocol state changed to: ProtocolConnectingRDP(3)
    [2014-Apr-08 10:00:23] RDP (0): Protocol state changed to: ProtocolInactive(4)
    [2014-Apr-08 10:00:23] RDP (0): Server supports RAIL
    [2014-Apr-08 10:00:23] RDP (0): Protocol state changed to: ProtocolActive(5)
    [2014-Apr-08 10:00:38] RDP (0): Server hides cursor
    [2014-Apr-08 10:00:40] RDP (0): Server shows cursor
    [2014-Apr-08 10:08:35] RDP (0): Protocol state changed to: ProtocolDisconnected(8)
    [2014-Apr-08 10:08:35] RDP (0): ------ END ACTIVE CONNECTION ------
    [2014-Apr-08 10:08:35] RDP (0): Exception caught: Exception in file '../../librdp/legacytcpstreamadapter.cpp' at line 322
    User Message : Failed to read from socket: -1
    [2014-Apr-08 10:08:39] RDP (0): Final rdp configuration used: screen mode id:i:2
    use multimon:i:1
    session bpp:i:24
    full address:s:192.168.16.x
    audiomode:i:0
    username:s:m
    disable wallpaper:i:0
    disable full window drag:i:0
    disable menu anims:i:0
    disable themes:i:0
    alternate shell:s:
    shell working directory:s:
    authentication level:i:2
    connect to console:i:0
    gatewayusagemethod:i:0
    disable cursor setting:i:0
    allow font smoothing:i:1
    allow desktop com:1
    bookmarktype:i:3
    use redirection server name:i:0
    [2014-Apr-08 10:08:39] RDP (0): --- BEGIN INTERFACE LIST ---
    [2014-Apr-08 10:08:39] RDP (0): lo0 af=18 addr= netmask=
    [2014-Apr-08 10:08:39] RDP (0): lo0 af=30 (AF_INET6) addr=::1 netmask=ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff
    [2014-Apr-08 10:08:39] RDP (0): lo0 af=2 (AF_INET) addr=127.0.0.1 netmask=255.0.0.0
    [2014-Apr-08 10:08:39] RDP (0): lo0 af=30 (AF_INET6) addr=fe80::1%lo0 netmask=ffff:ffff:ffff:ffff::
    [2014-Apr-08 10:08:39] RDP (0): gif0 af=18 addr= netmask=
    [2014-Apr-08 10:08:39] RDP (0): stf0 af=18 addr= netmask=
    [2014-Apr-08 10:08:39] RDP (0): en0 af=18 addr= netmask=
    [2014-Apr-08 10:08:39] RDP (0): en0 af=30 (AF_INET6) addr=fe80::12dd:b1ff:febe:9771%en0 netmask=ffff:ffff:ffff:ffff::
    [2014-Apr-08 10:08:39] RDP (0): en0 af=2 (AF_INET) addr=192.168.16.195 netmask=255.255.255.0
    [2014-Apr-08 10:08:39] RDP (0): en1 af=18 addr= netmask=
    [2014-Apr-08 10:08:39] RDP (0): en4 af=18 addr= netmask=
    [2014-Apr-08 10:08:39] RDP (0): en3 af=18 addr= netmask=
    [2014-Apr-08 10:08:39] RDP (0): p2p0 af=18 addr= netmask=
    [2014-Apr-08 10:08:39] RDP (0): bridge0 af=18 addr= netmask=
    [2014-Apr-08 10:08:39] RDP (0): --- END INTERFACE LIST ---
    [2014-Apr-08 10:08:39] RDP (0): ----- BEGIN ACTIVE CONNECTION -----
    [2014-Apr-08 10:08:39] RDP (0): client version: 8.0.24428
    [2014-Apr-08 10:08:39] RDP (0): Protocol state changed to: ProtocolConnectingNetwork(1)
    [2014-Apr-08 10:08:39] RDP (0): Resolved '192.168.16.25' to '192.168.16.25' using NameResolveMethod_DNS(1)
    [2014-Apr-08 10:08:39] RDP (0): Protocol state changed to: ProtocolNegotiatingCredentials(2)
    [2014-Apr-08 10:08:39] RDP (0): Protocol state changed to: ProtocolConnectingRDP(3)
    [2014-Apr-08 10:08:39] RDP (0): Protocol state changed to: ProtocolInactive(4)
    [2014-Apr-08 10:08:39] RDP (0): Server supports RAIL
    [2014-Apr-08 10:08:39] RDP (0): Protocol state changed to: ProtocolActive(5)
    [2014-Apr-08 10:08:40] RDP (0): Protocol state changed to: ProtocolInactive(4)
    [2014-Apr-08 10:08:40] RDP (0): Server supports RAIL
    [2014-Apr-08 10:08:40] RDP (0): Protocol state changed to: ProtocolActive(5)
    [2014-Apr-08 11:02:36] RDP (0): Protocol state changed to: ProtocolDisconnected(8)
    [2014-Apr-08 11:02:36] RDP (0): Exception caught: Exception in file '../../librdp/legacytcpstreamadapter.cpp' at line 322
    User Message : Failed to read from socket: -1
    [2014-Apr-08 11:02:36] RDP (0): ------ END ACTIVE CONNECTION ------
    [2014-Apr-08 11:04:38] RDP (0): Final rdp configuration used: screen mode id:i:2
    use multimon:i:1
    session bpp:i:24
    full address:s:192.168.16.25
    audiomode:i:0
    username:s:michele.lefebvre
    disable wallpaper:i:0
    disable full window drag:i:0
    disable menu anims:i:0
    disable themes:i:0
    alternate shell:s:
    shell working directory:s:
    authentication level:i:2
    connect to console:i:0
    gatewayusagemethod:i:0
    disable cursor setting:i:0
    allow font smoothing:i:1
    allow desktop com:1
    bookmarktype:i:3
    use redirection server name:i:0
    [2014-Apr-08 11:04:38] RDP (0): --- BEGIN INTERFACE LIST ---
    [2014-Apr-08 11:04:38] RDP (0): lo0 af=18 addr= netmask=
    [2014-Apr-08 11:04:38] RDP (0): lo0 af=30 (AF_INET6) addr=::1 netmask=ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff
    [2014-Apr-08 11:04:38] RDP (0): lo0 af=2 (AF_INET) addr=127.0.0.1 netmask=255.0.0.0
    [2014-Apr-08 11:04:38] RDP (0): lo0 af=30 (AF_INET6) addr=fe80::1%lo0 netmask=ffff:ffff:ffff:ffff::
    [2014-Apr-08 11:04:38] RDP (0): gif0 af=18 addr= netmask=
    [2014-Apr-08 11:04:38] RDP (0): stf0 af=18 addr= netmask=
    [2014-Apr-08 11:04:38] RDP (0): en0 af=18 addr= netmask=
    [2014-Apr-08 11:04:38] RDP (0): en0 af=30 (AF_INET6) addr=fe80::12dd:b1ff:febe:9771%en0 netmask=ffff:ffff:ffff:ffff::
    [2014-Apr-08 11:04:38] RDP (0): en0 af=2 (AF_INET) addr=192.168.16.1xx netmask=255.255.255.0
    [2014-Apr-08 11:04:38] RDP (0): en1 af=18 addr= netmask=
    [2014-Apr-08 11:04:38] RDP (0): en4 af=18 addr= netmask=
    [2014-Apr-08 11:04:38] RDP (0): en3 af=18 addr= netmask=
    [2014-Apr-08 11:04:38] RDP (0): p2p0 af=18 addr= netmask=
    [2014-Apr-08 11:04:38] RDP (0): bridge0 af=18 addr= netmask=
    [2014-Apr-08 11:04:38] RDP (0): --- END INTERFACE LIST ---
    [2014-Apr-08 11:04:38] RDP (0): ----- BEGIN ACTIVE CONNECTION -----
    [2014-Apr-08 11:04:38] RDP (0): client version: 8.0.24428
    [2014-Apr-08 11:04:38] RDP (0): Protocol state changed to: ProtocolConnectingNetwork(1)
    [2014-Apr-08 11:04:38] RDP (0): Resolved '192.168.16.25' to '192.168.16.25' using NameResolveMethod_DNS(1)
    [2014-Apr-08 11:04:38] RDP (0): Protocol state changed to: ProtocolNegotiatingCredentials(2)
    [2014-Apr-08 11:04:38] RDP (0): Protocol state changed to: ProtocolConnectingRDP(3)
    [2014-Apr-08 11:04:38] RDP (0): Protocol state changed to: ProtocolInactive(4)
    [2014-Apr-08 11:04:38] RDP (0): Server supports RAIL
    [2014-Apr-08 11:04:39] RDP (0): Protocol state changed to: ProtocolActive(5)
    [2014-Apr-08 11:04:39] RDP (0): Protocol state changed to: ProtocolInactive(4)
    [2014-Apr-08 11:04:39] RDP (0): Server supports RAIL
    [2014-Apr-08 11:04:39] RDP (0): Protocol state changed to: ProtocolActive(5)
    [2014-Apr-08 11:04:49] RDP (0): Server hides cursor
    [2014-Apr-08 11:04:50] RDP (0): Server shows cursor
    [2014-Apr-08 11:04:51] RDP (0): Server hides cursor
    [2014-Apr-08 11:04:55] RDP (0): Server shows cursor
    [2014-Apr-08 11:05:09] RDP (0): Server hides cursor
    [2014-Apr-08 11:05:12] RDP (0): Server shows cursor
    [2014-Apr-08 11:06:33] RDP (0): Server hides cursor
    [2014-Apr-08 11:06:33] RDP (0): Server shows cursor
    [2014-Apr-08 11:06:35] RDP (0): Server hides cursor
    [2014-Apr-08 11:06:44] RDP (0): Server shows cursor
    [2014-Apr-08 11:06:49] RDP (0): Server hides cursor
    [2014-Apr-08 11:06:50] RDP (0): Server shows cursor
    [2014-Apr-08 11:06:54] RDP (0): Server hides cursor
    [2014-Apr-08 11:07:02] RDP (0): Server shows cursor
    [2014-Apr-08 11:07:06] RDP (0): Server hides cursor
    [2014-Apr-08 11:07:14] RDP (0): Server shows cursor
    [2014-Apr-08 11:07:26] RDP (0): Server hides cursor
    [2014-Apr-08 11:07:29] RDP (0): Server shows cursor
    [2014-Apr-08 11:07:32] RDP (0): Server hides cursor
    [2014-Apr-08 11:07:33] RDP (0): Server shows cursor
    [2014-Apr-08 11:07:35] RDP (0): Server hides cursor
    [2014-Apr-08 11:07:35] RDP (0): Server shows cursor
    [2014-Apr-08 11:07:35] RDP (0): Server hides cursor
    [2014-Apr-08 11:07:35] RDP (0): Server shows cursor
    [2014-Apr-08 11:07:35] RDP (0): Server hides cursor
    [2014-Apr-08 11:07:35] RDP (0): Server shows cursor
    [2014-Apr-08 11:07:36] RDP (0): Server hides cursor
    [2014-Apr-08 11:07:36] RDP (0): Server shows cursor
    [2014-Apr-08 11:07:36] RDP (0): Server hides cursor
    [2014-Apr-08 11:07:36] RDP (0): Server shows cursor
    [2014-Apr-08 11:07:36] RDP (0): Server hides cursor
    [2014-Apr-08 11:07:36] RDP (0): Server shows cursor
    [2014-Apr-08 11:07:38] RDP (0): Server hides cursor
    [2014-Apr-08 11:07:38] RDP (0): Server shows cursor
    [2014-Apr-08 11:17:05] RDP (0): Server hides cursor
    [2014-Apr-08 11:17:08] RDP (0): Server shows cursor
    [2014-Apr-08 11:26:53] RDP (0): Server hides cursor
    [2014-Apr-08 11:26:54] RDP (0): Server shows cursor
    [2014-Apr-08 11:26:54] RDP (0): Server hides cursor
    [2014-Apr-08 11:26:54] RDP (0): Server shows cursor
    [2014-Apr-08 11:26:54] RDP (0): Server hides cursor
    [2014-Apr-08 11:26:54] RDP (0): Server shows cursor
    [2014-Apr-08 11:26:54] RDP (0): Server hides cursor
    [2014-Apr-08 11:26:54] RDP (0): Server shows cursor
    [2014-Apr-08 11:26:54] RDP (0): Server hides cursor
    [2014-Apr-08 11:26:54] RDP (0): Server shows cursor
    [2014-Apr-08 11:26:58] RDP (0): Server hides cursor
    [2014-Apr-08 11:26:58] RDP (0): Server shows cursor
    [2014-Apr-08 11:26:58] RDP (0): Server hides cursor
    [2014-Apr-08 11:26:58] RDP (0): Server shows cursor
    [2014-Apr-08 11:27:05] RDP (0): Server hides cursor
    [2014-Apr-08 11:27:06] RDP (0): Server shows cursor
    [2014-Apr-08 11:27:15] RDP (0): Server hides cursor
    [2014-Apr-08 11:27:15] RDP (0): Server shows cursor
    [2014-Apr-08 11:27:15] RDP (0): Server hides cursor
    [2014-Apr-08 11:27:15] RDP (0): Server shows cursor
    [2014-Apr-08 11:27:17] RDP (0): Server hides cursor
    [2014-Apr-08 11:27:17] RDP (0): Server shows cursor
    [2014-Apr-08 11:27:22] RDP (0): Server hides cursor
    [2014-Apr-08 11:27:22] RDP (0): Server shows cursor
    [2014-Apr-08 11:27:23] RDP (0): Server hides cursor
    [2014-Apr-08 11:27:25] RDP (0): Server shows cursor
    [2014-Apr-08 11:27:25] RDP (0): Server hides cursor
    [2014-Apr-08 11:27:25] RDP (0): Server shows cursor
    [2014-Apr-08 11:27:25] RDP (0): Server hides cursor
    [2014-Apr-08 11:27:26] RDP (0): Server shows cursor
    [2014-Apr-08 11:27:29] RDP (0): Server hides cursor
    [2014-Apr-08 11:27:29] RDP (0): Server shows cursor
    [2014-Apr-08 11:27:29] RDP (0): Server hides cursor
    [2014-Apr-08 11:27:29] RDP (0): Server shows cursor
    [2014-Apr-08 11:27:29] RDP (0): Server hides cursor
    [2014-Apr-08 11:27:29] RDP (0): Server shows cursor
    [2014-Apr-08 11:27:31] RDP (0): Server hides cursor
    [2014-Apr-08 11:27:31] RDP (0): Server shows cursor
    [2014-Apr-08 11:27:32] RDP (0): Server hides cursor
    [2014-Apr-08 11:27:33] RDP (0): Server shows cursor
    [2014-Apr-08 11:27:35] RDP (0): Server hides cursor
    [2014-Apr-08 11:27:36] RDP (0): Server shows cursor
    [2014-Apr-08 11:29:50] RDP (0): Protocol state changed to: ProtocolDisconnected(8)
    [2014-Apr-08 11:29:50] RDP (0): ------ END ACTIVE CONNECTION ------
    [2014-Apr-08 11:29:50] RDP (0): Exception caught: Exception in file '../../librdp/legacytcpstreamadapter.cpp' at line 322
    User Message : Failed to read from socket: -1
    [2014-Apr-08 11:30:04] RDP (0): Final rdp configuration used: screen mode id:i:2
    use multimon:i:1
    session bpp:i:24
    full address:s:192.168.16.x
    audiomode:i:0
    username:s:m
    disable wallpaper:i:0
    disable full window drag:i:0
    disable menu anims:i:0
    disable themes:i:0
    alternate shell:s:
    shell working directory:s:
    authentication level:i:2
    connect to console:i:0
    gatewayusagemethod:i:0
    disable cursor setting:i:0
    allow font smoothing:i:1
    allow desktop com:1
    bookmarktype:i:3
    use redirection server name:i:0
    [2014-Apr-08 11:30:04] RDP (0): --- BEGIN INTERFACE LIST ---
    [2014-Apr-08 11:30:04] RDP (0): lo0 af=18 addr= netmask=
    [2014-Apr-08 11:30:04] RDP (0): lo0 af=30 (AF_INET6) addr=::1 netmask=ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff
    [2014-Apr-08 11:30:04] RDP (0): lo0 af=2 (AF_INET) addr=127.0.0.1 netmask=255.0.0.0
    [2014-Apr-08 11:30:04] RDP (0): lo0 af=30 (AF_INET6) addr=fe80::1%lo0 netmask=ffff:ffff:ffff:ffff::
    [2014-Apr-08 11:30:04] RDP (0): gif0 af=18 addr= netmask=
    [2014-Apr-08 11:30:04] RDP (0): stf0 af=18 addr= netmask=
    [2014-Apr-08 11:30:04] RDP (0): en0 af=18 addr= netmask=
    [2014-Apr-08 11:30:04] RDP (0): en0 af=30 (AF_INET6) addr=fe80::12dd:b1ff:febe:9771%en0 netmask=ffff:ffff:ffff:ffff::
    [2014-Apr-08 11:30:04] RDP (0): en0 af=2 (AF_INET) addr=192.168.16.1xx netmask=255.255.255.0
    [2014-Apr-08 11:30:04] RDP (0): en1 af=18 addr= netmask=
    [2014-Apr-08 11:30:04] RDP (0): en4 af=18 addr= netmask=
    [2014-Apr-08 11:30:04] RDP (0): en3 af=18 addr= netmask=
    [2014-Apr-08 11:30:04] RDP (0): p2p0 af=18 addr= netmask=
    [2014-Apr-08 11:30:04] RDP (0): bridge0 af=18 addr= netmask=
    [2014-Apr-08 11:30:04] RDP (0): --- END INTERFACE LIST ---
    [2014-Apr-08 11:30:04] RDP (0): ----- BEGIN ACTIVE CONNECTION -----
    [2014-Apr-08 11:30:04] RDP (0): client version: 8.0.24428
    [2014-Apr-08 11:30:04] RDP (0): Protocol state changed to: ProtocolConnectingNetwork(1)
    [2014-Apr-08 11:30:04] RDP (0): Resolved '192.168.16.25' to '192.168.16.25' using NameResolveMethod_DNS(1)
    [2014-Apr-08 11:30:04] RDP (0): Protocol state changed to: ProtocolNegotiatingCredentials(2)
    [2014-Apr-08 11:30:04] RDP (0): Protocol state changed to: ProtocolConnectingRDP(3)
    [2014-Apr-08 11:30:04] RDP (0): Protocol state changed to: ProtocolInactive(4)
    [2014-Apr-08 11:30:04] RDP (0): Server supports RAIL
    [2014-Apr-08 11:30:04] RDP (0): Protocol state changed to: ProtocolActive(5)
    [2014-Apr-08 11:30:05] RDP (0): Protocol state changed to: ProtocolInactive(4)
    [2014-Apr-08 11:30:05] RDP (0): Server supports RAIL
    [2014-Apr-08 11:30:05] RDP (0): Protocol state changed to: ProtocolActive(5)
    [2014-Apr-08 11:30:11] RDP (0): Server hides cursor
    [2014-Apr-08 11:30:11] RDP (0): Server shows cursor
    [2014-Apr-08 11:30:11] RDP (0): Server hides cursor
    [2014-Apr-08 11:30:11] RDP (0): Server shows cursor
    [2014-Apr-08 11:30:12] RDP (0): Server hides cursor
    [2014-Apr-08 11:30:12] RDP (0): Server shows cursor
    [2014-Apr-08 11:30:12] RDP (0): Server hides cursor
    [2014-Apr-08 11:30:12] RDP (0): Server shows cursor
    [2014-Apr-08 11:30:12] RDP (0): Server hides cursor
    [2014-Apr-08 11:30:12] RDP (0): Server shows cursor
    [2014-Apr-08 11:30:30] RDP (0): Server hides cursor
    [2014-Apr-08 11:30:31] RDP (0): Server shows cursor
    [2014-Apr-08 11:30:31] RDP (0): Server hides cursor
    [2014-Apr-08 11:30:31] RDP (0): Server shows cursor
    [2014-Apr-08 14:45:21] RDP (0): Protocol state changed to: ProtocolDisconnected(8)
    [2014-Apr-08 14:45:21] RDP (0): Exception caught: Exception in file '../../librdp/legacytcpstreamadapter.cpp' at line 322
    User Message : Failed to read from socket: -1
    [2014-Apr-08 14:45:21] RDP (0): ------ END ACTIVE CONNECTION ------
    [2014-Apr-08 15:11:03] RDP (0): Final rdp configuration used: screen mode id:i:2
    use multimon:i:1
    session bpp:i:24
    full address:s:192.168.16.x
    audiomode:i:0
    username:s:m
    disable wallpaper:i:0
    disable full window drag:i:0
    disable menu anims:i:0
    disable themes:i:0
    alternate shell:s:
    shell working directory:s:
    authentication level:i:2
    connect to console:i:0
    gatewayusagemethod:i:0
    disable cursor setting:i:0
    allow font smoothing:i:1
    allow desktop com:1
    bookmarktype:i:3
    use redirection server name:i:0
    [2014-Apr-08 15:11:03] RDP (0): --- BEGIN INTERFACE LIST ---
    [2014-Apr-08 15:11:03] RDP (0): lo0 af=18 addr= netmask=
    [2014-Apr-08 15:11:03] RDP (0): lo0 af=30 (AF_INET6) addr=::1 netmask=ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff
    [2014-Apr-08 15:11:03] RDP (0): lo0 af=2 (AF_INET) addr=127.0.0.1 netmask=255.0.0.0
    [2014-Apr-08 15:11:03] RDP (0): lo0 af=30 (AF_INET6) addr=fe80::1%lo0 netmask=ffff:ffff:ffff:ffff::
    [2014-Apr-08 15:11:03] RDP (0): gif0 af=18 addr= netmask=
    [2014-Apr-08 15:11:03] RDP (0): stf0 af=18 addr= netmask=
    [2014-Apr-08 15:11:03] RDP (0): en0 af=18 addr= netmask=
    [2014-Apr-08 15:11:03] RDP (0): en0 af=30 (AF_INET6) addr=fe80::12dd:b1ff:febe:9771%en0 netmask=ffff:ffff:ffff:ffff::
    [2014-Apr-08 15:11:03] RDP (0): en0 af=2 (AF_INET) addr=192.168.16.1xx netmask=255.255.255.0
    [2014-Apr-08 15:11:03] RDP (0): en1 af=18 addr= netmask=
    [2014-Apr-08 15:11:03] RDP (0): en4 af=18 addr= netmask=
    [2014-Apr-08 15:11:03] RDP (0): en3 af=18 addr= netmask=
    [2014-Apr-08 15:11:03] RDP (0): p2p0 af=18 addr= netmask=
    [2014-Apr-08 15:11:03] RDP (0): bridge0 af=18 addr= netmask=
    [2014-Apr-08 15:11:03] RDP (0): --- END INTERFACE LIST ---
    [2014-Apr-08 15:11:03] RDP (0): ----- BEGIN ACTIVE CONNECTION -----
    [2014-Apr-08 15:11:03] RDP (0): client version: 8.0.24428
    [2014-Apr-08 15:11:03] RDP (0): Protocol state changed to: ProtocolConnectingNetwork(1)
    [2014-Apr-08 15:11:03] RDP (0): Resolved '192.168.16.x' to '192.168.16.x' using NameResolveMethod_DNS(1)
    [2014-Apr-08 15:11:03] RDP (0): Protocol state changed to: ProtocolNegotiatingCredentials(2)
    [2014-Apr-08 15:11:03] RDP (0): Protocol state changed to: ProtocolConnectingRDP(3)
    [2014-Apr-08 15:11:03] RDP (0): Protocol state changed to: ProtocolInactive(4)
    [2014-Apr-08 15:11:03] RDP (0): Server supports RAIL
    [2014-Apr-08 15:11:03] RDP (0): Protocol state changed to: ProtocolActive(5)
    [2014-Apr-08 15:11:04] RDP (0): Protocol state changed to: ProtocolInactive(4)
    [2014-Apr-08 15:11:04] RDP (0): Server supports RAIL
    [2014-Apr-08 15:11:04] RDP (0): Protocol state changed to: ProtocolActive(5)
    [2014-Apr-08 15:22:36] RDP (0): Protocol state changed to: ProtocolInactive(4)
    [2014-Apr-08 15:22:36] RDP (0): Disconnect initiated by server
    [2014-Apr-08 15:22:41] RDP (0): Protocol state changed to: ProtocolDisconnected(8)
    [2014-Apr-08 15:22:41] RDP (0): ------ END ACTIVE CONNECTION ------
    [2014-Apr-08 15:22:41] RDP (0): Exception caught: Exception in file '../../librdp/legacytcpstreamadapter.cpp' at line 322
    User Message : Failed to read from socket: -1
    [2014-Apr-08 16:29:11] RDP (0): Final rdp configuration used: screen mode id:i:2
    use multimon:i:1
    session bpp:i:24
    full address:s:192.168.16.x
    audiomode:i:0
    username:s:michele.lefebvre
    disable wallpaper:i:0
    disable full window drag:i:0
    disable menu anims:i:0
    disable themes:i:0
    alternate shell:s:
    shell working directory:s:
    authentication level:i:2
    connect to console:i:0
    gatewayusagemethod:i:0
    disable cursor setting:i:0
    allow font smoothing:i:1
    allow desktop com:1
    bookmarktype:i:3
    use redirection server name:i:0
    [2014-Apr-08 16:29:11] RDP (0): --- BEGIN INTERFACE LIST ---
    [2014-Apr-08 16:29:11] RDP (0): lo0 af=18 addr= netmask=
    [2014-Apr-08 16:29:11] RDP (0): lo0 af=30 (AF_INET6) addr=::1 netmask=ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff
    [2014-Apr-08 16:29:11] RDP (0): lo0 af=2 (AF_INET) addr=127.0.0.1 netmask=255.0.0.0
    [2014-Apr-08 16:29:11] RDP (0): lo0 af=30 (AF_INET6) addr=fe80::1%lo0 netmask=ffff:ffff:ffff:ffff::
    [2014-Apr-08 16:29:11] RDP (0): gif0 af=18 addr= netmask=
    [2014-Apr-08 16:29:11] RDP (0): stf0 af=18 addr= netmask=
    [2014-Apr-08 16:29:11] RDP (0): en0 af=18 addr= netmask=
    [2014-Apr-08 16:29:11] RDP (0): en0 af=30 (AF_INET6) addr=fe80::12dd:b1ff:febe:9771%en0 netmask=ffff:ffff:ffff:ffff::
    [2014-Apr-08 16:29:11] RDP (0): en0 af=2 (AF_INET) addr=192.168.16.195 netmask=255.255.255.0
    [2014-Apr-08 16:29:11] RDP (0): en1 af=18 addr= netmask=
    [2014-Apr-08 16:29:11] RDP (0): en4 af=18 addr= netmask=
    [2014-Apr-08 16:29:11] RDP (0): en3 af=18 addr= netmask=
    [2014-Apr-08 16:29:11] RDP (0): p2p0 af=18 addr= netmask=
    [2014-Apr-08 16:29:11] RDP (0): bridge0 af=18 addr= netmask=
    [2014-Apr-08 16:29:11] RDP (0): --- END INTERFACE LIST ---
    [2014-Apr-08 16:29:11] RDP (0): ----- BEGIN ACTIVE CONNECTION -----
    [2014-Apr-08 16:29:11] RDP (0): client version: 8.0.24428
    [2014-Apr-08 16:29:11] RDP (0): Protocol state changed to: ProtocolConnectingNetwork(1)
    [2014-Apr-08 16:29:11] RDP (0): Resolved '192.168.16.25' to '192.168.16.25' using NameResolveMethod_DNS(1)
    [2014-Apr-08 16:29:11] RDP (0): Protocol state changed to: ProtocolNegotiatingCredentials(2)
    [2014-Apr-08 16:29:11] RDP (0): Protocol state changed to: ProtocolConnectingRDP(3)
    [2014-Apr-08 16:29:11] RDP (0): Protocol state changed to: ProtocolInactive(4)
    [2014-Apr-08 16:29:12] RDP (0): Server supports RAIL
    [2014-Apr-08 16:29:12] RDP (0): Protocol state changed to: ProtocolActive(5)
    [2014-Apr-08 16:29:51] RDP (0): Protocol state changed to: ProtocolInactive(4)
    [2014-Apr-08 16:29:51] RDP (0): Disconnect initiated by server
    [2014-Apr-08 16:29:56] RDP (0): Protocol state changed to: ProtocolDisconnected(8)
    [2014-Apr-08 16:29:56] RDP (0): ------ END ACTIVE CONNECTION ------
    [2014-Apr-08 16:29:56] RDP (0): Exception caught: Exception in file '../../librdp/legacytcpstreamadapter.cpp' at line 322
    User Message : Failed to read from socket: -1
    [2014-Apr-08 16:37:07] RDP (0): *** Application terminated ***
    [2014-Apr-09 09:24:29] RDP (0): Final rdp configuration used: screen mode id:i:2
    use multimon:i:1
    session bpp:i:24
    full address:s:192.168.16.x
    audiomode:i:0
    username:s:m
    disable wallpaper:i:0
    disable full window drag:i:0
    disable menu anims:i:0
    disable themes:i:0
    alternate shell:s:
    shell working directory:s:
    authentication level:i:2
    connect to console:i:0
    gatewayusagemethod:i:0
    disable cursor setting:i:0
    allow font smoothing:i:1
    allow desktop com:1
    bookmarktype:i:3
    use redirection server name:i:0
    [2014-Apr-09 09:24:29] RDP (0): --- BEGIN INTERFACE LIST ---
    [2014-Apr-09 09:24:29] RDP (0): lo0 af=18 addr= netmask=
    [2014-Apr-09 09:24:29] RDP (0): lo0 af=30 (AF_INET6) addr=::1 netmask=ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff
    [2014-Apr-09 09:24:29] RDP (0): lo0 af=2 (AF_INET) addr=127.0.0.1 netmask=255.0.0.0
    [2014-Apr-09 09:24:29] RDP (0): lo0 af=30 (AF_INET6) addr=fe80::1%lo0 netmask=ffff:ffff:ffff:ffff::
    [2014-Apr-09 09:24:29] RDP (0): gif0 af=18 addr= netmask=
    [2014-Apr-09 09:24:29] RDP (0): stf0 af=18 addr= netmask=
    [2014-Apr-09 09:24:29] RDP (0): en0 af=18 addr= netmask=
    [2014-Apr-09 09:24:29] RDP (0): en0 af=30 (AF_INET6) addr=fe80::12dd:b1ff:febe:9771%en0 netmask=ffff:ffff:ffff:ffff::
    [2014-Apr-09 09:24:29] RDP (0): en0 af=2 (AF_INET) addr=192.168.16.195 netmask=255.255.255.0
    [2014-Apr-09 09:24:29] RDP (0): en1 af=18 addr= netmask=
    [2014-Apr-09 09:24:29] RDP (0): en4 af=18 addr= netmask=
    [2014-Apr-09 09:24:29] RDP (0): en3 af=18 addr= netmask=
    [2014-Apr-09 09:24:29] RDP (0): p2p0 af=18 addr= netmask=
    [2014-Apr-09 09:24:29] RDP (0): bridge0 af=18 addr= netmask=
    [2014-Apr-09 09:24:29] RDP (0): --- END INTERFACE LIST ---
    [2014-Apr-09 09:24:29] RDP (0): ----- BEGIN ACTIVE CONNECTION -----
    [2014-Apr-09 09:24:29] RDP (0): client version: 8.0.24428
    [2014-Apr-09 09:24:29] RDP (0): Protocol state changed to: ProtocolConnectingNetwork(1)
    [2014-Apr-09 09:24:29] RDP (0): Resolved '192.168.16.x' to '192.168.16.x' using NameResolveMethod_DNS(1)
    [2014-Apr-09 09:24:29] RDP (0): Protocol state changed to: ProtocolNegotiatingCredentials(2)
    [2014-Apr-09 09:24:29] RDP (0): Protocol state changed to: ProtocolConnectingRDP(3)
    [2014-Apr-09 09:24:29] RDP (0): Protocol state changed to: ProtocolInactive(4)
    [2014-Apr-09 09:24:29] RDP (0): Server supports RAIL
    [2014-Apr-09 09:24:29] RDP (0): Protocol state changed to: ProtocolActive(5)
    [2014-Apr-09 09:24:45] RDP (0): Server hides cursor
    [2014-Apr-09 09:24:46] RDP (0): Server shows cursor
    [2014-Apr-09 09:24:46] RDP (0): Server hides cursor
    [2014-Apr-09 09:24:49] RDP (0): Server shows cursor
    [2014-Apr-09 09:25:08] RDP (0): Server hides cursor
    [2014-Apr-09 09:25:10] RDP (0): Server shows cursor
    [2014-Apr-09 09:25:15] RDP (0): Server hides cursor
    [2014-Apr-09 09:25:27] RDP (0): Server shows cursor
    [2014-Apr-09 09:25:30] RDP (0): Server hides cursor
    [2014-Apr-09 09:25:31] RDP (0): Server shows cursor
    [2014-Apr-09 09:25:33] RDP (0): Server hides cursor
    [2014-Apr-09 09:25:34] RDP (0): Server shows cursor
    [2014-Apr-09 09:25:38] RDP (0): Server hides cursor
    [2014-Apr-09 09:25:48] RDP (0): Server shows cursor
    [2014-Apr-09 09:25:50] RDP (0): Server hides cursor
    [2014-Apr-09 09:26:40] RDP (0): Server shows cursor
    [2014-Apr-09 09:26:40] RDP (0): Server hides cursor
    [2014-Apr-09 09:26:40] RDP (0): Server shows cursor
    [2014-Apr-09 09:26:40] RDP (0): Server hides cursor
    [2014-Apr-09 09:26:40] RDP (0): Server shows cursor
    [2014-Apr-09 09:26:40] RDP (0): Server hides cursor
    [2014-Apr-09 09:26:41] RDP (0): Server shows cursor
    [2014-Apr-09 09:26:41] RDP (0): Server hides cursor
    [2014-Apr-09 09:26:41] RDP (0): Server shows cursor
    [2014-Apr-09 09:26:41] RDP (0): Server hides cursor
    [2014-Apr-09 09:26:41] RDP (0): Server shows cursor
    [2014-Apr-09 09:26:53] RDP (0): Server hides cursor
    [2014-Apr-09 09:26:53] RDP (0): Server shows cursor
    [2014-Apr-09 09:26:53] RDP (0): Server hides cursor
    [2014-Apr-09 09:26:53] RDP (0): Server shows cursor
    [2014-Apr-09 09:26:58] RDP (0): Server hides cursor
    [2014-Apr-09 09:26:58] RDP (0): Server shows cursor
    [2014-Apr-09 09:27:20] RDP (0): Server hides cursor
    [2014-Apr-09 09:27:22] RDP (0): Server shows cursor
    [2014-Apr-09 09:27:23] RDP (0): Server hides cursor
    [2014-Apr-09 09:27:23] RDP (0): Server shows cursor
    [2014-Apr-09 10:10:53] RDP (0): Protocol state changed to: ProtocolDisconnected(8)
    [2014-Apr-09 10:10:53] RDP (0): ------ END ACTIVE CONNECTION ------
    [2014-Apr-09 10:10:53] RDP (0): Exception caught: Exception in file '../../librdp/legacytcpstreamadapter.cpp' at line 322
    User Message : Failed to read from socket: -1
    [2014-Apr-09 10:10:56] RDP (0): Final rdp configuration used: screen mode id:i:2
    use multimon:i:1
    session bpp:i:24
    full address:s:192.168.16.x
    audiomode:i:0
    username:s:m
    disable wallpaper:i:0
    disable full window drag:i:0
    disable menu anims:i:0
    disable themes:i:0
    alternate shell:s:
    shell working directory:s:
    authentication level:i:2
    connect to console:i:0
    gatewayusagemethod:i:0
    disable cursor setting:i:0
    allow font smoothing:i:1
    allow desktop com:1
    bookmarktype:i:3
    use redirection server name:i:0
    [2014-Apr-09 10:10:56] RDP (0): --- BEGIN INTERFACE LIST ---
    [2014-Apr-09 10:10:56] RDP (0): lo0 af=18 addr= netmask=
    [2014-Apr-09 10:10:56] RDP (0): lo0 af=30 (AF_INET6) addr=::1 netmask=ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff
    [2014-Apr-09 10:10:56] RDP (0): lo0 af=2 (AF_INET) addr=127.0.0.1 netmask=255.0.0.0
    [2014-Apr-09 10:10:56] RDP (0): lo0 af=30 (AF_INET6) addr=fe80::1%lo0 netmask=ffff:ffff:ffff:ffff::
    [2014-Apr-09 10:10:56] RDP (0): gif0 af=18 addr= netmask=
    [2014-Apr-09 10:10:56] RDP (0): stf0 af=18 addr= netmask=
    [2014-Apr-09 10:10:56] RDP (0): en0 af=18 addr= netmask=
    [2014-Apr-09 10:10:56] RDP (0): en0 af=30 (AF_INET6) addr=fe80::12dd:b1ff:febe:9771%en0 netmask=ffff:ffff:ffff:ffff::
    [2014-Apr-09 10:10:56] RDP (0): en0 af=2 (AF_INET) addr=192.168.16.1xx netmask=255.255.255.0
    [2014-Apr-09 10:10:56] RDP (0): en1 af=18 addr= netmask=
    [2014-Apr-09 10:10:56] RDP (0): en4 af=18 addr= netmask=
    [2014-Apr-09 10:10:56] RDP (0): en3 af=18 addr= netmask=
    [2014-Apr-09 10:10:56] RDP (0): p2p0 af=18 addr= netmask=
    [2014-Apr-09 10:10:56] RDP (0): bridge0 af=18 addr= netmask=
    [2014-Apr-09 10:10:56] RDP (0): --- END INTERFACE LIST ---
    [2014-Apr-09 10:10:56] RDP (0): ----- BEGIN ACTIVE CONNECTION -----
    [2014-Apr-09 10:10:56] RDP (0): client version: 8.0.24428
    [2014-Apr-09 10:10:56] RDP (0): Protocol state changed to: ProtocolConnectingNetwork(1)
    [2014-Apr-09 10:10:56] RDP (0): Resolved '192.168.16.x' to '192.168.16.x' using NameResolveMethod_DNS(1)
    [2014-Apr-09 10:10:56] RDP (0): Protocol state changed to: ProtocolNegotiatingCredentials(2)
    [2014-Apr-09 10:10:56] RDP (0): Protocol state changed to: ProtocolConnectingRDP(3)
    [2014-Apr-09 10:10:56] RDP (0): Protocol state changed to: ProtocolInactive(4)
    [2014-Apr-09 10:10:56] RDP (0): Server supports RAIL
    [2014-Apr-09 10:10:56] RDP (0): Protocol state changed to: ProtocolActive(5)
    [2014-Apr-09 10:10:56] RDP (0): Protocol state changed to: ProtocolInactive(4)
    [2014-Apr-09 10:10:56] RDP (0): Server supports RAIL
    [2014-Apr-09 10:10:56] RDP (0): Protocol state changed to: ProtocolActive(5)
    [2014-Apr-09 10:12:00] RDP (0): Server hides cursor
    [2014-Apr-09 10:12:01] RDP (0): Server shows cursor
    [2014-Apr-09 10:16:50] RDP (0): Protocol state changed to: ProtocolDisconnected(8)
    [2014-Apr-09 10:16:50] RDP (0): ------ END ACTIVE CONNECTION ------
    [2014-Apr-09 10:16:50] RDP (0): Exception caught: Exception in file '../../librdp/legacytcpstreamadapter.cpp' at line 322
    User Message : Failed to read from socket: -1
    [2014-Apr-09 10:22:22] RDP (0): Final rdp configuration used: screen mode id:i:2
    use multimon:i:1
    session bpp:i:24
    full address:s:192.168.16.x
    audiomode:i:0
    username:s:m
    disable wallpaper:i:0
    disable full window drag:i:0
    disable menu anims:i:0
    disable themes:i:0
    alternate shell:s:
    shell working directory:s:
    authentication level:i:2
    connect to console:i:0
    gatewayusagemethod:i:0
    disable cursor setting:i:0
    allow font smoothing:i:1
    allow desktop com:1
    bookmarktype:i:3
    use redirection server name:i:0
    [2014-Apr-09 10:22:22] RDP (0): --- BEGIN INTERFACE LIST ---
    [2014-Apr-09 10:22:22] RDP (0): lo0 af=18 addr= netmask=
    [2014-Apr-09 10:22:22] RDP (0): lo0 af=30 (AF_INET6) addr=::1 netmask=ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff
    [2014-Apr-09 10:22:22] RDP (0): lo0 af=2 (AF_INET) addr=127.0.0.1 netmask=255.0.0.0
    [2014-Apr-09 10:22:22] RDP (0): lo0 af=30 (AF_INET6) addr=fe80::1%lo0 netmask=ffff:ffff:ffff:ffff::
    [2014-Apr-09 10:22:22] RDP (0): gif0 af=18 addr= netmask=
    [2014-Apr-09 10:22:22] RDP (0): stf0 af=18 addr= netmask=
    [2014-Apr-09 10:22:22] RDP (0): en0 af=18 addr= netmask=
    [2014-Apr-09 10:22:22] RDP (0): en1 af=18 addr= netmask=
    [2014-Apr-09 10:22:22] RDP (0): en1 af=30 (AF_INET6) addr=fe80::ee35:86ff:fe3b:e3d8%en1 netmask=ffff:ffff:ffff:ffff::
    [2014-Apr-09 10:22:22] RDP (0): en1 af=2 (AF_INET) addr=192.168.16.1xx netmask=255.255.255.0
    [2014-Apr-09 10:22:22] RDP (0): en4 af=18 addr= netmask=
    [2014-Apr-09 10:22:22] RDP (0): en3 af=18 addr= netmask=
    [2014-Apr-09 10:22:22] RDP (0): p2p0 af=18 addr= netmask=
    [2014-Apr-09 10:22:22] RDP (0): bridge0 af=18 addr= netmask=
    [2014-Apr-09 10:22:22] RDP (0): --- END INTERFACE LIST ---
    [2014-Apr-09 10:22:22] RDP (0): ----- BEGIN ACTIVE CONNECTION -----
    [2014-Apr-09 10:22:22] RDP (0): client version: 8.0.24428
    [2014-Apr-09 10:22:22] RDP (0): Protocol state changed to: ProtocolConnectingNetwork(1)
    [2014-Apr-09 10:22:22] RDP (0): Resolved '192.168.16.x' to '192.168.16.x' using NameResolveMethod_DNS(1)
    [2014-Apr-09 10:22:22] RDP (0): Protocol state changed to: ProtocolNegotiatingCredentials(2)
    [2014-Apr-09 10:22:22] RDP (0): Protocol state changed to: ProtocolConnectingRDP(3)
    [2014-Apr-09 10:22:22] RDP (0): Protocol state changed to: ProtocolInactive(4)
    [2014-Apr-09 10:22:22] RDP (0): Server supports RAIL
    [2014-Apr-09 10:22:22] RDP (0): Protocol state changed to: ProtocolActive(5)
    [2014-Apr-09 10:22:22] RDP (0): Protocol state changed to: ProtocolInactive(4)
    [2014-Apr-09 10:22:22] RDP (0): Server supports RAIL
    [2014-Apr-09 10:22:22] RDP (0): Protocol state changed to: ProtocolActive(5)
    [2014-Apr-09 10:26:40] RDP (0): Protocol state changed to: ProtocolDisconnecting(7)
    [2014-Apr-09 10:26:40] RDP (0): Protocol state changed to: ProtocolDisconnected(8)
    [2014-Apr-09 10:26:40] RDP (0): *** Application terminated ***
    [2014-Apr-09 10:27:28] RDP (0): *** Application terminated ***
    [2014-Apr-09 10:28:36] RDP (0): Final rdp configuration used: screen mode id:i:2
    use multimon:i:1
    session bpp:i:24
    full address:s:192.168.16.x
    audiomode:i:0
    username:s:m
    disable wallpaper:i:0
    disable full window drag:i:0
    disable menu anims:i:0
    disable themes:i:0
    alternate shell:s:
    shell working directory:s:
    authentication level:i:2
    connect to console:i:0
    gatewayusagemethod:i:0
    disable cursor setting:i:0
    allow font smoothing:i:1
    allow desktop com:1
    bookmarktype:i:3
    use redirection server name:i:0
    [2014-Apr-09 10:28:36] RDP (0): --- BEGIN INTERFACE LIST ---
    [2014-Apr-09 10:28:36] RDP (0): lo0 af=18 addr= netmask=
    [2014-Apr-09 10:28:36] RDP (0): lo0 af=30 (AF_INET6) addr=::1 netmask=ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff
    [2014-Apr-09 10:28:36] RDP (0): lo0 af=2 (AF_INET) addr=127.0.0.1 netmask=255.0.0.0
    [2014-Apr-09 10:28:36] RDP (0): lo0 af=30 (AF_INET6) addr=fe80::1%lo0 netmask=ffff:ffff:ffff:ffff::
    [2014-Apr-09 10:28:36] RDP (0): gif0 af=18 addr= netmask=
    [2014-Apr-09 10:28:36] RDP (0): stf0 af=18 addr= netmask=
    [2014-Apr-09 10:28:36] RDP (0): en0 af=18 addr= netmask=
    [2014-Apr-09 10:28:36] RDP (0): en0 af=30 (AF_INET6) addr=fe80::12dd:b1ff:febe:9771%en0 netmask=ffff:ffff:ffff:ffff::
    [2014-Apr-09 10:28:36] RDP (0): en0 af=2 (AF_INET) addr=192.168.16.1xx netmask=255.255.255.0
    [2014-Apr-09 10:28:36] RDP (0): en1 af=18 addr= netmask=
    [2014-Apr-09 10:28:36] RDP (0): en4 af=18 addr= netmask=
    [2014-Apr-09 10:28:36] RDP (0): en3 af=18 addr= netmask=
    [2014-Apr-09 10:28:36] RDP (0): p2p0 af=18 addr= netmask=
    [2014-Apr-09 10:28:36] RDP (0): bridge0 af=18 addr= netmask=
    [2014-Apr-09 10:28:36] RDP (0): --- END INTERFACE LIST ---
    [2014-Apr-09 10:28:36] RDP (0): ----- BEGIN ACTIVE CONNECTION -----
    [2014-Apr-09 10:28:36] RDP (0): client version: 8.0.24428
    [2014-Apr-09 10:28:36] RDP (0): Protocol state changed to: ProtocolConnectingNetwork(1)
    [2014-Apr-09 10:28:36] RDP (0): Resolved '192.168.16.25' to '192.168.16.x' using NameResolveMethod_DNS(1)
    [2014-Apr-09 10:28:36] RDP (0): Protocol state changed to: ProtocolNegotiatingCredentials(2)
    [2014-Apr-09 10:28:36] RDP (0): Protocol state changed to: ProtocolConnectingRDP(3)
    [2014-Apr-09 10:28:36] RDP (0): Protocol state changed to: ProtocolInactive(4)
    [2014-Apr-09 10:28:36] RDP (0): Server supports RAIL
    [2014-Apr-09 10:28:36] RDP (0): Protocol state changed to: ProtocolActive(5)
    [2014-Apr-09 10:28:36] RDP (0): Protocol state changed to: ProtocolInactive(4)
    [2014-Apr-09 10:28:36] RDP (0): Server supports RAIL
    [2014-Apr-09 10:28:36] RDP (0): Protocol state changed to: ProtocolActive(5)
    [2014-Apr-09 11:33:11] RDP (0): Protocol state changed to: ProtocolDisconnected(8)
    [2014-Apr-09 11:33:11] RDP (0): Exception caught: Exception in file '../../librdp/legacytcpstreamadapter.cpp' at line 322
    User Message : Failed to read from socket: -1
    [2014-Apr-09 11:33:11] RDP (0): ------ END ACTIVE CONNECTION ------
    [2014-Apr-09 11:33:18] RDP (0): Final rdp configuration used: screen mode id:i:2
    use multimon:i:1
    session bpp:i:24
    full address:s:192.168.16.x
    audiomode:i:0
    username:s:michele.lefebvre
    disable wallpaper:i:0
    disable full window drag:i:0
    disable menu anims:i:0
    disable themes:i:0
    alternate shell:s:
    shell working directory:s:
    authentication level:i:2
    connect to console:i:0
    gatewayusagemethod:i:0
    disable cursor setting:i:0
    allow font smoothing:i:1
    allow desktop com:1
    bookmarktype:i:3
    use redirection server name:i:0
    [2014-Apr-09 11:33:18] RDP (0): --- BEGIN INTERFACE LIST ---
    [2014-Apr-09 11:33:18] RDP (0): lo0 af=18 addr= netmask=
    [2014-Apr-09 11:33:18] RDP (0): lo0 af=30 (AF_INET6) addr=::1 netmask=ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff
    [2014-Apr-09 11:33:18] RDP (0): lo0 af=2 (AF_INET) addr=127.0.0.1 netmask=255.0.0.0
    [2014-Apr-09 11:33:18] RDP (0): lo0 af=30 (AF_INET6) addr=fe80::1%lo0 netmask=ffff:ffff:ffff:ffff::
    [2014-Apr-09 11:33:18] RDP (0): gif0 af=18 addr= netmask=
    [2014-Apr-09 11:33:18] RDP (0): stf0 af=18 addr= netmask=
    [2014-Apr-09 11:33:18] RDP (0): en0 af=18 addr= netmask=
    [2014-Apr-09 11:33:18] RDP (0): en0 af=30 (AF_INET6) addr=fe80::12dd:b1ff:febe:9771%en0 netmask=ffff:ffff:ffff:ffff::
    [2014-Apr-09 11:33:18] RDP (0): en0 af=2 (AF_INET) addr=192.168.16.195 netmask=255.255.255.0
    [2014-Apr-09 11:33:18] RDP (0): en1 af=18 addr= netmask=
    [2014-Apr-09 11:33:18] RDP (0): en4 af=18 addr= netmask=
    [2014-Apr-09 11:33:18] RDP (0): en3 af=18 addr= netmask=
    [2014-Apr-09 11:33:18] RDP (0): p2p0 af=18 addr= netmask=
    [2014-Apr-09 11:33:18] RDP (0): bridge0 af=18 addr= netmask=
    [2014-Apr-09 11:33:18] RDP (0): --- END INTERFACE LIST ---
    [2014-Apr-09 11:33:18] RDP (0): ----- BEGIN ACTIVE CONNECTION -----
    [2014-Apr-09 11:33:18] RDP (0): client version: 8.0.24428
    [2014-Apr-09 11:33:18] RDP (0): Protocol state changed to: ProtocolConnectingNetwork(1)
    [2014-Apr-09 11:33:18] RDP (0): Resolved '192.168.16.25' to '192.168.16.25' using NameResolveMethod_DNS(1)
    [2014-Apr-09 11:33:18] RDP (0): Protocol state changed to: ProtocolNegotiatingCredentials(2)
    [2014-Apr-09 11:33:18] RDP (0): Protocol state changed to: ProtocolConnectingRDP(3)
    [2014-Apr-09 11:33:18] RDP (0): Protocol state changed to: ProtocolInactive(4)
    [2014-Apr-09 11:33:19] RDP (0): Server supports RAIL
    [2014-Apr-09 11:33:19] RDP (0): Protocol state changed to: ProtocolActive(5)
    [2014-Apr-09 11:33:19] RDP (0): Protocol state changed to: ProtocolInactive(4)
    [2014-Apr-09 11:33:19] RDP (0): Server supports RAIL
    [2014-Apr-09 11:33:19] RDP (0): Protocol state changed to: ProtocolActive(5)
    [2014-Apr-09 11:33:34] RDP (0): Server hides cursor
    [2014-Apr-09 11:33:38] RDP (0): Server shows cursor
    Any help would be appreciated.

    Hi,
    A connection was forcibly closed by a peer. This normally results from a loss of the connection on the remote socket due to a timeout or a restart. On a datastream socket, the
    connection was reset. This reset could be generated locally by the network system when it detects a connection failure, or it might be received from the remote host (in TCP terms, the remote host sent an RST packet). This error is also possible on a datagram
    socket; for instance, this error could result if your application sends a UDP datagram to a host, which rejects it by responding with an ICMP Port Unreachable.
    Please check the following:
    1. Ping the remote host you were connected to. If it does respond, this problem might have been a transient one (so you can reconnect now), or the server application you were
    connected to might have terminated (so you might not be able to connect again).
    2. Type tracert at the command prompt to determine the path to the host you were connected to. This won't reveal too much unless you know the router addresses at the remote end,
    but it might help to identify if the problem is somewhere along the way.
    3. Check if there is any related error log in the server side.
    Thanks.
    Jeremy Wu
    TechNet Community Support

Maybe you are looking for