Connection reset by peer.

I recently started getting following exception. I use Windows 2000
          with weblogic 5.1 service pack 12. This problem does not effect the
          functionality, and happens randomly.
          Thank you,
          berker(at)optonline.net
          java.net.SocketException: Connection reset by peer: socket write error
               at java.net.SocketOutputStream.socketWrite(Native Method)
               at java.net.SocketOutputStream.write(SocketOutputStream.java:83)
               at weblogic.servlet.internal.ChunkUtils.writeChunks(ChunkUtils.java:88)
               at weblogic.servlet.internal.ResponseHeaders.writeHeaders(ResponseHeaders.java:336)
               at weblogic.servlet.internal.ServletResponseImpl.writeHeaders(ServletResponseImpl.java:603)
               at weblogic.servlet.internal.ServletOutputStreamImpl.flush(ServletOutputStreamImpl.java:101)
               at weblogic.servlet.internal.ServletOutputStreamImpl.writeStream(ServletOutputStreamImpl.java:430)
               at weblogic.servlet.FileServlet.sendFile(FileServlet.java:199)
               at weblogic.servlet.FileServlet.service(FileServlet.java:56)
               at javax.servlet.http.HttpServlet.service(HttpServlet.java:865)
               at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:105)
               at weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:742)
               at weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:686)
               at weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContextManager.java:247)
               at weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:361)
               at weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:261)
               at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
          

Looks like the browser user is closing the browser or moving on to a new url before the response comes back.
          Search the newsgroup, as there are a number of posts concerning this.
          Bill
          berker wrote:
          > I recently started getting following exception. I use Windows 2000
          > with weblogic 5.1 service pack 12. This problem does not effect the
          > functionality, and happens randomly.
          >
          > Thank you,
          > berker(at)optonline.net
          >
          > java.net.SocketException: Connection reset by peer: socket write error
          > at java.net.SocketOutputStream.socketWrite(Native Method)
          > at java.net.SocketOutputStream.write(SocketOutputStream.java:83)
          > at weblogic.servlet.internal.ChunkUtils.writeChunks(ChunkUtils.java:88)
          > at weblogic.servlet.internal.ResponseHeaders.writeHeaders(ResponseHeaders.java:336)
          > at weblogic.servlet.internal.ServletResponseImpl.writeHeaders(ServletResponseImpl.java:603)
          > at weblogic.servlet.internal.ServletOutputStreamImpl.flush(ServletOutputStreamImpl.java:101)
          > at weblogic.servlet.internal.ServletOutputStreamImpl.writeStream(ServletOutputStreamImpl.java:430)
          > at weblogic.servlet.FileServlet.sendFile(FileServlet.java:199)
          > at weblogic.servlet.FileServlet.service(FileServlet.java:56)
          > at javax.servlet.http.HttpServlet.service(HttpServlet.java:865)
          > at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:105)
          > at weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:742)
          > at weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:686)
          > at weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContextManager.java:247)
          > at weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:361)
          > at weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:261)
          > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
          

Similar Messages

  • 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.

  • SSL: Connection reset by peer ; Failed to enable crypto error while calling the report using bing API with SOAP client

    Hi,
    I am trying to fetch report using bing API and making a SOAP call for fetching the data. I get the following error:
    [Warning] fopen(): SSL: Connection reset by peer [file] /var/www/sites/psmedia/perfectstormmedia/tools/class/msn_api.class.php [line] 780
    02-04-2015 10:17:41 (BST) : [Warning] fopen(): Failed to enable crypto [file] /var/www/sites/psmedia/perfectstormmedia/tools/class/msn_api.class.php [line] 780
    02-04-2015 10:17:41 (BST) : [Warning] fopen(https://download.api.bingads.microsoft.com/ReportDownload/Download.aspx?q=rzr63XFt5qJduddohoIRyOYAP%2f1%2ftsnhk8L%2bzBmUpdU2CQlcUB98RpY%2bbOaLFFGMqAC4IUUadC%2fNdNnJqeVCY%2f%2bpy6noVsVA%2fMJp47a3Xb1VjABfKhcdKy6vqpgEdcQg%2fQZ7QcEpZ3bEloJjUtGpDquFk53BnkeHEPVWZkDYcsQegRz%2fpG4t4w6gKCCRmhArd6osr6ZU9CMJ3lbxtGXjcQEMPvP2apNyr9P%2fc8niyfWA2aBcm1aEmOLX2KL3aRJ4rz9N7gG7uBslVZH%2b4rUjHdB7CMkbb%2fHyHwvPTqGPbPCHnicefr%2b%2fDP70hlkBEGfyOOswK67%2bl1zh7CyIv%2bcMlaDsuDX1HeFf4uORfD41H1z7):
    failed to open stream: operation failed [file] /var/www/sites/psmedia/perfectstormmedia/tools/class/msn_api.class.php [line] 780
    Whenever I execute my script. Can you please let me know what we can do to solve this issue. The version of PHP we are using is 5.3.3 with open ssl. 

    Hi Shobha,
    I can't confirm what version of PHP you are using, but to err on the side of caution please use the version specified in the sample/SDK:
    PHP 5.4.14 has been installed from PHP.
    Here is our code examples:
    https://msdn.microsoft.com/en-US/library/bing-ads-overview-getting-started-php-with-web-services.aspx
    Thanks,
    Itai

  • Microsoft Remote Desktop displaying "Connection Reset by Peer"

    Server Side Configuration:
    RDS Gateway Server: MS Server 2008 R2
    RDS Web Server: MS Server 2012 R2 Standard
    RDS Server: MS Server 2008 R2
    Client Side Configurations:
    Dell OptiPlex 9020: MS Windows 7 Enterprise with MS RDC [will refer to as DELL]
    Apple iPad Air: IOS 7.1 with MRD 8.0.5.24403 [will refer to as IPAD]
    Apple MacBook Pro Retina: OS X 10.9.2 with MRD 8.0.5 (Build 24428) [will refer to as MAC]
    First off, this setup is in production and has been working great for all our remote users internally and externally for more then a year. This is our first Apple client to try and connect. I'm pretty sure it's not the server side of things.
    I have tested all three client setups decried above on the same internal network and form the same external Internet connection.
    The DELL and IPAD connect both internally and externally. The MAC will not connect internally or externally. The error box that is displayed simply states "connection reset by peer."

    [2014-Mar-17 10:20:46] RDP (0): en0 af=2 (AF_INET)  addr=192.168.113.147 netmask=255.255.255.0
    [2014-Mar-17 10:20:46] RDP (0): en1 af=18  addr= netmask=
    [2014-Mar-17 10:20:46] RDP (0): en2 af=18  addr= netmask=
    [2014-Mar-17 10:20:46] RDP (0): bridge0 af=18  addr= netmask=
    [2014-Mar-17 10:20:46] RDP (0): p2p0 af=18  addr= netmask=
    [2014-Mar-17 10:20:46] RDP (0): --- END INTERFACE LIST ---
    [2014-Mar-17 10:20:46] RDP (0): ----- BEGIN ACTIVE CONNECTION -----
    [2014-Mar-17 10:20:46] RDP (0): client version: 8.0.24428
    [2014-Mar-17 10:20:46] RDP (0): Protocol state changed to: ProtocolConnectingNetwork(1)
    [2014-Mar-17 10:20:51] RDP (0): Protocol state changed to: ProtocolDisconnected(8)
    [2014-Mar-17 10:20:51] RDP (0): ------ END ACTIVE CONNECTION ------
    [2014-Mar-17 10:20:51] RDP (0): --- BEGIN INTERFACE LIST ---
    [2014-Mar-17 10:20:51] RDP (0): lo0 af=18  addr= netmask=
    [2014-Mar-17 10:20:51] RDP (0): lo0 af=30 (AF_INET6)  addr=::1 netmask=ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff
    [2014-Mar-17 10:20:51] RDP (0): lo0 af=2 (AF_INET)  addr=127.0.0.1 netmask=255.0.0.0
    [2014-Mar-17 10:20:51] RDP (0): lo0 af=30 (AF_INET6)  addr=fe80::1%lo0 netmask=ffff:ffff:ffff:ffff::
    [2014-Mar-17 10:20:51] RDP (0): gif0 af=18  addr= netmask=
    [2014-Mar-17 10:20:51] RDP (0): stf0 af=18  addr= netmask=
    [2014-Mar-17 10:20:51] RDP (0): en0 af=18  addr= netmask=
    [2014-Mar-17 10:20:51] RDP (0): en0 af=30 (AF_INET6)  addr=fe80::7a31:c1ff:febb:5fc%en0 netmask=ffff:ffff:ffff:ffff::
    [2014-Mar-17 10:20:51] RDP (0): en0 af=2 (AF_INET)  addr=192.168.113.147 netmask=255.255.255.0
    [2014-Mar-17 10:20:51] RDP (0): en1 af=18  addr= netmask=
    [2014-Mar-17 10:20:51] RDP (0): en2 af=18  addr= netmask=
    [2014-Mar-17 10:20:51] RDP (0): bridge0 af=18  addr= netmask=
    [2014-Mar-17 10:20:51] RDP (0): p2p0 af=18  addr= netmask=
    [2014-Mar-17 10:20:51] RDP (0): --- END INTERFACE LIST ---
    [2014-Mar-17 10:20:51] RDP (0): ----- BEGIN ACTIVE CONNECTION -----
    [2014-Mar-17 10:20:51] RDP (0): client version: 8.0.24428
    [2014-Mar-17 10:20:51] RDP (0): Protocol state changed to: ProtocolConnectingNetwork(1)
    [2014-Mar-17 10:20:51] RDP (0): Resolved 'gw.glennburdette.com' to '71.93.34.165' using NameResolveMethod_DNS(1)
    [2014-Mar-17 10:20:51] RDP (0): Resolved 'gw.glennburdette.com' to '71.93.34.165' using NameResolveMethod_DNS(1)
    [2014-Mar-17 10:20:51] RDP (0): Error message: Connection reset by peer
    [2014-Mar-17 10:20:51] RDP (0): Protocol state changed to: ProtocolDisconnected(8)
    [2014-Mar-17 10:20:51] RDP (0): Error message: Connection reset by peer
    [2014-Mar-17 10:20:51] RDP (0): ------ END ACTIVE CONNECTION ------
    [2014-Mar-17 10:21:01] RDP (0): Final rdp configuration used: redirectcomports=1
    server port=3389
    use multimon=1
    promptcredentialonce=1
    authentication level=2
    full address=rds.gbpb.local
    session bpp=32
    prompt for credentials on client=1
    redirectprinters=1
    drivestoredirect=
    gatewayusagemethod=2
    alternate full address=rds.gbpb.local
    workspace id=RDWEB.gbpb.local
    allow font smoothing=1
    redirectposdevices=0
    gatewaycredentialssource=0
    devicestoredirect=*
    redirectsmartcards=1
    redirectclipboard=1
    gatewayprofileusagemethod=1
    gatewayhostname=gw.glennburdette.com
    [2014-Mar-17 10:21:01] RDP (0): Final rdp configuration used: gatewayhostname:s:gw.glennburdette.com
    screen mode id:i:2
    use multimon:i:1
    session bpp:i:32
    full address:s:rds.gbpb.local
    audiomode:i:0
    username:s:
    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:1
    disable cursor setting:i:0
    allow font smoothing:i:1
    allow desktop com:1
    bookmarktype:i:3
    use redirection server name:i:0

  • JCO - Connection reset by peer - after 5 minute timeout

    Hello
    We're using SUP with the JCO Connector. This has been working flawlessly since project inception. Now, after switching to a new data center (Windows Server 2008 Server Enterprise Edition, SP2 on VMWare) we're observing a mysterious behavior with timeouts of idle connections. I hope someone in this forum knows what this might be.
    JCO connections originate from SUP servers. When such connections are idle for more than 5 minutes they get disconnected from SAP -- this is in agreement with SAP timeout parameter of 300 seconds.
    On our new systems we noticed that requests sent 5min+ (after timeout) show following error:
    Thread-8 [22:08:55:343]: [JNI-LAYER] RFC.nativeExecute() before RfcCallReceive(2,"Z_U_ONEMOBILE_SWO_SEARCH",0000000010CDC850,0000000000000000,0000000010C81530,000000000C79CA88)
    Thread-8 [22:08:55:344]: [JNI-LAYER] RFC.nativeExecute() after  RfcCallReceive(2,"Z_U_ONEMOBILE_SWO_SEARCH",0000000010CDC850,0000000000000000,0000000010C81530,000000000C79CA88) = RFC_SYS_EXCEPTION
    Thread-8 [22:08:55:344]: [JAV-LAYER] JCO.Client.execute (Z_U_ONEMOBILE_SWO_SEARCH) threw a NON-ABAP exception: com.sap.mw.jco.JCO$Exception: (104) RFC_ERROR_SYSTEM_FAILURE: CPIC-CALL: 'CMRCV : rc=20
    ERROR       connection to partner '---removed!---:3299'
                broken
    TIME        Fri Feb 11 18:08:55 201
    RELEASE     710
    COMPONENT   NI (network interface)
    VERSION     39
    RC          -6
    MODULE      nixxi.cpp
    LINE        4448
    DETAIL      NiIWrite: P=161.88.23.170:3299; L=0.0.0.0:49730
    SYSTEM CALL WSASend
    ERRNO       10054
    ERRNO TEXT  WSAECONNRESET: Connection reset by peer
    COUNTER     3
    Thread-8 [22:08:55:344]: [JNI-LAYER] RFC.nativeDisconnect()                                       enter, [SUCCESS]
    Thread-8 [22:08:55:344]: [JNI-LAYER] RFC.nativeDisconnect() before RfcClose(2)
    Thread-8 [22:08:55:344]: [JNI-LAYER] RFC.nativeDisconnect() after  RfcClose(2)
    Thread-8 [22:08:55:344]: [JNI-LAYER] RFC.nativeDisconnect()                   with rc = RFC_OK   leave, [SUCCESS]
    Our suspicion is that the JCO client doesn't notice the fact that it gets disconnected. We used Network Monitor 3.4 to look at network traffic. Indeed, after 5 minutes the client gets a single frame (with reset flag) and no acknowledgement goes back.
    What could this be?
    We use
    JCO 2.1.8 AMD 64-bit (contains librfc 6.40) and
    JCO 2.1.9 AMD 64-bit (contains librfc 6.40) but replaced this with librfc 7.10 (after seeing Note 825494). Behavior was exactly the same. We did confirm in jco/rfc trace that those versions were actually used.
    Any ideas?
    Thanks and regards
    Edited by: B. Gottipati on Feb 14, 2011 9:17 PM

    Hello
    We're using SUP with the JCO Connector. This has been working flawlessly since project inception. Now, after switching to a new data center (Windows Server 2008 Server Enterprise Edition, SP2 on VMWare) we're observing a mysterious behavior with timeouts of idle connections. I hope someone in this forum knows what this might be.
    JCO connections originate from SUP servers. When such connections are idle for more than 5 minutes they get disconnected from SAP -- this is in agreement with SAP timeout parameter of 300 seconds.
    On our new systems we noticed that requests sent 5min+ (after timeout) show following error:
    Thread-8 [22:08:55:343]: [JNI-LAYER] RFC.nativeExecute() before RfcCallReceive(2,"Z_U_ONEMOBILE_SWO_SEARCH",0000000010CDC850,0000000000000000,0000000010C81530,000000000C79CA88)
    Thread-8 [22:08:55:344]: [JNI-LAYER] RFC.nativeExecute() after  RfcCallReceive(2,"Z_U_ONEMOBILE_SWO_SEARCH",0000000010CDC850,0000000000000000,0000000010C81530,000000000C79CA88) = RFC_SYS_EXCEPTION
    Thread-8 [22:08:55:344]: [JAV-LAYER] JCO.Client.execute (Z_U_ONEMOBILE_SWO_SEARCH) threw a NON-ABAP exception: com.sap.mw.jco.JCO$Exception: (104) RFC_ERROR_SYSTEM_FAILURE: CPIC-CALL: 'CMRCV : rc=20
    ERROR       connection to partner '---removed!---:3299'
                broken
    TIME        Fri Feb 11 18:08:55 201
    RELEASE     710
    COMPONENT   NI (network interface)
    VERSION     39
    RC          -6
    MODULE      nixxi.cpp
    LINE        4448
    DETAIL      NiIWrite: P=161.88.23.170:3299; L=0.0.0.0:49730
    SYSTEM CALL WSASend
    ERRNO       10054
    ERRNO TEXT  WSAECONNRESET: Connection reset by peer
    COUNTER     3
    Thread-8 [22:08:55:344]: [JNI-LAYER] RFC.nativeDisconnect()                                       enter, [SUCCESS]
    Thread-8 [22:08:55:344]: [JNI-LAYER] RFC.nativeDisconnect() before RfcClose(2)
    Thread-8 [22:08:55:344]: [JNI-LAYER] RFC.nativeDisconnect() after  RfcClose(2)
    Thread-8 [22:08:55:344]: [JNI-LAYER] RFC.nativeDisconnect()                   with rc = RFC_OK   leave, [SUCCESS]
    Our suspicion is that the JCO client doesn't notice the fact that it gets disconnected. We used Network Monitor 3.4 to look at network traffic. Indeed, after 5 minutes the client gets a single frame (with reset flag) and no acknowledgement goes back.
    What could this be?
    We use
    JCO 2.1.8 AMD 64-bit (contains librfc 6.40) and
    JCO 2.1.9 AMD 64-bit (contains librfc 6.40) but replaced this with librfc 7.10 (after seeing Note 825494). Behavior was exactly the same. We did confirm in jco/rfc trace that those versions were actually used.
    Any ideas?
    Thanks and regards
    Edited by: B. Gottipati on Feb 14, 2011 9:17 PM

  • XI 2.0 Inbound file adapter : Connection reset by peer

    I am using XI 2.0 and have an inbound file adapter. It polls every 5 minutes. But at least 1 or twice a day the file adapter stops with the following error message.
    "java.net.SocketException: Connection reset by peer: JVM_recv in socket input stream read" occurred \par
    There have been times when this runs for days or weeks without any problems.
    Has anyone else seen this issue and how do your correct it?
    Currently I have to go into the file adpaters and restart them manually. It would be nice if there was some way to automate this function. Any ideas?
    Regards,
    Jim

    With JDK 5.0 use ojdbc5.jar instead of ojdbc14.jar.

  • Connection reset py peer

    When I try to connect to Itunes Store on my iphone, I get a message back saying "Cannot connect to Itunes Store.  Connection reset by peer.  How can I resolve this?

    Hi Roen,
    Maybe I'm pointing you into the wrong direction, on forehand my apologies for that.
    What I need you should check: Ironport has a limit on the number of concurrent TLS session. Your problem might occur when this limit is reached and an additional host tries to setup a TLS connection.
    (Not sure, just a shot in the dark)
    Good luck with this problem,
    Best Regards,
    Steven

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

    Hey Guys,
    Has anyone seen this issue? We get this error in our Weblogic app logs at times and no one is able to login to our application. Our database server and SQL server seem fine at a high level. Any ideas what is causing this?
    com.s1.arch.persistence.exception.PersistenceException weblogic.jdbc.mssqlserver4.TdsException: I/O exception while talking to the server, java.net.SocketException: Connection reset by peer: JVM_recv in socket input stream read
    Thanks

    please make sure that there is no Firewall between your servers and DB server. this message usually happen when there is a fire wall between the servers. if yes please make sure that the connection time on fire wall is longer than the time needed to complete an operation another thing that you need to check if you have a fire wall which is to make sure that Oracle DBMS return the request to the same port that it is listening to (1521 default).

  • JCOM throwing SocketException: Connection reset by peer: socket write error

    I have an ejb which is calling a simple ActiveX component using JCOM.
    Ocassionally the ejb loses the ability to connect to the ActiveX component. Any attempt to call a method results in a java.net.SocketException: Connection reset by peer: socket write error.
    However the ActiveX component continues to run correctly. I can still connect to it using a vb test client. This is using com to connect, not DCOM as used by JCOM(JIntegra).
    The application server and the ActiveX component are running on the same server.
    Any suggestions as to why the JIntegra DCOM request could be failing?
    Thanks,
    Greg.

    I have an ejb which is calling a simple ActiveX component using JCOM.
    Ocassionally the ejb loses the ability to connect to the ActiveX component. Any attempt to call a method results in a java.net.SocketException: Connection reset by peer: socket write error.
    However the ActiveX component continues to run correctly. I can still connect to it using a vb test client. This is using com to connect, not DCOM as used by JCOM(JIntegra).
    The application server and the ActiveX component are running on the same server.
    Any suggestions as to why the JIntegra DCOM request could be failing?
    Thanks,
    Greg.

  • 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

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

    Dear All,
    We are facing a very unusual problem. In our application, there is a functionality to transfer files to a FTP server using java FTPClient.
    Now while transferring set of files, few times it throws the error:
    Connection reset by peer: JVM_recv in socket input stream read
    This error comes irregularly.
    Can you suggest the reason for this.
    Regards,
    Akhil

    which platform are you using? which ip stack , ipv4 or ipv6?
    try to set -Djava.net.preferIPv4Stack="true" when startup,
    it will use ipv4 stack instead of default ipv6 on solaris.

  • 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

  • Office Web Apps Server Name issue with Sharepoint 2013

    I have a POC Lab setup for SharePoint/OfficeWebApps with SSL offloading. I am using IIS reverse proxy for my SSL offloader. Most systems can connect to SharePoint and OWA through the Loadbalancer and create documents as desired. The configuration is

  • WAR files on managed servers

    I have a question about placing new war files in production. First, why does WebLogic recommend AGAINST using auto-deploy in production? Is it for security or stability and what are those arguements? Second, do I need to move the actual war file to t

  • Issue regarding local time

    Hi, Assume that an application with db data are supposed to be installed in London (in a data center) whereas ... all users who would connect to this db are in Greece. The db time zone would be of London ... which means that the date-time data would

  • Firewire help please

    k guys i nee some serious help....im getting a little nervous here. I recently purchased a mackie mixer the onyx 1620, and the other day i purchased the firewire adapter let me just say the mixer is great, i couldnt be happier. However, the firewire

  • Grey Wi-Fi bottom

    Hejj guys I've got a big problem. My iPhone 4s isn't working anymore. I need (and have) WI-FI at home, but cannot use it. The WI-FI bottoms backround is dark grey and i cannot turn it on. Hope for help :)            - iPhone 4s            - Wi-Fi